-
Notifications
You must be signed in to change notification settings - Fork 43
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
Use stable Sphinx for building the "default" images #114
Comments
I'm fine with making a split on this site -- I'd still prefer to have a single landing page though for this; and have different Sphinx versions be presented under a dropdown or something. :) |
Agreed. With #115, I've switched to using the stable Sphinx release for themes.
Let's track this separately. I've opened #116 for this. |
I'd love to see this 😍 . I like the idea 💯 |
Hi! I'm opening this issue because of this comment from @pradyunsg
(from #113 (comment))
I think it's really good to build all the themes with the latest beta release from Sphinx because it helps developers to know if their theme is going to work once that version of Sphinx becomes stable. However, from a Sphinx's user perspective, it's not good to be pointed to this site to decide which theme to use and realize that some of them are broken.
Besides, from a marketing perspective, it's not good for the Sphinx ecosystem in general, to refer to this site as the canonical place to find really good themes and decide which one to use, but find there are some that are broken.
That said, I think it would be awesome if we could have two different versions of this site:
I went ahead and tried this using Read the Docs:
I'm happy to rebase the commits and create a PR if you consider this work useful. If you like this work, but want to keep using GH pages to host the both versions, we can figure it out how to do it there as well. Let me know.
The text was updated successfully, but these errors were encountered: