Skip to main content
50% off Capell extensions Claim
Capell home
Live demo

We use cookies for essential features and optional analytics.

Manage cookie preferences

Choose which optional cookies Capell may use.

Essential
Always on

Required for Capell to work — login, security, page rendering.

Analytics

Anonymous usage telemetry to improve editor performance.

Marketing

Personalization for the Capell marketing site.

Cookie policy

Group packages only when they share one rollout

See suite contents Browse individual listings

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.

CMS capture: package inventory Installed capabilities stay inspectable. The real extensions screen makes package ownership, version state, and operational actions visible inside the CMS.
Composer output: core package Capell installs as Laravel packages. Actual composer show output captured from this application, with the local repository path and build reference omitted.
Diagnostic capture: operations health Health checks name the problem and the next action. A real Diagnostics package capture showing setup and operational checks before a release becomes a production incident.

Actual Capell CMS extensions screen showing installed packages, package descriptions, versions, and management actions.

Shared project job Required and optional pieces Individual listing review

A suite is an adoption plan for related packages, not a reason to take the largest set. It earns its place 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.

Suite contents

Compare the work each suite covers

Editorial Foundation A publishing group for teams introducing page composition, reusable sections, navigation, articles, coordinated releases, and discovery together.
  • Layout Builder Page composition
  • Content Blocks Reusable sections
  • Blog Editorial publishing
  • Navigation Menus
  • Publishing Studio Workflow
  • SEO Suite Discovery
6 package areas. Install the pieces your publishing flow needs. Review publishing path
Growth Campaign A campaign group for teams that own the connected path from landing page and form through audience follow-up and reporting.
  • Campaign Studio Campaign pages
  • Form Builder Lead capture
  • Newsletter Audience
  • Insights Reporting
  • GA4 Reports Analytics
  • Email Studio Messaging
6 package areas. Adopt campaign tools without merging their install boundaries. Review growth path
Operations Readiness An operations group when release health, account review, access controls, and migration checks share one readiness programme.
  • Diagnostics Health checks
  • Deployments Release support
  • Login Audit Security
  • Password Policy Access
  • Access Gate Protection
  • Migration Assistant Content moves
6 package areas. Review operational impact before installing. Review trust and operations
Complete Theme Collection The current paid theme collection for teams that genuinely need several design families across projects or properties.
  • Case Study Platform Premium
  • Premium Portfolio Collection Premium
  • Filter Gallery Premium
  • Editorial Serif Premium
  • Dense News Analysis Premium
  • Design Led Magazine Premium
  • Experimental Directory Premium
  • Motion Archive Premium
  • Raw Index Premium
  • Dark Product System Premium
10 theme options. Use the theme gallery to compare current cards. Open theme gallery
Portfolio & Gallery Theme Suite Three paid starting points for teams delivering more than one portfolio, case-study, or gallery experience.
  • Case Study Platform Premium
  • Premium Portfolio Collection Premium
  • Filter Gallery Premium
3 theme options. Use the theme gallery to compare current cards. Open theme gallery
Editorial & Publishing Theme Suite Three paid starting points for teams maintaining distinct long-form, news, and design-publication experiences.
  • Editorial Serif Premium
  • Dense News Analysis Premium
  • Design Led Magazine Premium
3 theme options. Use the theme gallery to compare current cards. Open theme gallery

Make sure the group stays understandable after launch

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.

Browse all extensions Review package model
Name the joined-up job Choose a suite when its packages solve one connected publishing, campaign, operations, or theme-delivery requirement. Browse extensions
Keep independent pieces independent A package that can wait should not become a day-one dependency merely because it appears in the same group. Compare individual packages
Reuse the rollout work For agencies, the saving should come from repeatable discovery, setup, checks, training, and handover rather than forcing identical client sites. Agency path
Check every package contract Before rollout, confirm maturity, compatibility, access, support, upgrade timing, and removal for each included dependency. Review trust
Loading footer