-
Notifications
You must be signed in to change notification settings - Fork 207
MRG: Update docs #279
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
MRG: Update docs #279
Conversation
Old docs: http://sphinx-gallery.readthedocs.io/en/latest/advanced_configuration.html This PR's version: Ready for review/merge from my end. |
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 new order and table of context looks appropriate to me. I don't understand why code-blocks language specification got changed. I myself was never explicit on bash as there is not much syntax highlighting to be made there. I would argue making python and bash blocks explicit.
``doc/conf.py`` file with: | ||
|
||
.. code-block:: python | ||
``doc/conf.py`` file with:: |
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'm just curious. Why do you make bash code blocks now explicit, make the python blocks now un-explicit?
Python is the default, so specifying it wastes space (most modules I've
seen don't bother to specify when it's Python)
|
============= | ||
Configuration | ||
============= | ||
|
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'd start with a short description of what is to come. Something like
"Configuration and customization of sphinx-gallery is done with a dictionary specified in your conf.py
file. A list of the possible keys are shown below, and are explained in greater detail elsewhere 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.
(edited this slightly, just in case you're reading from your email ;-) )
|
||
And some things can be tweaked directly in CSS: | ||
|
||
- ``.sphx-glr-thumbcontainer`` (:ref:`setting_thumbnail_size`) |
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.
did we ever add the more descriptive classes for other objects (e.g. DIVs etc)?
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.
all our CSS is in sphinx_gallery/_static/gallery.css, and every user can always overload that with their own CSS. I left PR #210 forgotten, at some point we shall go back to it.
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.
ah yeah - I meant using more sphinx-gallery-specific classes in the DIVs...I'll comment over in #210!
This looks almost ready to go for me - two quick comments but then I am +1 on merge |
@choldgraf can you see if you're happy with the latest header change? The only remaining question in my mind is is this list of options complete? I saw at least I also saw over in #210 something about |
I think we should merge this, and open an issue about the more general challenge of "how do we ensure that all the functionality of SG (within the conf.py file) is tested and documented"...I think the repo's |
I'll merge this tomorrow AM if nobody protests :-) |
Okay I've also added these to the
... because without the first, I didn't know that the links I added to This should at least make visible other similar errors in the future. |
I'm not sure what the |
No, it just gives more warnings about bad links
|
Ping @choldgraf this should be good to go |
ππ π π |
Closes #276.
Closes #277.
WIP because building freezes on my machine atEmbedding documentation hyperlinks in examples ...
(40%) so I want to see what CircleCI gives, and I still want/need to address #277.