Filament CMS Extension Suites

Combine focused packages without hiding their boundaries

This page helps users understand package suites as guided paths, not bundled mystery boxes.

Extension suites show which independent Capell packages make sense together for a familiar job, such as publishing articles, managing campaigns, improving search, or running migrations.

Each package still has its own Composer name, migrations, capabilities, support path, and install impact. The suite is a recommended path, not a bundled black box.

Suites are navigation, not camouflage. They help users find a sensible bundle of related packages, but they should never hide which package owns which table, admin screen, command, public route, widget, or support obligation.

That keeps the install path honest. A team can adopt the whole suite, start with one package, or remove a piece later without losing sight of the underlying package boundaries.

Next steps

• Return to package groups for the overview.
• Create an extension when suite work repeats.
• Review upgrades before changing package sets.