Skip to main content
Marketplace

Capell marketplace for trusted CMS packages

The marketplace hub should feel like due diligence, not a plugin shelf. Package adoption should be visible before anything changes in production.

Core: CMS foundation Package: Installable depth Roadmap: Future platform work
Artwork · Marketplace trust

The marketplace artwork gives the hub a product-specific visual system for package discovery, compatibility, author trust, and install intent.

Commercial V3
Buyer proof

Marketplace proof points.

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

Package Show install impact first. Listings should expose Composer name, capability labels, schema impact, routes, widgets, policies, and public output.
Package Make author trust visible. Verified authors, support status, security contact, reviews, install counts, and compatibility should be close to the CTA.
Roadmap Package author economics. Revenue share, payout model, author tiers, and featured placement need a clear public promise before launch.
Maturity labels

Marketplace capabilities by maturity.

Marketplace 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.