Roadmap

Roadmap

Sardine CMS is a CMS: the bar for "complete" is what editors already expect from the mature CMSs they come from. The full capability inventory — what ships today, what is partial, and where each gap is scheduled — lives in docs/ROADMAP.md, kept honest next to the code. The headlines:

Shipped (Milestones 0–3)

Content core with per-language translation states, four storage engines, validation engine with per-rule reporting, deterministic builder with full multilingual SEO, theme system, deployment targets, the cms CLI, and the complete browser admin (accounts and roles, editors, media library, workflow, publishing) on AdminLTE with its behaviors. v0.1.x on PyPI; live demo at https://sardine.ph7x.com.

M5 — Editorial completeness (next)

Direct unpublish, scheduled publishing (publish_at, honored at build time), revisions with restore, trash/restore, duplicate-as-draft, per-entry preview, quick list actions, featured content, authorship, media library filters, a users screen, editorial notes.

M6 — Extensibility and adoption

The extension contract (custom content types, custom fields, validation rules, build steps), an explicit menu manager, build-time image derivatives, redirect maps per target, a comments-integration contract for static sites, a JSON content target, importers so existing sites can walk in. (Admin localization already shipped: gettext catalogs in the five site languages, per-user preference.)

M7 — Operations

Email/notifications (password reset, review requests), TOTP two-factor, on-publish webhooks, cms doctor, documented backup/restore and scheduled-build recipes.

1.0

M5–M7 shipped, admin stable, two production deployments beyond the original site, a deprecation policy on PyPI, and every conformance suite documented as a public contract.