-
Notifications
You must be signed in to change notification settings - Fork 20
Work out how to host docs for individual tools #4
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
Comments
Hi @adamltyson, are there any constraints on what tech stack should be used to build the website and aggregate the docs? |
This issue is slightly outdated, we have a single website to host all the docs (this is the repo). What's missing is a way to aggregate the API docs (to be built from the docstrings using Sphinx) into the one site. |
@adamltyson did you mean something like this? |
Yep, that's what we need. The tricky bit is doing it for every BrainGlobe package, and rendering them on a single website. |
I think I figured it out. I will raise a PR once I'm done with the remaining BG packages. |
Ideally we want:
a) Tool-specific docs to be part of the relevant repo so that docs can be updated along with code (and autogenerated API docs)
b) All docs to be accessible via one site (brainglobe.info)
How do we do this? I haven't found any tool to automate this, the best way seems to be some kind of custom build script. The process could be something like:
Any ideas @alessandrofelder? We should think about this as we start to accumulate more documentation for different parts of the project.
The text was updated successfully, but these errors were encountered: