-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Docs overhaul: GitHub Discussions, add logo, new theme #4960
Conversation
@sampsyo @RollingStar @Serene-Arc The bad news is:
Out of the box Alabaster doesn't offer as much configuration abilities as readthedocs theme: https://alabaster.readthedocs.io/en/latest/customization.html#theme-options It's suggested that custom_stylesheet is used for customization. So, if we continue to want to go down that route, I would greatly appreciate any input on where possible this CSS should be altered to adress my above mentioned concerns: Some more resources to dig in, maybe I missed something, help me get through all that: |
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.
Awesome; thanks for changing all these links! I found one nit to fix.
It's too bad about the mobile usefulness of Alabaster. That doesn't seem great! I can see what you mean when browsing, for example, https://requests.readthedocs.io/ on mobile. It's fine-ish for reading the current page, but there is no navigation—the sidebar is just completely hidden on mobile.
Ah well. Maybe we should just go back to the RTD theme? Even if it's less beautiful, it is more full featured. I guess we could browse other Sphinx themes too, but it doesn't necessarily seem like the most effective use of time to worry too much about picking the perfect one:
https://sphinx-themes.org
README_kr.rst
Outdated
@@ -104,5 +104,5 @@ Read More | |||
`Adrian Sampson`_ 와 많은 사람들의 지지를 받아 Beets를 만들었다. | |||
돕고 싶다면 `forum`_.를 방문하면 된다. | |||
|
|||
.. _forum: https://discourse.beets.io | |||
.. _forum: https://https://github.com/beetbox/beets/discussions/ |
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
I vote for changing the theme if it's causing this much angst. The visual continuity is less important than the practical use, which is the point of documentation. We should just get a new theme and go with that. New theme right around the time of our only release for like two years wouldn't cause too much confusion either. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
@Serene-Arc forget my last two comments! I should read more carefully before replying 😅 I think we are on the same page here. Functionality should come first! That's why the Alabaster theme already has lost the race for me, even though I love it visually. So since yesterday evening I'm thinking about either going back to readthedocs (because we know it works!) or finding something new. @sampsyo since you handed over "the mighty beetroot" to me, there was no going back! 🤣 Have a look below why we can't go back to the readthedocs theme haha! |
So I had a wonderful morning with playing around with Sphinx theming and (no shit) I really enjoyed it :-) readthedocs with some customization - top left background defaulting to blue was a no-go with the beetroot with white background. There is issues though: The version number text is white, as well as the "beets" title on top of the logo. That would require more customization. |
This is the book theme. From scrolling thru all the themes yesterday evening this was my favorite and I thought it could be our best choice. I had to do some customization though since initially the font-size overall was too big for my taste. I really couldn't stand that, so now let me proudly present....base-font set a nuance smaller. I like it now. It's also mobile friendly they say. Please not the secondary sidebar on the right. It shows the current pages chapters in detail. Very handy to jump between let's say different config options (assuming we were in the Configuration chapter)! Great feature! |
After my first failed attempts getting my former favorite - the book theme - right, I learned that book is a close descendet of the pydata theme. So I gave this one a try and surprisingly I have to admit: This is my absolute favorite now! Even though it has loads of features, it still has a very clean look! Also dig the smaller logo on top left. Best feature is (next to the secondary sidebar we know from the book theme already) the "top level navigation" - it is super handy to have our main chapters on first sight, actually at all times, sitting there and switching between them is made so easy without having to use a sidebar at all. So yeah, that would be my favorite! What do you guys say? @Serene-Arc @sampsyo @Steffo99 @RollingStar (I have the setup of all those themes each in a single commit now so actually we could even give one a try and redecide later on - switching now is easy. To really test it for mobile purposes we have to actually merge it, I can't think of another easy way) |
Looks nice and intuitive! |
Awesome!!! That PyData theme looks really good—it's less retro-looking than the official RTD theme, and the navigation features look useful. I say go for it! |
and leave html_static_path commented out in conf.py as a reminder. We might need it if builds via readthedocs require it.
and rephrase a little if required. Often "our forums" was stated. Mostly I tried to use the wording "discussion board" throughout and (almost) never used the term "GitHub Discussions"
- Fixed sidebar - Sidebar collapse (default but make sure)
- Sticky Nnavigation (default but make sure) - Top left area white, to fit with beets logo background - Title "beets" - Logo only false, we want to see title - Version true, we want to see which beets version we are looking at - Issue: The latter two are invisible, would require custom CSS!!!
- Collapse nav - Add title "beets" next to small logo on top left
- Reduce base font a bit by custom.css - Collapse nav - Title "beets" below logo
This reverts commit 71873b6. Revert back to using "pydata" theme. Keep this in the history, just in case we reconsider to using "book".
I think it's great! |
- Set static path and css file in Sphinx config. - Codebox style to black/white - Secondary color to beetroot red - Inline code color to beetroot green - Leave primary color (pydata teal), difficult to read with beetroot green. Works well with beetroot red actually. - Leave some notes on colors in beets.css for reference.
@Serene-Arc or @sampsyo a little help required :-) I can't get the test-docs job to run successfully. I've added the them package to the docs requirements in setup.py, but that doesn't seem to be enough. A local docs run tells me this:
do I need to add the theme name/package somewhere in ci.yaml workflow? (I think the "missing theme.conf" error is misleading - at least up to my current research....) Thanks in advance for any hints! |
and in add to deps in tox.ini.
Got it! Adding to tox.ini |
Oh wow! It's lovely on mobile as well. I'm very happy with it 😍 ![]() ![]() Two fixme's though: Forgot to set favicon to beetroot too! And I forgot to disable the "dark theme button" I mean we can keep it but I just didnt customize it to fit with the logo, so @sampsyo if you could send me the beetroot with a transparent background instead of white or the original project file, if it still exists. Or tell me to screw around with the pic I got with Gimp myself and I'll fix at least the logo for the darktheme :-)) For now all good I guess 😃 |
Perfect! Thanks a lot! I quickly exchanged it in Now both light and dark theme use it. I reconsidered about the favicon: The regular "readthedocs" favicon is being used and I think a lot of people are very used to finding python project docs with that typical favicon between all their open browser tabs (including myself), so I think that is actually a good thing. So IMO, all sorted out here :-) |
Thank you! Some examples with the new theme: https://beets.readthedocs.io/en/latest/index.html |
Description
Fixes #4916
Make sure the Alabaster theme stays used.Some customization attempts to the Alabaster theme.And some bad news.....read my post below.To Do
Changelog.Tests.Preview