We need a better way to share content that lives in separate repos via links in TOC.
- We want to be able to cross-link to content
- We want to be able to reuse or pull content into a toc
Example of what MS does: https://dotnet.github.io/docfx/tutorial/intro_toc.html#link-to-another-toc-file
Use case:
- We have many cli plugins at /docs root today: https://dev.console.test.cloud.ibm.com/docs/container-registry-cli-plugin/container-registry-cli.html
- We want to be able to pull the plugin content into the toc and point to them from
/cli
At this link :https://dev.console.test.cloud.ibm.com/docs/cli/plugins/auto-scaling/index.html#autoscalingcli, auto-scaling is building today inside /cli (content is physically nested) so of course toc works, its just nested, but pointing off to container-registry-cli-plugin which lives at /docs/ root in its own folder, does not.
https://github.ibm.com/Bluemix-Docs/cli/blob/staging/toc
Right now using relative path will not work, and toc link for xml has no correlative to json:
[Container Registry CLI plug-in](../container-registry-cli-plugin/container-registry-cli.html)
We need a better way to share content that lives in separate repos via links in TOC.
Example of what MS does: https://dotnet.github.io/docfx/tutorial/intro_toc.html#link-to-another-toc-file
Use case:
/cliAt this link :https://dev.console.test.cloud.ibm.com/docs/cli/plugins/auto-scaling/index.html#autoscalingcli, auto-scaling is building today inside /cli (content is physically nested) so of course toc works, its just nested, but pointing off to
container-registry-cli-pluginwhich lives at /docs/ root in its own folder, does not.https://github.ibm.com/Bluemix-Docs/cli/blob/staging/toc
Right now using relative path will not work, and toc link for xml has no correlative to json:
[Container Registry CLI plug-in](../container-registry-cli-plugin/container-registry-cli.html)