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–5)

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 (closed)

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

Shipped: the explicit extension contract and custom fields (ADR-0028), menu manager, responsive image derivatives (ADR-0029), redirect maps, lossless portable dump/import, a controlled foreign-blog adapter (ADR-0030), and design-aware autosave/live preview (ADR-0027).

Reusable-block authoring shipped: the section-kind gallery is now a tested contract — nine bundled kinds (including quote, FAQ, CTA and image gallery), both themes, admin field suggestions and extension-added kinds. The comments contract is fixed (ADR-0031): provider-neutral, consent-first, providers as extensions — implementation lands next, followed by the deterministic versioned JSON content target.

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.