-
Notifications
You must be signed in to change notification settings - Fork 12
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
How to organize the Software Guide TOC #64
Comments
The button is not cutting it for me, still thinking of alternatives.
this is not about my taste, it's people going round in circles between hardware and software docs and getting confused. This is related to the sites needing separate but similar visual identities (as in open-ephys/bonsai-onix1-docs#15) |
We discussed with @cjsha how to make the links to documentation more evident. At the Software Guide page, provide the linkouts to the external documentation sites (bonsai.onix1 library docs and GUI docs) So then that leaves us with two other things that are hierarchically different: the oni-repl docs and the old library docs.
|
I think it's good practice for every page to belong to a table of contents especially so it can have proper breadcrumbs. I propose the toc keeps all four items that are currently there but the first two link out to external sites if possible. What do you think? |
I'm not sure how to make OpenEphys.Onix1 a first-class citizen in the same way that Bonsai.Onix was.
Previous discussion exists in PR #62
If we're happy how it is, we can leave it as is, but I wanted to open this issue in case anyone had any more ideas or comments regarding this concern.
The text was updated successfully, but these errors were encountered: