It seems that browsers add some special default styling to header tags :(
I found that for smaller heading tags, like h5 could give more padding then h1 tags...
To fix this, everything should now just recieve the theme standard of 24px bottom margin.
I think we talked about this and never followed through on the next few
release, not sure though. After we release a new version, I think we should be updating
the repository version to something other than the most current release.
The effect would be that the version in the repository would be an
alpha/dev release, and so would be possible to differentiate easily
between 0.5.2 release on PyPI and 0.5.3alpha1 development release from Git.
Right now, we don't follow up with incrementing this version, and so
it's harder to tell the difference. This is mostly for our use in
development.
It adds a small bit of overhead, but is nice and explicit.
This PR updates the version in the repository to 1.0.0alpha1. If we had
adopted this workflow, the progression would have been:
* Release 0.5.2, open PR bumping to 0.5.2 (run `bump2version release` and open PR)
* Follow up 0.5.2 release by bumping to `0.5.3alpha1` (run `bump2version patch` and open PR)
* We add a new feature, bump to `0.6.0alpha1` (run `bump2version minor` and open PR)
* Oops, backwards incompatible change. We bump to `1.0.0alpha1` (run `bump2version major` and open PR)
* We're ready for an rc, bump to `1.0.0rc1` (run `bump2version release` and open PR)
* Maybe we cut another rc after some fixes
* We're ready for final release, bump to `1.0.0` (run `bump2version release` and open PR)
* Follow up the release PR by bumping to the next version (run `bump2version patch` and open PR)
This likely was indirectly broken with da86e4dc62
This commit addes our standard headerlink icon styles to math links aswell, before they had no styling.
Fixes#1189
This should'nt be a breaking change as backward compatibility is preserved so this change could go into 1.0 or wait until 1.1.
I know a lot of users are asking for this so it might be nice to include this in 1.0.
Fixes#1115
* Fix support for logos as urls
Sphinx since 4.0 appears to support html_logo to also contain urls. As
a consequence, the other themes in sphinx appear to be just using the
new logo_url variable, and in this theme that fixes support for it, too.
* Add backwards compatibility and add favicon_url
Co-authored-by: Aaron Carlisle <carlisle.b3d@gmail.com>
* Adds support for explicit tox environments for html4/5
* Adds utility factors for py2/3, for easy access to the system python3
binary
* Adds a noop -qa postfix factor to make it easy to compare against
master or a tag
Many of our PRs have out of date assets, making it hard to test the
latest changes. This will at least throw an error on the PR when build
assets aren't updated.
Many of our PRs have out of date assets, making it hard to test the
latest changes. This will at least throw an error on the PR when build
assets aren't updated.
