A Sphinx theme for Renku documentation based on RTD theme.
https://renku-sphinx-theme.readthedocs.io/en/latest/
Installation
Add renku-sphinx-theme to setup.py or requirements.txt used for building your documentation.
Set html_theme to 'renku' in docs/conf.py.
Configure at least description and github_repo in html_theme_options.
Enjoy your beautiful Renku documentation style.
Style (css)
This repo contains a scss file that generates a css file. The css file shouldn’t be manually modified since it’s generated with the scss. Instructions to change and run the scss file are inside it ./renku_sphinx_theme/static/custom.scss.
Renku repo is a better repository for testing style changes.
The easy way of doing this is to go to the renku repo, add a temporary css (custom.css) in the docs/conf.py file and follow this steps:
https://renku.readthedocs.io/en/latest/how-to-guides/contributing/documentation.html
After doing the changes in the temporary css add this to custom.scss in this repository, build this into a css file using the instructions and commit the css and scss files.
Building
To build docs after doing changes, and test things inside this repository
From the base folder… pip install -r docs/requirements.txt
This should be done in case there where changes in fonts or new css files added pip install --editable .
There is no Makefile here but in order to do the “make html” action you should do
cd docs sphinx-build -b html -d _build/doctrees . _build/html
Docs will be built into _build/html... open this files with chrome to see the changes.
Releasing
Create a pull request updating renku_sphinx_theme/version.py to the new version number and CHANGES.rst to list the new changes.
Once the pull request is merged, create a new release.
The release will be automatically be pushed to PyPI.
Changes
0.5.2 (2026-01-19)
This release allows the renku-sphinx-theme to be installed with sphinx-rtd-theme>=3.1.
0.5.1 (2025-12-09)
This release allows the renku-sphinx-theme to be installed with sphinx>=9.
0.5.0 (2025-01-24)
This release makes minor changes for compatibility with sphinx>=8 and sphinx-rtd-theme>=3.
0.4.0 (2025-01-23)
This release bumps sphinx-rtd-theme dependency to make the style compatible with sphinx 7+
0.3.0 (2023-08-14)
Big dependency update.
0.2.3 (2023-04-26)
chore: add dependabot.yml (76baee5)
chore: remove dependency on non-existent compile-scss (617e566)
chore: fix pypi description (23536d9)
chore(deps): update sphinx-rtd-theme requirement (2ca96ca)
chore: bump python version (0dd1fe6)
chore: delete layout.html (5fa988d)
fix: update styles to fix sidebar background leaking into main content (5ab737b)
0.2.2 (2021-07-09)
0.1.0 (2018-05-17)
Initial public release.
Metadata
Release files for renku-sphinx-theme 0.5.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| renku_sphinx_theme-0.5.2.tar.gz | 587.2 kB | With provenance | Details for renku_sphinx_theme-0.5.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| renku_sphinx_theme-0.5.2-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for renku_sphinx_theme-0.5.2-py2.py3-none-any.whl |
Total release size: 1.2 MB
Release files / renku_sphinx_theme-0.5.2.tar.gz
| Download URL | renku_sphinx_theme-0.5.2.tar.gz |
|---|---|
| Size | 587.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9cd0325960d1ba75b3df69920a95777b761b2cb610f258cdce70f2cfcdd0c855
|
|
BLAKE2b-256 checksum How to use checksums |
41a9a7b0fe166863002acc16bd9160bf56b66cd0c9721de750765a8c31eb50ba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 26, 2026.
Transparency logRelease files / renku_sphinx_theme-0.5.2-py2.py3-none-any.whl
| Download URL | renku_sphinx_theme-0.5.2-py2.py3-none-any.whl |
|---|---|
| Size | 580.2 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
5ccd3053cfc9c227b41ec5daaad940b1ef21fc82ad093981a1b236f6e73516fa
|
|
BLAKE2b-256 checksum How to use checksums |
54d3c0409a84f21929c6fcf5e670084fa92ce151892e71a1ff5c9670d89bc02a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 26, 2026.
Transparency logSecurity for renku-sphinx-theme 0.5.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for renku_sphinx_theme-0.5.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 26, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.