Skip to main content

sphinx-revealjs-quickstart

A CLI to quickly scaffold presentation projects with Sphinx + sphinx-revealjs.

Usage

uvx sphinx-revealjs-quickstart -p project -a author

To also generate GitHub Pages deployment assets, add --github-pages:

uvx sphinx-revealjs-quickstart --github-pages -p project -a author

This tool also accepts the same arguments as sphinx-quickstart (e.g. -l, -v, --release). See the sphinx-quickstart man page for the full list.

Generated Files

Default

.
├── Makefile
├── build/
└── source/
    ├── _static/
    │   └── css/
    │       └── common.css.jinja
    ├── conf.py
    └── index.rst

With --github-pages

.
├── .github/
│   └── workflows/
│       └── publish-pages.yml
├── Makefile
├── build/
└── source/
    ├── _static/
    │   └── css/
    │       └── common.css.jinja
    ├── _templates/
    │   └── page.html
    ├── conf.py
    └── index.rst

About the Generated Content

  • source/conf.py and source/_static/css/common.css.jinja contain settings and styles that creator (nikkie) usually uses

Customizing highlight_color

The generated conf.py includes an html_context entry:

html_context = {
    "highlight_color": "#5ae08e",
}

common.css.jinja is a Sphinx CSS template that reads this value at build time. Change highlight_color to any CSS color value to update the <strong> tag color in your slides. Remove the entry entirely to omit the strong color rule from the generated CSS.

Customizing OGP metadata (with --github-pages)

When --github-pages is used, the generated conf.py also includes OGP-related entries in html_context:

html_context = {
    "highlight_color": "#5ae08e",
    "twitter_site": "",
    "site_base_url": "",
}

These values are used by the generated source/_templates/page.html to render Open Graph and Twitter Card meta tags:

Key Description
twitter_site Twitter/X account handle (e.g. @yourname) used in twitter:site meta tag
site_base_url Base URL of your GitHub Pages site (e.g. https://yourname.github.io/yourrepo) used in og:url and og:image

Fill in these values in conf.py after scaffolding.

Release files for sphinx-revealjs-quickstart 0.0.4

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

Source distribution (sdist)

Source distribution for sphinx-revealjs-quickstart 0.0.4
File Size Uploaded
sphinx_revealjs_quickstart-0.0.4.tar.gz 7.7 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for sphinx-revealjs-quickstart 0.0.4
File Interpreter ABI Platform
sphinx_revealjs_quickstart-0.0.4-py3-none-any.whl Python 3 none any Details

Total release size: 15.3 kB

Release files / sphinx_revealjs_quickstart-0.0.4.tar.gz

Download URL sphinx_revealjs_quickstart-0.0.4.tar.gz
Size 7.7 kB
Tags Source
SHA-256 checksum
How to use checksums
131cd97ef45cf4f5e4f8444c6382b496e58a9c93225d3081af82c2b98d8777ff
BLAKE2b-256 checksum
How to use checksums
b6117b946b9796201941097f80881a001fe25e93d665238b40e48646e0dc87c1
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 Mar 18, 2026.

Transparency log

Release files / sphinx_revealjs_quickstart-0.0.4-py3-none-any.whl

Download URL sphinx_revealjs_quickstart-0.0.4-py3-none-any.whl
Size 7.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
6b1e468761d58fe932c7e307c9509bf7f71b794c55e434ecbdfde09bab6ebc70
BLAKE2b-256 checksum
How to use checksums
829d194f16584236c1d78165fd322ddae3c23480d5a6755e3c0a902539cc6057
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 Mar 18, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.0.4 This release

2 release files

0.0.3

2 release files

0.0.2

2 release files

0.0.1

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