Packages for related tasks
Compare the complete job first, then inspect which packages are essential and which can wait. A group does not make every package mandatory.
Do not assume a bundle discount or shared support terms. Use the linked listing for current commercial detail and review each package's production impact.
Choose related packages together
Use suite membership to understand a workflow without assuming every package is necessary.
Suites group related Capell packages so you can examine a broader requirement in one place. The current manifest membership below is the authority for what belongs in each suite. Start from your site's workflow, check the included packages and decide what the application needs to maintain.
A suite is an adoption plan for related packages, not a reason to take the largest set. It fits when the group shares discovery, setup, release checks, training, and support ownership.
Before choosing a suite
- Name the complete job the group solves.
- Separate required packages from pieces that can wait.
- Check each listing for maturity, access, compatibility, support, and impact.
- Confirm any saving or shared support term rather than assuming one.
If the packages do not share a rollout or an owner, adopt them individually.
Check the whole workflow
Understand how the grouped packages contribute to the outcome.
A suite can make related capabilities easier to evaluate, but each package still has a scope and lifecycle. Read the current membership and identify the role of each part. Check configuration and dependencies before assuming the group behaves as one indivisible feature.
Use a representative task to test the package combination. Keep the licence and commercial details tied to the current catalogue rather than treating the grouping as a new entitlement.
Keep adoption focused
Avoid maintaining a capability merely because it appears in a group.
Some projects need a complete suite; others need only a bounded individual package. Compare the current options and the maintenance they introduce. A grouping does not remove the need to own upgrades, permissions and removal consequences.
Record which parts the application uses and how they are verified. That inventory helps a future maintainer understand why the selected combination exists and what an upgrade can affect.
Compare Capell suites
Editorial Foundation Suite A publishing group for teams introducing page composition, reusable sections, navigation, articles and coordinated releases together.
- Layout Builder Included
- Block Library Included
- Navigation Included
- Media Library Included
- Blog Included
Operations Readiness Suite An operations group when release health, account review, access controls and migration checks share one readiness programme.
- Access Gate Included
- Publishing Studio Included
- Migration Assistant Included
- Wordpress Importer Included
- Login Audit Included
- Diagnostics Included
- Filament Peek Included
- Frontend Authoring Included
Growth Campaign Suite A campaign group for teams that own the connected path from landing page and form through audience follow-up and search discovery.
- Campaign Studio Included
- Form Builder Included
- Seo Suite Included
- Search Included
- Url Manager Included
Publishing Workflow Suite A workflow group for teams that need drafting, preview and publishing tools alongside the content they are editing.
- Publishing Studio Included
- Filament Peek Included
- Frontend Authoring Included
- Blog Included
- Navigation Included
Complete Theme Collection The current paid theme collection for teams that genuinely need several design families across projects or properties.
- Theme Portfolio Included
- Theme Platform Included
- Theme Editorial Included
- Theme Blog Included
- Theme Submissions Included
- Theme Catalogue Included
- Theme Magazine Included
- Theme Saas Included
- Theme Curated Included
- Theme Showreel Included
- Theme Onepage Included
- Theme Directory Included
- Theme Minimalist Included
- Theme Brutalist Included
- Theme Awards Included
- Theme Knowledge Included
- Theme Events Included
- Theme Business Included
- Theme Almanac Included
- Theme Bistro Included
- Theme Broadsheet Included
- Theme Folio Included
- Theme Grounds Included
- Theme Paperdesk Included
- Theme Switchboard Included
Portfolio & Gallery Theme Suite Paid starting points for teams delivering portfolio, case-study, or gallery experiences.
- Theme Portfolio Included
- Theme Catalogue Included
- Theme Saas Included
- Theme Curated Included
- Theme Onepage Included
- Theme Directory Included
- Theme Minimalist Included
Editorial & Publishing Theme Suite Paid starting points for teams maintaining long-form, news, and design-publication experiences.
- Theme Editorial Included
- Theme Blog Included
- Theme Magazine Included
Search & Performance Suite A discovery group for teams tuning search visibility, redirects and page-load performance together.
- Seo Suite Included
- Search Included
- Url Manager Included
- Frontend Optimizer Included
Media Workflow Suite A media group for teams organising assets, enrichment and lead capture in one pass.
- Media Library Included
- Media Ai Included
- Tags Included
- Form Builder Included
Migration & Import Suite A migration group for teams moving content in, checking it, and confirming site health before launch.
- Migration Assistant Included
- Wordpress Importer Included
- Media Library Included
- Diagnostics Included
Choose only the packages you need
A coherent suite can save discovery, setup, testing, and training work when its packages support one joined-up workflow. That benefit disappears when optional pieces become unexplained dependencies.
Record the requirement behind each package, the shared release checks, the support owner, and what would happen if one part were replaced. Use individual packages when the work does not share those boundaries.