Skip to main content
Decision tool

Find Capell packages by project problem

Decision-support tools should qualify the reader, explain the recommendation, and move useful leads towards docs, marketplace, migration, or a founder conversation.

Talk to the founder Read the docs
Core: CMS foundation Package: Installable depth Roadmap: Future platform work
Artwork · Platform map

The platform artwork supports the commercial IA by separating content management, page building, workflow, packages, APIs, operations, and roadmap items.

Commercial V3
Buyer proof

Package Finder proof points.

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

Core Give an ungated starting point. The first useful answer should be visible before asking for an email address.
Package Capture qualified intent. Email capture belongs on downloadable results, extended calculations, or founder-call handoff.
Roadmap Track with PostHog after consent. Tool starts, completions, recommendations, and conversion paths should emit analytics only after consent.
Maturity labels

Package Finder capabilities by maturity.

Package Finder 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 Package Finder.

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