rootiest.com
Source for rootiest.com: the home page of Rootiest Solutions, the catalog of
Rootiest's self-hosted services, its open-source projects, and the Terms of Service that cover all of them.
The site is plain static HTML generated by a small Python script (standard library only). It loads
nothing from other sites: no analytics, fonts, embeds or third-party scripts.
Layout
| Path |
What it is |
site/ |
The web root. Everything in it is published; nothing outside it is. |
site/assets/site.css |
Styles: Catppuccin Latte (light) and Mocha (dark), following the system setting |
site/assets/icons.svg |
Icon sprite of Lucide glyphs (ISC License) |
scripts/sitegen/data/ |
The content as data: services, projects, contacts, the Terms' date |
scripts/sitegen/html/, scripts/sitegen/pages/ |
HTML building blocks and one module per page |
content/legal/ |
The Terms of Service text, as an HTML fragment |
scripts/build.py |
Generates the pages into site/ |
scripts/check.py |
Checks site/: up to date, no broken links, no third-party scripts |
Every .html file in site/ and site/sitemap.xml is generated. Never edit them by hand: edit the
data or content and rebuild. Everything else in site/ (images, icons, robots.txt, .well-known/) is
kept by hand.
Build and check
python3 scripts/build.py # regenerate site/
python3 scripts/check.py # what CI runs
Preview locally with any static server, for example python3 -m http.server -d site 8000.
Updating content
- A service or project: edit
scripts/sitegen/data/services.py or projects.py, then rebuild.
Service hostnames and access levels follow the Rootiest infrastructure services map.
- The Terms of Service: edit
content/legal/terms.html. Every <h2> needs an id (the table
of contents is built from them). Update the updated date in scripts/sitegen/data/legal.py, then
rebuild.
- The privacy notices: they live in the privacy
repository, which publishes them; rootiest.com serves them at
/privacy/. Paths served from other
repositories are listed in MOUNTED in scripts/sitegen/config.py, and scripts/check.py does not
look for them in site/.
- A new glyph: add the Lucide symbol to
site/assets/icons.svg and refer to it by name.
Deployment
Pushes to main on git.rootiest.dev run
.github/workflows/pages.yml, which checks the site and publishes site/ to the Rootiest edge servers'
static web root (pages/rootiest.com), live within a few minutes on both edges. Caddy serves it at
rootiest.com, and serves /privacy/ from the privacy repository's published pages. Its site block also
sets the security headers (including a Content-Security-Policy that allows no scripts), sends missing
paths to 404.html with a 404 status, redirects www.rootiest.com to the apex, and sends /discord,
discord.rootiest.com and join.rootiest.com to the Discord invite (keep that invite in step with
DISCORD_INVITE in scripts/sitegen/config.py).
The GitHub repository rootiest/rootiest.github.io is a
push mirror of this one; nothing is deployed from it.
Social preview image
site/img/banner.png (1200×630, used for og:image) is rendered from scripts/banner.html.
It is always Catppuccin Mocha, since link previews can't follow the viewer's light/dark mode.
The glows are not CSS gradients: scripts/banner-bg.py computes them and dithers them into
scripts/banner-bg.png, because browser gradients band visibly on dark colours.
After editing either file, re-render with Firefox and numpy installed:
python3 scripts/render-banner.py
When the image changes, bump the ?v= number in OG_IMAGE in scripts/sitegen/config.py and
rebuild, so Discord and other sites fetch the new one instead of their cached copy.
License
AGPL-3.0-or-later. Lucide glyphs: ISC License.