{"action":"created","issue":{"url":"https://api.github.com/repos/EWSoftware/SHFB/issues/305","repository_url":"https://api.github.com/repos/EWSoftware/SHFB","labels_url":"https://api.github.com/repos/EWSoftware/SHFB/issues/305/labels{/name}","comments_url":"https://api.github.com/repos/EWSoftware/SHFB/issues/305/comments","events_url":"https://api.github.com/repos/EWSoftware/SHFB/issues/305/events","html_url":"https://github.com/EWSoftware/SHFB/issues/305","id":160031417,"number":305,"title":"Separating Sandcastle Assembly Documentation into Multiple Navigation TOCs","user":{"login":"swirlywonder","id":212884,"avatar_url":"https://avatars.githubusercontent.com/u/212884?v=3","gravatar_id":"","url":"https://api.github.com/users/swirlywonder","html_url":"https://github.com/swirlywonder","followers_url":"https://api.github.com/users/swirlywonder/followers","following_url":"https://api.github.com/users/swirlywonder/following{/other_user}","gists_url":"https://api.github.com/users/swirlywonder/gists{/gist_id}","starred_url":"https://api.github.com/users/swirlywonder/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/swirlywonder/subscriptions","organizations_url":"https://api.github.com/users/swirlywonder/orgs","repos_url":"https://api.github.com/users/swirlywonder/repos","events_url":"https://api.github.com/users/swirlywonder/events{/privacy}","received_events_url":"https://api.github.com/users/swirlywonder/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":9,"created_at":"2016-06-13T19:56:17Z","updated_at":"2016-06-29T18:46:22Z","closed_at":null,"body":"I have been struggling over the past week to solve splitting assembly documentation into multiple parent directories. Between myself and the community on stack overflow, I have thus far been unsuccessful in solving the problem.\r\n\r\nHere is a link to that post:\r\nhttp://stackoverflow.com/questions/37711760/separating-sandcastle-assembly-documentation-into-multiple-navigation-tocs\r\n\r\nTo summarize, I have multiple libraries with distinctly separate release cycles and semantic versions. I am attempting to maintain a single documentation website with separated sections for documenting each assembly and it's appropriate class namespaces.\r\n\r\nHere is an example structure:\r\n\r\nOverview\r\nLibrary A\r\n--Overview\r\n--Release notes\r\n--**Library A generated Namespace/Assembly documentation**\r\nLibrary B\r\n--Overview\r\n--Release notes\r\n--**Library B generated Namespace/Assembly documentation**\r\nLibrary C\r\n--Overview\r\n--Release notes\r\n--**Library C generated Namespace/Assembly documentation**\r\n\r\nAs mentioned in my post, I am not opposed to custom work but I have had considerable trouble determining the proper approach to altering the default behavior of a single namespace parent topic for all assemblies combined."},"comment":{"url":"https://api.github.com/repos/EWSoftware/SHFB/issues/comments/229450933","html_url":"https://github.com/EWSoftware/SHFB/issues/305#issuecomment-229450933","issue_url":"https://api.github.com/repos/EWSoftware/SHFB/issues/305","id":229450933,"user":{"login":"swirlywonder","id":212884,"avatar_url":"https://avatars.githubusercontent.com/u/212884?v=3","gravatar_id":"","url":"https://api.github.com/users/swirlywonder","html_url":"https://github.com/swirlywonder","followers_url":"https://api.github.com/users/swirlywonder/followers","following_url":"https://api.github.com/users/swirlywonder/following{/other_user}","gists_url":"https://api.github.com/users/swirlywonder/gists{/gist_id}","starred_url":"https://api.github.com/users/swirlywonder/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/swirlywonder/subscriptions","organizations_url":"https://api.github.com/users/swirlywonder/orgs","repos_url":"https://api.github.com/users/swirlywonder/repos","events_url":"https://api.github.com/users/swirlywonder/events{/privacy}","received_events_url":"https://api.github.com/users/swirlywonder/received_events","type":"User","site_admin":false},"created_at":"2016-06-29T18:46:22Z","updated_at":"2016-06-29T18:46:22Z","body":"I was able to create a redirect component and it is fully functional. Luckily no XSLT was required for this to work so it's pretty self-contained. The sample is attached.\r\n\r\n[ContentRedirectComponent.zip](https://github.com/EWSoftware/SHFB/files/339936/ContentRedirectComponent.zip)\r\n\r\nI'd like to adhere to naming patterns of existing components for both the component/plugin and the structure of the redirect token (for lack of a better term). Currently, the presence of <redirect url=\\\"http://www.example.com\\\" /> anywhere within the conceptual topic will transform the page into an automatic redirect. Obviously this wouldn't be a known element to your XSD for MAML so I'm open to a better way. Do you have a better recommendation for how to name these? "}}
{"actor":{"display_login":"swirlywonder"}}