-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
html_style works locally but not on ReadTheDocs #885
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
Comments
Here is the code that sets these variables: https://github.com/rtfd/readthedocs.org/blob/master/readthedocs/doc_builder/templates/doc_builder/conf.py.tmpl#L21-L51 -- looks like it might be overriding your custom style. We do this to keep things consistent when using our own theme, but I could probably be convinced to change it for a good reason. |
There definitely should be a way to add some css, preferably an easy one and documented. Current situation is, however, meaning
(1) is not backward compatible, srictly speaking, but since nobody probably uses setting that doesn't work shouldn't cause much trouble. |
I second the motion ... there are a handful of small CSS tweaks I'd like to make in my docs, and either of the suggestions by @Suor would be very welcome. |
I'm running into the same situation here. https://github.com/realestate-com-au/bespin/blob/master/docs/sphinx/conf.py#L17 |
We are now displaying the actually used |
doesnt make any difference to me. html_style is still being ignored. Or better said, when looking at conf.py at build time, you dont override html_style but on the other hand you dont include it in the html source either. |
There is a pattern for this in our docs now: Closing this here as I don't think we'll change this |
I use readthedocs theme both locally and on ReadTheDocs. However,
html_style
has no effect when docs are compiled on the service.By the way, I am just trying to add some custom CSS. Here is my
conf.py
- https://github.com/Suor/funcy/blob/master/docs/conf.pyThe text was updated successfully, but these errors were encountered: