Skip to main content
Launch offer: 50% off all Capell extensions and suites while the first-party marketplace catalogue is being shaped. Claim launch offer
Capell home
Cookie preferences

Essential storage keeps Capell secure. Optional analytics stay off unless accepted.

Cookie Policy

CMS capability through Laravel packages

Large CMS products get messy when every feature lands in one core codebase. Capell uses package-led growth so SEO, search, forms, themes, publishing workflow, access gates, diagnostics, and marketplace features can be installed deliberately.

Packages use Laravel conventions: service providers, migrations, Actions, config, tests, manifests, render hooks, and clear extension points.

Composer packages Install impact Marketplace
Capell marketplace evidence surface showing extension manifests, package review, install impact, and public package pages.
Browse extensions Developer experience

What packages can add

The package model matters because not every project needs every CMS feature on day one. Install capability when it is worth owning.

SEO, search, and discovery Add deeper search, SEO audits, sitemap behavior, AI discovery, and public indexing around the same page model. Open detail
Themes and frontend helpers Theme packages can provide layouts, visual presets, assets, and setup paths without taking over the application frontend. Open detail
Publishing workflow Install approvals, releases, controlled documents, previews, or cache operations when the team needs more governance. Open detail
Marketplace operations Author onboarding, package review, installation receipts, and suite management can grow as normal Laravel functionality. Open detail
Questions

Package questions

Packages should make CMS capability easier to review, not harder to trust.

Are packages required for a basic Capell site?

No. Start with the foundation you need. Add packages when SEO, search, workflow, themes, or operations deserve a dedicated capability.

Can agencies create their own packages?

Yes. Repeatable client functionality can live in Laravel packages with manifests, providers, tests, docs, and reviewable install impact.

Does package-led growth mean public output leaks package internals?

No. Package internals, permissions, admin selectors, and editor metadata must stay out of anonymous public output.

Next step

Install CMS features only when they earn their place

The best next step is to browse the extension surface, then compare the developer experience behind package creation and review.

Browse extensions Open developer experience