-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hierarchy & Structure #4
Comments
hey @sophshep I can certainly try to help out, let me know what you need. |
Thanks @willdoran! @rjmackay set up the basic build on the rtd-sphinx branch. I'm currently working through theming it, but setting up the structure is beyond me. I believe that currently it just has existing content that Robbie brought over, which is quite messy. What I'd like to do is organize it to match the document above. Each page can have dummy content or just be empty. Then the comms team can enter content into a fresh system via GitHub. |
@sophshep: Ok, groovy. I'll pull down the repo, peruse it and figure out how to get the structure to fit the doc. I'll update you when I have it together. |
@sophshep Ok - stop me if this is the not what you're looking for or you've already got this bit: In order to match the ToC structure from the doc it is necessary to edit the index.rst file. This is the landing page. For example, the section Getting started with Ushahidi Would become in the index.rst file:
In the getting-started dir, an index.rst should be created linking out to the subpages getting-started/index.rst:
That is one option, it is also possible to create a single file called getting-started.rst and to create sub-heading with in it. A good example for that approach is the guzzle docs: Let me know if that was any help or just made things worse! |
I need Dev help to set up the navigation & pages on our new sphinx build to match those of the support taxonomy doc: https://docs.google.com/document/d/1mabJN8S5FNYlS0EQ5Cm-hNNcBxPLHcc6BmN79RqpTpw/edit
cc @rjmackay @willdoran @jshorland
The text was updated successfully, but these errors were encountered: