-
Notifications
You must be signed in to change notification settings - Fork 474
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
New documentation #1474
New documentation #1474
Conversation
@hgrecco you can build it and tell me what you think. |
8c75069
to
17ef268
Compare
I'd also recommend using |
Thanks for the tip |
@jules-ch I like it a lot. It is clean, with good contrast, readability and tables and code are properly colored. Go for it. A few things that I have noticed:
|
Sounds Perfect! |
I am already working in the code reorganization (I will rebase afterwards) just to get a flavor of how it would look like. |
Yeah saw that, just wanted to know how you would like to proceed since it will have an impact on API reference mostly. |
ping, @jules-ch. Is there anything I can do to help finishing this? Otherwise, should we release now and include the new documentation in the next release? There's a few bug fixes that would be really important to be included in a release very soon. |
Gonna push this next week for the next release at least the new trees & theme & start from there with new contents. |
@jules-ch, any updates on this? I think this was close enough, and the only thing left to do is to fix the linter job. |
With the reorganization in facets, I need to update conflicts & API reference. |
sure, no pressure. FYI the merge conflicts seem to be pretty small (I'd think the only one caused directly by the facets is two lines in the |
17ef268
to
1d937f7
Compare
Ok this is ready to be merged. There is still work to be done to have a proper API Reference that we can link in the documentation. |
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.
I have a few questions, but otherwise this looks good to me, and I agree that anything further (like the API docs) can be done in a separate PR
5967ca2
to
b437377
Compare
a2cc663
to
e0932e0
Compare
@keewis & @hgrecco if you can make a final review. I tried to stick to the style of numpy, pandas etc. tell me what you think & I will merge this |
Congratulation for all the awesome work! It looks fantastic. The facets look fine to me ,but I am maybe not the best person to judge as I know perfectly where everything is and why! In any case, I like it a lot. My only suggestion is if there is room for a code snippet in the main page. What do you think? I usually like to see how it looks at a glance! |
The links on https://pint--1474.org.readthedocs.build/en/1474/user/numpy.html#Technical-Commentary are slightly messed up now. Is there a way to disable intpretting the unit definition code blocks on https://pint--1474.org.readthedocs.build/en/1474/user/defining.html as python code? Seeing 60 and min colored looks off. To me it seems odd to see 3 topics under "Going further", I think they would fit under advanced topics. Not a big deal though. There are two pint.facets.numpy in the API reference |
One more thing (sorry) that I just noticed. At the footer I would rather put By the Pint Authors (and if possible a link to the AUTHORS file). And in Contributing: We do not use travis anymore. |
Ok, I'll make the changes
Yep saw that commit haven't been pushed yesterday xD |
From a quick glance, this looks good to me. I'd probably fix the the footer and merge afterwards: this change is big enough already, so I think anything further would be easier to review / merge in separate PRs. The links in the As for the facets: those are pretty advanced and most likely only contributors would read it, but I think we should try to create a new page describing the API to help new contributors with understanding the general structure of the code base (but once again, I don't think that should be done in this PR). |
I agree with @keewis. I'll try to fix most of your remarks but we need to get this out & work form there. |
4f5db6d
to
6014b35
Compare
- Rework of configuration with new sphinx_book_theme - Use ipython directive where necessary - Add theme to requirements_docs.txt - Start using autosummarry - Fix doctests - Add sphinx design to requirements - Add overview & panels in home page - Update footer with `Pint Developers` - Fix docstrings - Use string imports in __all__ in __init__.py
6014b35
to
51d0614
Compare
I've changed the footer. I'll wait for CI to finish & I'm gonna merge this. We can have follow up issues/PR. |
This my go to rework the Pint Documentation.
About the theme, we can choose between, they are widely used & offer good reading experience :
For the pydata sphinx theme I need to rearrange the toc tree a bit to have a proper Userguide, API Reference, dev guide if we choose it.