-
Notifications
You must be signed in to change notification settings - Fork 110
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
Documentation tied to version of compas pkg. #341
Comments
hi anton, yes, that is indeed an unsolved problem that causes confusion. especially when we make backwards incompatible changes to the API. as far as i know, it is not possible to use your own theme with RTD, so i would prefer the would be helpful indeed if you could propose a solution. thanks, |
Hi Tom! I see. Yeah, RTD only allows its own theme or the standard Sphinx theme. I will try to get the versioning-extension to work in the coming week. There's is some questions regarding the maintenance of the project, see sphinx-contrib/sphinxcontrib-versioning#59, but there seems to be people interested and keen to keep it going. EDIT |
if clicking on the version number switches the docs to the corresponding version, then that is great :) |
pasting here from a parallel discussion:
context: we encountered in the MAS compas introduction, that the example mesh-delaunay-from-points and mesh-remeshing both import from |
I'm currently updating the examples ( |
the examples will need some manual maintenance. there is no way around this. we should clearly mention that people have to report broken examples on the issue tracker... |
I haven't forgotten this, I've tried to get it working but no luck so far. See linked issue for more details. |
Documentation will reflect latest release, PR #396. Closing. |
Adding this as a note to future self, we would need to amend old tagged commits to add sphinxcontrib_versioning to the conf.py extension array. |
This might be something to look at again, I've been following the development of a new sphinx plugin, sphinx-multiversion. I can do some test, maybe this weekend.. |
Generic Ping. I see that Maybe @gonzalocasas have some experience? |
Documentation tied to version of compas pkg.
Problem description
I'd guess that the majority of users are installing compas from pypi or conda which means that they are installing the repo at a tagged commit. If they want to view the documentation online however they will see documentation from the most recent commit, which could cause confusion.
So the correct (version specific) documentation will be available in the installed package but not online.
Proposed solution
I think it would be good to consider a system that allows documentation tied to tagged commits.
Two examples with both works with Sphinx would be:
Sphinxcontrib-versioning could probably work with our current
Invoke
solution while a solution like ReadTheDocs would mean having the docs built and hosted by another service.If there's interest I'd happily help making this change.
The text was updated successfully, but these errors were encountered: