Skip to content
pH7x Systems edited this page Jul 18, 2026 · 8 revisions

Stillsite

Stillsite is a multilingual, static-first CMS framework: a content and publishing engine that pairs a real editorial workflow (translations, review states, validation gates) with deterministic static builds.

What makes it different

  • EN is the source of truth; PT-PT, ES, FR and DE translations carry explicit states (missing / outdated / complete) derived from content checksums — edit the source and its translations flag themselves outdated automatically.
  • Validation before publish, always: language parity, unique slugs, media references, alt-text coverage, category rules. Errors block publishing.
  • Deterministic builds: same input → byte-identical output, with hashed asset URLs, full multilingual SEO (canonical, hreflang, Open Graph, JSON-LD, sitemap, RSS) and deployment targets for Azure Static Web Apps, nginx and generic hosts.
  • The database is never the source of truth: portable JSON/Markdown export is. SQLite in development, PostgreSQL in production, same storage contract.
  • Design-agnostic: themes are packages discovered via entry points; the bundled reference theme is just one example.

Documentation

Page What it covers
Getting Started Install, scaffold, seed, build, preview
CLI Reference Every cms command and option
Configuration The stillsite.toml reference
Content Model Articles, pages, sections, media, translation states
Storage Backends SQLite, PostgreSQL, migrations, conformance
Themes Theme packages, template contexts, overrides, islands
Admin Panel Running the admin, accounts, roles, editors
Architecture Layered packages and the ADR index
Deployment Export targets and the demo pipeline
Development and Testing Contributing, gates, test suites

Status

Milestones 0–2 complete (content core, validation engine, deterministic builder, CLI). Milestone 3 (browser admin) is in progress: accounts/access control, shell + dashboard, article and page editors with side-by-side translation are done; media library, workflow/publishing and hardening are next. The detailed plan lives in docs/PLAN.md.

Clone this wiki locally