-
Notifications
You must be signed in to change notification settings - Fork 655
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
Switch docs theme #4276
Switch docs theme #4276
Conversation
Linter Bot Results:Hi @lilyminium! Thanks for making this PR. We linted your code and found the following: Some issues were found with the formatting of your code.
Please have a look at the Please note: The |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @lilyminium, awesome work!
Codecov ReportPatch and project coverage have no change.
Additional details and impacted files@@ Coverage Diff @@
## develop #4276 +/- ##
==========================================
Coverage 93.40% 93.40%
==========================================
Files 170 184 +14
Lines 22250 23358 +1108
Branches 4071 4071
==========================================
+ Hits 20783 21818 +1035
- Misses 951 1024 +73
Partials 516 516
☔ View full report in Codecov by Sentry. |
Is this one of those where we can just say we don't care and it'll go away soon or is that being too hopeful? |
I could maybe pin sphinx_rtd_theme >=1 with mdanalysis_sphinx_theme to resolve this? (or would RTD just ignore that version and go for the more permissive variant?) It is a very weirdly old version (released 2019, sphinx_rtd_theme is on 2.0.0rc2 atm) and I'm curious why RTD has picked it. It'd be a bit annoying if we couldn't preview our docs properly there. User guide is picking up the same 0.4.3... |
I guess you could try just override the version in the yaml file here for now and see what happens? If that doesn't work then they are doing some annoying black magic in the background that is unlikely get fixed with pinning upstream. |
Seems to have done a thing? TIL RTD actually advocates for pinning the sphinx_rtd_theme version: https://docs.readthedocs.io/en/stable/guides/reproducible-builds.html#id2 |
Oh nice! I was just tracking stuff down myself, since everywhere seemed to be picking up the 0.4.3 version. I think it might be preferring anaconda/noarch (https://anaconda.org/anaconda/sphinx_rtd_theme), which tops out at 0.4.3, over conda-forge (https://anaconda.org/conda-forge/sphinx_rtd_theme). Edit: whoops, I should have let RTD finish building before pushing the rebase :/ sorry for the wait |
bf6f558
to
7ccfaf4
Compare
Less work is better work. I would just go with the lower bound pin? Would it make sense to just have the pin upstream in the new theme? It's annoying to add a dependency, but it would probably save you some headaches later? |
Yeah I'll pin upstream. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks super-nice already on RTD. Great work! I look forward to seeing it merged.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you tick the lgplv2 box?
Otherwise, lgtm! This is really awesome, thanks @lilyminium ! 🎉
@@ -31,11 +31,11 @@ | |||
|
|||
This module contains classes for interconverting between Cartesian and an | |||
internal coordinate system, Bond-Angle-Torsion (BAT) coordinates | |||
:cite:p:`Chang2003`, for a given set of atoms or residues. This coordinate | |||
:footcite:p:`Chang2003`, for a given set of atoms or residues. This coordinate |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we document how we do citations anywhere in our docs? We probably should tell folks that cite -> footcite now
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are there any peculiarities to footbibliography that should be stated somewhere? (I don't know how/if it differs from the old approach)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ticked :)
I don't think so, no more than bibliography
is. The footbib is used for local bibliographies (on the same page as the reference), so we can remove stuff like the a-
and b-
prefixes we had before. The normal bibliography is for global bibliographies, so one reference list for the entire repo. This is all readily available on the sphinx bibtex extension docs though. I was planning to add in some notes in the mdanalysis-sphinx-theme -- MDAnalysis/mdanalysis-sphinx-theme#26
The one catch is that there's meant to be one footbib per reference per page, so if footbibliographies are created multiple times for the same reference, then only the first one will ahve the reference and all links will go there. Again I got this from the official docs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you maybe raise an issue in the userguide for docs on this? This is the kind of info any contributor new or old should be told to look at so imho, even if it's just a reference to the theme docs, your above explanation should exist there in some way.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, done
Fixes MDAnalysis/mdanalysis-sphinx-theme#33
Fixes #4199
Changes made in this Pull Request:
PR Checklist
Developers certificate of origin
📚 Documentation preview 📚: https://mdanalysis--4276.org.readthedocs.build/en/4276/