Skip to main content
Build in public

Build Capell in public

Build-in-public content should make early-stage progress legible without turning roadmap exploration into a customer commitment.

Subscribe for monthly updates View roadmap
Core: CMS foundation Package: Installable depth Roadmap: Future platform work
Artwork · Open core

Generated Recraft artwork for the open source and commercial boundary pages.

Commercial V3
Buyer proof

Build In Public proof points.

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

Core Visible founder updates. Monthly notes should explain what shipped, what changed, and which product assumptions are still being tested.
Package Community signals. Package count, contributor activity, discussions, events, and showcase work can build confidence.
Roadmap Public metrics. Waitlist count, package count, production sites, and release cadence should be live-backed before becoming headline claims.
Maturity labels

Build In Public capabilities by maturity.

Build In Public 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 Build In Public.

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