Skip to main content
Colophon

How this Capell site is built

The marketing site should be its own reference customer, showing the CMS records, packages, theme, and public output behind this site.

Read the docs Browse packages
Core: CMS foundation Package: Installable depth Roadmap: Future platform work
Artwork · Developer experience

Generated Recraft artwork for developer experience and extension-boundary pages.

Commercial V3
Buyer proof

Colophon proof points.

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

Core Seeded as CMS pages. Home, Pricing, and commercial pages should be Capell CMS records, not static Blade one-offs.
Package Packages used by the site. Navigation, LayoutBuilder, Frontend, Foundation Theme, HTML Cache, marketplace, and workflow packages should be listed.
Roadmap Editor side-by-side proof. A public editor screenshot next to rendered output can become stronger proof once the launch site is stable.
Maturity labels

Colophon capabilities by maturity.

Colophon 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

Where to go after Colophon.

Read more Why Capell Start with the product story and Laravel boundary. Continue Read more Platform Review the Core, Package, and Roadmap capability map. Continue Read more Pricing Move from evaluation into early access and founder contact. Continue