Super Simple Static Site (ssss)
ssss is a static site generator that uses Jinja2 and Markdown to build fast, lightweight static HTML sites. Scaffold a new site in seconds and run it anywhere.
Installation
Using uv / uvx (Recommended)
Run ssss instantly without manual installation via uvx:
uvx ssss --scaffold
Or install ssss globally as a tool using uv:
uv tool install ssss
Using pipx
Install ssss in an isolated environment via pipx:
pipx install ssss
On Arch Linux, install pipx first if needed:
sudo pacman -S python-pipx
Using pip
Alternatively, if you are in an active virtual environment:
pip install ssss
Usage
Quick start
Run --scaffold to initialize a new project, write starter templates and content, and build the site in one step:
ssss --scaffold
This creates:
ssss.yml # configuration file
site/
source/
index.md # starter content
_templates/
base.html # HTML base layout (Pico CSS included)
default.j2 # default Jinja2 template
build/
index.html # generated output
Init only
Use --init if you only want to create the configuration file and directory structure, without writing any template or content files:
ssss --init
Build an existing site
Once a configuration file exists, run ssss without any flags to build:
ssss
Use a custom config file
ssss --config path/to/custom.yml
Configuration
Configure your site via ssss.yml. The site section defines site-wide variables accessible in all templates and content files:
site:
title: My Site
description: A site built with ssss.
author: Your Name
url: https://example.com
Templates
Templates live in site/source/_templates/. ssss uses staticjinja for rendering.
base.html— base HTML layout, extended by Jinja2 templatesdefault.j2— default template, applied to all Markdown files without a dedicated template__<stem>.j2— template applied only to the content file with the matching stem
The default scaffold includes Pico CSS via CDN — a minimal, classless CSS framework for semantic HTML that makes every page look clean with zero extra effort.
CLI reference
ssss --help
| Flag | Description |
|---|---|
--scaffold |
Create config, directories, and starter files, then build |
--init |
Create config and directories only |
--config, -c |
Path to a configuration file |
--version, -v |
Print the version and exit |
--help, -h |
Show help and exit |
License
AGPL-3.0-or-later © Magnus Åberg (The Commits)
Metadata
Release files for ssss 1.3.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| ssss-1.3.4.tar.gz | 20.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ssss-1.3.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 49.5 kB
Release files / ssss-1.3.4.tar.gz
| Download URL | ssss-1.3.4.tar.gz |
|---|---|
| Size | 20.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
24a46976d67d14d819936084ab14af07883c799c88260bb005cd1fb848fa76fd
|
|
BLAKE2b-256 checksum How to use checksums |
6fd8fbb825e3dbfedf402c51b795c630eaff09f79599065647cb4f9a885392ac
|
| 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 29, 2026.
Transparency logRelease files / ssss-1.3.4-py3-none-any.whl
| Download URL | ssss-1.3.4-py3-none-any.whl |
|---|---|
| Size | 28.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8ad03d8e81433cf4d99c0ed572613a7ac34e5c901877d4e30b59361e946103e5
|
|
BLAKE2b-256 checksum How to use checksums |
2bb357e6ed01af66d1b8fabcac8c59e31e6dd66dcc4c4fdba25eb8b5bae3b0f1
|
| 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 29, 2026.
Transparency log