Skip to main content

asterion_sphinx_style

publish pypi

Sphinx style for Asterion public documentation.

A plain sphinx extension, usable in any sphinx project:

# conf.py
extensions = ["asterion_sphinx_style"]

It configures sphinx-rtd-theme rather than shipping a theme of its own, so everything a reader already knows about Read the Docs navigation still holds.

Install

pip install asterion-sphinx-style

If a project already builds its extensions list elsewhere, rebind rather than mutate:

extensions = [*extensions, "asterion_sphinx_style"]

Overriding

Everything is applied only when the project left it unset, so your conf.py always wins:

html_logo = "_static/my-logo.png"   # yours, not Asterion's
html_theme = "furo"                 # the style stops configuring the theme

One caveat: html_theme reads as alabaster when a project has not chosen one, so a project that deliberately picks alabaster is indistinguishable from one that picked nothing, and the style will switch it to sphinx_rtd_theme. Any other theme is respected.

Palette

Sampled from the logo wordmark and AsterionReport.cls. Contrast is against white, WCAG 2.1.

Role Hex Ratio
Brand blue #0832F6 7.51:1 AAA — safe for links and body text
Deep blue #030189 15.33:1 navigation header, admonition titles
Navy #010042 19.45:1 hover and visited states
Alert red #DC0000 5.19:1 danger and error admonitions only

What it does, and what it deliberately does not

Sets, when unset: html_theme, html_logo, html_favicon, and the theme's style_nav_header_background. Adds one stylesheet and its own static directory (appended, so your _static keeps precedence).

It does not repaint the theme's navigation machinery — the current-page tree, expand/collapse states, light/dark alternation. That is a tuned system, and a style that rewrites it ends up fighting the theme on every release. Only surfaces that read as brand are touched.

Design rules

A style is typically installed once and applied to every version of a site, including releases cut years earlier. Three rules follow:

  1. Fill, never clobber — a project's own settings always win.
  2. Absolute paths, appended — packaged assets by absolute path; html_static_path appended to on builder-inited, never assigned.
  3. Never warn — doc builds commonly run under -W, where one warning on one old page fails an entire site.

Versioning

The git tag is the only version that exists; pyproject.toml is dynamic via hatch-vcs. A release is git tag vX.Y.Z && git push --tags.

License

Apache-2.0. See LICENSE. The Asterion Robotics logo and name are trademarks of Asterion Robotics and are not covered by that grant.

Metadata

Release files for asterion-sphinx-style 0.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for asterion-sphinx-style 0.1.1
File Size Uploaded
asterion_sphinx_style-0.1.1.tar.gz 38.9 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for asterion-sphinx-style 0.1.1
File Interpreter ABI Platform
asterion_sphinx_style-0.1.1-py3-none-any.whl Python 3 none any Details

Total release size: 76.3 kB

Release files / asterion_sphinx_style-0.1.1.tar.gz

Download URL asterion_sphinx_style-0.1.1.tar.gz
Size 38.9 kB
Tags Source
SHA-256 checksum
How to use checksums
3fd0e0b0501988269906d67f4a3d13e89b1825eeec63efde7d439a334d9bbe7f
BLAKE2b-256 checksum
How to use checksums
01a6176d6226b87f02f437f08d9d152e57093c09d2889aaab3f3b31e290eb3ed
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.14

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 Jul 27, 2026.

Transparency log

Release files / asterion_sphinx_style-0.1.1-py3-none-any.whl

Download URL asterion_sphinx_style-0.1.1-py3-none-any.whl
Size 37.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
47fdd6995faedfb8f826b56a169b3cbfd323da8d81dfa95222ee0cf34217f44b
BLAKE2b-256 checksum
How to use checksums
2c095202a4404e37458a06e3b5fcf12019ca37ec886de6e1ee1a063bac0138da
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.14

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 Jul 27, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.1 This release

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page