Trust

Trust, security, and operating posture

Trust content should be factual and modest: security reporting, supported versions, compliance posture, incident history, and data boundaries.

Core: CMS foundation Package: Installable depth Roadmap: Future platform work

Buyer proof

Trust proof points.

Trust explains the buyer promise, names the product surface, and keeps shipped core behaviour separate from package and roadmap work.

Core Security reporting path. Disclosure policy, security contact, testing boundaries, and security.txt should be easy to find.

Package Package trust signals. Verified authors, compatibility, support status, advisories, and install impact protect production users.

Roadmap Compliance and uptime. Status history, data residency, uptime metrics, and compliance artefacts should only appear when backed by operations.

Maturity labels

Trust uses visible maturity labels so buyers can tell what is in the CMS foundation, what arrives through packages, and what remains planned.

Core CMS foundation Capell core covers structured records, admin surfaces, URLs, layouts, media, translations, and public rendering boundaries.

Package Installable depth Packages add focused workflow, operations, growth, forms, SEO, search, migration, or marketplace capability.

Roadmap Future platform work Unshipped promises stay labelled until the product and docs prove them.

Internal links