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

Add CMS capability without patching Core.

A useful extension removes work the team already understands. Open its listing for maturity, supported versions, data and migration impact, visible surfaces, access terms, support, and removal guidance.

Released listings are current adoption options; Beta requires an explicit decision. Unlisted Labs work is product direction, not an install option.

Released or Beta status Visible production impact Public or paid access
Browse current listings Compare grouped adoption
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.

Use the marketplace when a repeatable package can remove a named piece of CMS work. The live listing is the adoption contract: current maturity, compatibility, surfaces, data access, migrations, jobs, support, licence, access, and removal guidance.

Capell Foundation is distributed through public MIT-licensed packages. Paid catalogue packages remain proprietary commercial software and use entitlement-scoped Composer access. Released and explicitly accepted Beta listings are current options; unlisted Labs experiments are not.

Before installation

  • Confirm the package solves a requirement the team already understands.
  • Inspect what changes for editors, visitors, data, deployment, and operations.
  • Check compatibility, support, advisories, access, and retained data.
  • Test the representative workflow and removal path away from production.
Featured extensions

A short starting set

Featured placement is a discovery aid, not a recommendation for every project. Open the full listing before making a package decision.

The Capell Layout Builder arranging page widgets inside a page layout. Page building Layout Builder Reusable widgets, named layout areas, and reviewed bulk layout changes.
Media Library extension artwork. Media Media Library One consistent media field everywhere plus a media-health dashboard.
Capell content collections used to manage structured site navigation. Site structure Navigation Site and language-scoped navigation trees with page references and frontend loading support.
A Capell editorial workflow review before publication. Preview Filament Peek Private previews for unsaved editor changes before content is published.
A successful Capell public HTML cache response. Performance HTML Cache Public response caching with explicit invalidation and observable cache state.
Layered Capell frontend theme concepts. Frontend Foundation Theme A maintained public theme starting point that remains adaptable inside the Laravel app.

A smaller catalogue, reviewed as one Laravel system

First-party, publisher verified, Stable, Beta and Capell reviewed remain separate signals.

Capell reviewed applies only to the exact package release that passed automated checks, AI-assisted analysis and authorised human sign-off. Changed code must pass again, and review reduces risk rather than guaranteeing permanent security.

1 of 45 eligible first-party releases currently carry exact-release review evidence.

  1. No database queries in public views

    Public Blade receives complete hydrated render data without Eloquent, DB access or lazy-loading fallbacks.

    Automated AI-assisted

  2. Declared package boundaries

    Dependencies, contributions, migrations, permissions and removal behaviour must match reachable package code.

    Automated AI-assisted

  3. Exact-release accountability

    Artifact and manifest hashes bind the evidence to one version before a human reviewer owns the release decision.

    Automated AI-assisted Human sign-off
Extension workflow

See package-led capability in practice

Follow package selection, review signals, an Admin workflow, and the explicit extension boundary that keeps project code maintainable.

A narrated walkthrough of Capell's package-led extension model.

Captions (SRT) Read transcript Watch on YouTube Browse extensions

Read the signals before choosing a package

Released and Beta listings are current install candidates when the project's access allows them. Incomplete work stays preview-only, withheld, or unlisted Labs until its marketplace readiness has been assessed.

Compare extension paths Submit an extension
Released or explicitly opted-in Beta Released is the stable adoption path. Beta needs an explicit acknowledgement. Unlisted Labs work is not a current marketplace install. Check the maturity boundary
Compatibility and footprint Check supported Capell, Laravel, and Filament versions alongside migrations, jobs, data access, permissions, and visible output. Review a package lifecycle
Capell Foundation or paid catalogue Capell Foundation packages are MIT-licensed and install without Capell credentials. Paid packages use separate commercial terms and require the matching active entitlement for protected access. Check package access
Support, advisories, and removal Confirm the responsible author, support route, maintenance expectation, security notices, and what happens to retained data when the dependency is removed. See the trust checks

Browse by job

Use a group to narrow the search. The individual listing remains the source for current maturity, dependencies, install impact, support, and access.

Themes
Foundation visual.
surface package manifest route Foundation state install impact Foundation Start here for common page composition, reusable content, navigation, media, articles, and taxonomy. Adopt only the parts the site's publishing model needs. View this item
Publishing Pro visual.
surface package manifest route https://capell.app/extensions/suites state install impact Publishing Pro Publishing Studio and API support coordinated releases and external delivery when those workflows are required. Document Lifecycle remains unlisted Labs work until marketplace readiness is assessed. View this item
Extensions: actual Capell extensions screen showing installed packages and their runtime status.
surface package manifest route https://capell.app/platform state install impact Search and SEO Choose from search and discovery packages when the site needs stronger metadata, crawl controls, broken-link recovery, internal search, or publish-time checks. View this item
Growth and Marketing visual.
surface package manifest route Growth and Marketing state install impact Growth and Marketing Campaign, form, newsletter, analytics, and email packages belong together only when the team owns the complete journey from landing page to follow-up and reporting. View this item
Performance visual.
surface package manifest route https://capell.app/trust state install impact Performance Performance packages help with public-page caching, invalidation, and asset delivery. Review measured route impact before adding them to an already fast application. View this item
Themes visual.
surface package manifest route https://capell.app/extensions/themes state install impact Themes Use a theme as a maintainable starting point for a redesign, then check its real previews, tier, supported content shapes, and replacement path. View this item
Operations and Security visual.
surface package manifest route https://capell.app/trust state install impact Operations and Security Current listings cover diagnostics, deployment, account review, access, translation, and migration work. Privacy Center, Site Monitor, Document Lifecycle, and Exception Reports remain unlisted Labs work. View this item
AI and Automation visual.
surface package manifest route AI and Automation state install impact AI and Automation Current listings cover agent and assisted-media workflows. Agent Delivery, Automation Studio, and Public Actions remain unlisted Labs work until marketplace readiness is assessed. View this item
Sites and Self-service visual.
surface package manifest route Sites and Self-service state install impact Sites and Self-service Current listings add events, payments, live chat, and Shopify commerce. Customer Portal, Knowledge Base, Bookings, and Structured Content Library remain unlisted Labs work. View this item

Turn the job into a package shortlist

The planner connects publishing, discovery, forms, migration, operations, theme, and growth requirements to likely packages. It explains the match; it does not replace maturity, compatibility, access, or impact review.

“Role-based checks drawn from product capabilities and fit boundaries.”

What to inspect before adding packages

Unlisted Labs capabilities being developed as packages

Use these entries to understand possible future capability and to give roadmap feedback. They are not available marketplace installs. Depend only on packages with an approved visible listing and an explicit Released or Beta maturity label.

Publish clean content for AI agents Agent Delivery serves published pages as public-safe JSON manifests and semantic chunks without scraping or exposing authoring state. View this item
Connect workflows without fragile controllers Automation Studio and Public Actions combine package events, registered Actions, validated submissions, signed webhooks, idempotency, durable retries, and dispatch audit. View this item
Accept public input through a safe boundary Public Actions validates and de-duplicates submissions, screens spam, protects outbound requests, signs webhooks, retries delivery, and records every dispatch attempt. View this item
Run experiments inside Laravel Experiments adds server-side targeting, sticky weighted allocation, conversion tracking, and statistically gated winner reports to Capell pages and campaigns. View this item
Build privacy evidence into the site Privacy Center records consent, policy acceptance, retention rules, and access, export, or deletion requests as a queryable system of record. View this item
Control document versions and acceptance Document Lifecycle publishes content-hashed document versions and records which actor accepted which version and when. View this item
Give customers one self-service home Customer Portal assembles billing, documents, registrations, gated resources, newsletter preferences, and support requests contributed by installed packages. View this item
Ship a structured help centre Knowledge Base adds collections, cacheable documentation routes, reader feedback, sanitised HTML, and typed AI-readable payloads without authoring leakage. View this item
Reuse real business content Structured Content Library stores portable case studies, testimonials, team members, services, FAQs, resources, partners, locations, and logos. View this item
Monitor the site beyond application errors Site Monitor tracks uptime, SSL certificates, domain expiry, and incidents as part of the same operational platform. View this item

Next step

Adopt one package from a real requirement

Carry a short list into the live catalogue and verify the listing before changing the application.

If no listed package solves the job cleanly, keep the work in project code or wait. A larger catalogue is not a reason to install more dependencies.

Open the live catalogue Check access and pricing
Loading footer