The HTML template overrides mean that you won't be getting improvements to qiskit_sphinx_theme. They also risk breaks because we assume the files are not overridden. It can be valid to override the templates, but should only be done intentionally and with an understanding that increases your maintenance burden.
Likewise, theme.css should not be overridden. Any overrides should go into a dedicated file like custom.css.
These CSS files were not used:
custom.css: not activated, and there is no .toggle element anymore anyways.
style.css: not activated, and its 3 CSS rules are holdovers from the Read The Docs theme.
gallery.css: you don't use sphinx-gallery.
This also:
Adds missing build-backend to pyproject.toml.
Activates jQuery, which is no longer activated by default in Sphinx 6+.
Pins the qiskit_sphinx_theme by minor version. While we try to keep breaking changes to a minimum, we are undergoing big improvements to the theme right now so this gives you better stability.
Warning: I could not get the docs to build locally.
The HTML template overrides mean that you won't be getting improvements to qiskit_sphinx_theme. They also risk breaks because we assume the files are not overridden. It can be valid to override the templates, but should only be done intentionally and with an understanding that increases your maintenance burden.
Likewise, theme.css should not be overridden. Any overrides should go into a dedicated file like
custom.css.These CSS files were not used:
custom.css: not activated, and there is no.toggleelement anymore anyways.style.css: not activated, and its 3 CSS rules are holdovers from the Read The Docs theme.gallery.css: you don't usesphinx-gallery.This also:
build-backendtopyproject.toml.Warning: I could not get the docs to build locally.