Skip to content

Package Product Groups

Capell groups first-party packages by customer-facing value. Composer names remain focused and stable; the product group controls how packages appear in catalogues, pricing, and marketplace screens.

Free baseline packages:

PackageComposer name
Blogcapell-app/blog
Navigationcapell-app/navigation
Tagscapell-app/tags
Addresscapell-app/address
Media Librarycapell-app/media-library
Frontend Authoringcapell-app/frontend-authoring
Foundation Themecapell-app/foundation-theme
Theme Agencycapell-app/theme-agency
Theme Corporatecapell-app/theme-corporate

Tags and Media Library are Foundation packages because taxonomy and media management are normal CMS expectations. Redirect management is built into Capell Core/Admin rather than shipped as an add-on package.

Product groupBundle keyPackages
Capell CommercialcommercialAIOrchestrator
Capell FormBuilderform-builderFormBuilder
Capell Publishing Propublishing-proPublishingStudio
Capell OperationsoperationsMigrationAssistant, Diagnostics, Login Audit
Capell GrowthgrowthInsights, CampaignStudio
Capell CommunicationscommunicationsEmail Studio
Capell Search & SEOsearch-seoSEO Suite, Search; AI Discovery, llms.txt, page Markdown, crawler policy, readiness audits
Capell ThemesthemesCommerce Theme, Healthcare Theme, SaaS Theme

Every first-party package should expose:

{
"productGroup": "Capell Themes",
"tier": "premium",
"bundle": "themes"
}

Use stable bundle keys in code and marketplace syncs. Use product group names in user-facing UI and docs.

Do not rename Composer packages simply because they sell together. For example, capell-app/migration-assistant, capell-app/diagnostics, and capell-app/login-audit stay separate packages but group together as Capell Operations.

Email Studio uses Capell Communications because transactional email is a distinct operational surface. It supports Growth and FormBuilder workflows, but it should not be sold as a newsletter or campaign audience tool.