-
-
Notifications
You must be signed in to change notification settings - Fork 192
New website style + docs sorting modifications #2924
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
base: main
Are you sure you want to change the base?
Conversation
src_c/doc/joystick_doc.h
Outdated
@@ -1,25 +1,2 @@ | |||
/* Auto generated file: with make_docs.py . Docs go in docs/reST/ref/ . */ | |||
#define DOC_JOYSTICK "Pygame module for interacting with joysticks, gamepads, and trackballs." | |||
#define DOC_JOYSTICK_INIT "init() -> None\nInitialize the joystick module." |
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.
Some failed checks are complaining about this, they can't compile the joystick module without this defined DOCs. I have no idea of how it works but I think some file or sphynx itself is reading the docs files and generating this entries. I am not sure why it's not finding them, have you run py setup.py docs --fullgeneration
?
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.
py setup.py docs --fullgeneration
is deprecated as stated in docs/README.md
. If I try to run it, I have an error with setuptools when it comes to call setup
at the end of setup.py
.
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.
py setup.py docs --fullgeneration
is deprecated as stated indocs/README.md
. If I try to run it, I have an error with setuptools when it comes to callsetup
at the end ofsetup.py
.
Weird, it works fine for me. Either way those #define need to come back, if you don't know how perhaps you should ask in #contributing (I don't know how either)
After some reviews with Damus, we found that there is a problem a problem of opacity on links with a feature when you hover it, you get some kind of infos about it. |
If you want to change content in the docs, do it in a separate PR. That doesn't belong in this PR. |
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.
As Starbuck mentioned, content changes should be in a separate PR so that this one and those content changes are not both contingent on the other. I also have a few gripes here that I would like to see addressed (or explained if not addressable)
@@ -1,4 +1,4 @@ | |||
.. include:: common.txt | |||
.. include:: ../../common.txt |
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 don't know that I like the relative pathing here. Is there no way around it?
You may want to test the new website style, you just have to edit | ||
``docs/reST/conf.py`` and change the value of ``html_theme`` to ``sphinx_book_theme``. | ||
(Make sure before to install the theme with ``python -m pip install sphinx_book_theme``) |
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.
Isn't this PR supposed to implement the new style? I'm confused by what's intended here
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.
Hello, thank you for the review !
After a big talk on discord, a lot mentionned the idea of making a progressive transition between the old style and the new style. So right now the ideal would be to keep it experimental, and then we make a new PR that will make it default or no.
:glob: | ||
:hidden: | ||
|
||
extra_infos/color_list.rst |
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.
extra_infos
doesn't sound right to me, maybe it should just be extra_info
?
I wanted to check out the style, so I switched the theme in conf.py and installed the additional package. But it fails to build.
|
Manipulate sound sample data. | ||
|
||
:doc:`ref/sprite` | ||
Higher level objects to represent game images. |
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.
Game images? Why not game objects
Yes I didn't update the branch yet. |
For the moment, this version directly uses the theme installed, I did no modification to it. I think I'll be moving it to custom themes so we can do changes on the colors and everything. (maybe next week) |
Hello,
This PR aims to change the website style after years of no modifications. I understand this is considered as a BIG UI change and there is a huge talk on the topic, so I want to make you understand the old theme isn't gone ! Indeed, the goal is to propose for the moment the new style only for static doc generation. Furthermore, the default style when generating docs is the old style, if you want to test the new website style, make sure to read
docs/README.md
, a small paragraph was added.Any feedbacks would be considered as a great opportunity to progress on this idea ! I hope you like the new style.