Some people might add the example code to the top of the file, in which case `alabaster` will overwrite later. Also, localization is important but not so important for people using this for the first time. My concern is that many people end up with Alabaster on RTD deployments after Sphinx 4 made it the default.
Co-authored-by: Aaron Carlisle <carlisle.b3d@gmail.com>
type="text/javascript" is unnecessary and even discouraged by the
specification: “Authors should omit the type attribute instead of
redundantly setting it.”
https://html.spec.whatwg.org/multipage/scripting.html#attr-script-type
It causes the validator to raise warnings, too.
Signed-off-by: Anders Kaseorg <andersk@mit.edu>
Sphinx 4.x moves javascript and css declarations to `script_files` and `css_files`. This patch fixes duplicatd link and script tags when using sphinx4
Sphinx 4.x changes the default setting of html_codeblock_linenos_style to 'inline' and deprecates `html_codeblock_linenos_style`. The css for `.hll` to make the hightling span the full line cause the line number and code to be split on seperate lines. I could not get the highlight to span the full line so it was removed completely. I also made line numbers not selectible by the user.
This changes also adds the needed changes to the tox testing enviorment alhough, sphinx4 is not officially released to pypi yet. You will need to test these changes locally using: `pip install git+https://github.com/sphinx-doc/sphinx@master`
* Cleanup: Sass formatting
This patch addresses some sass formatting to make the code easier to read:
- Use leading zeros on decimals less than 1
- Use parentheses around math for css propeties with multiply arguments
- Spaces after commas in arguments
In the future it would be nice to automatically format this with a tool like style lint.
* Revert Extra Tabbing
* Add back missing line
* Add whitespace back
* Fix whitespace 2
* Setup: Require docutils<0.17'
Docutils 0.17 changes some rendering of properties, until support is added we should probably pin to use an older version.
I may not be a bad idea to keep a pinned version in the theme to prevent this issue in the future.
* Release 0.5.2
Include a changelog and bump versions
* Fix changelog
Co-authored-by: Aaron Carlisle <carlisle.b3d@gmail.com>
Use `page_source_suffix` instead of checking `source_suffix`
Since we now require sphinx 1.6 we can cleanup this old workaround for old sphinx versions.
Sphinx 1.6 is required for de76c03824 we also do not test against versions lower than 1.6 so we should safely drop it.
This is similar to #1076 and #1075 but less strict
* Docs: Add text before config api type information
This makes it more clear what the confval is for without having to read through the type information.
This matches usual sphinx autodoc behavior.
* Only use one space above headings
* npm: Add a few missing package fields
This fixes these warnings when running `npm install`:
```
npm WARN sphinx_rtd_theme@0.5.1 No repository field.
npm WARN sphinx_rtd_theme@0.5.1 No license field.
```
* 0.5.2
* Revert version bump
* Revert version bump
This changes non PR builds on rtd to use the local theme and not the old 0.4.3 theme. We want our docs to show what the theme looks like based on the current release, not an old version.
The sets the right padding the same as the first level.
The current padding is too large and varies between toc levels.
Now, the right padding is the same between all levels and only the left padding changes
Currently, Nav buttons to expand the menu are a bit small and do not match the link text.
This makes the font size and line-height match between the text and icon.
