Skip to main content
Capell home
Install

A Laravel CMS that installs into your Filament app

This headline has history

    Dates are approximate. Changes here affect this browser only.

    Pages, real-theme preview and Page history on the Laravel app you already run, with maintained releases. Create a working site locally in about ten minutes.

    Choose where you are installing Capell
    laravel new my-studio --using=capell-app/starter-kit

    composer require capell-app/installer && php artisan capell:install

    • PHP 8.4
    • Laravel 13.x
    • Filament 5.7.6+ (5.x)
    • MIT-licensed Foundation

    The playground is private to your browser, needs no sign-up and expires after 20 minutes.

    Capell Page editor open on the article “The estuary at first light”, with Pages selected in the Website navigation
    Editor capture unavailable. Open the demo
    The published article “The estuary at first light” at phone width
    Capture unavailable.

    01 / 02 · Article

    The estuary at first light Edited as a Page in Filament, read by visitors on a phone.

    Full-size editor (opens in a new tab) Full-size mobile page (opens in a new tab)

    Restore any earlier version of a Page

    Compare a Page with an earlier version, then roll back. Capell saves the result as a new version, so the history you came from stays where it was.

    Page History covers Pages. It does not rewind other Pages, the media library or the whole site.

    Page History in the Capell admin: the Roll forward to version 3 dialog above the History table
    The same History table in the Capell admin, rolling forward to version 3.

    The estuary at first light Illustrative example Page, not a live application. The labels and messages are the product’s own.

    1. v2 Content updated Edit · first published version
    2. v3 Content updated Edit · hero text rewritten
    3. v4 Content updated Edit · hero text deleted by mistake
    4. v5 Rollback to version 3 Current Restore · version 3 saved again as a new version

    Custom Laravel CMS build compared with Capell Foundation

    A Page model and Filament resource solve the first screen. Capell provides the preview, recovery, upgrade and extension contracts that keep returning.

    Compare the custom work a Laravel team keeps owning with the maintained Foundation contracts Capell adds under the MIT licence.

    Recurring CMS work Custom Laravel and Filament build With Capell Foundation
    Design fields, forms, URLs, redirects and templates again for every new page family.
    Build and maintain a second rendering path that can drift from the public site.
    Decide how revisions, comparison, conflicts and restore should work after an editor needs them.
    Maintain project-specific migration notes, health checks and recovery steps.
    Accumulate application glue or patch the CMS whenever the project grows.

    Tick the rows your next project would otherwise build by hand.

    Editing stays in the admin, out of public pages

    Public pages are rendered from hydrated content only, with no editor controls, field paths or preview state.

    1. Content structure Define repeated page families.
    2. Filament editing Give editors a focused workspace.
    3. Your website Your templates. Your presentation.
    All inside your Laravel application
    Admin · Filament

    Editors, previews, page history and package management.

    render data blocked
    Public · rendered output

    Hydrated content only. No editor controls, field paths or preview state.

    Capell keeps the admin and the public request path apart, so an authoring change reaches visitors only through the page it publishes.

    Capell for agencies, developers, editors and site owners

    Agencies reuse structure across clients. Developers keep their stack. Editors get a guided workspace. Owners avoid paying for the same page twice.

    Choose the role closest to yours

    Reuse the parts clients keep asking for

    Use this path when client sites need a familiar build shape: reusable page types, themes, extension suites, migration reports, house packages, faster handoff, and editor-safe admin controls.

    The demo’s Fieldnotes home Page in the Folio Letterpress theme

    Why this path fits

    • Repeated client work becomes a known delivery system.
    • Themes, page types, and suites give teams reusable launch paths.
    • Handoff is easier because editor boundaries stay consistent.
    • Project-specific CMS behaviour can stay in Laravel packages instead of hidden custom glue.
    • Handover keeps production and entitlements with the client organisation.

    Risks reduced

    • Every client site becoming bespoke
    • Unclear migration and handoff evidence
    • Editors receiving unsafe or inconsistent controls
    • Hidden install impact across client projects

    Recommended next

    Start with the year-five CMS test, then review the agency page, migration path, themes, and suites for repeatable launch packages.

    Keep the public frontend yours

    Use this path when you want to understand Core, Admin, Frontend, packages, render hooks, Actions, data objects, tests, and how custom capability stays package-shaped while Blade or Livewire keep owning the public markup.

    Capell page type definitions

    Why this path fits

    • The CMS stays inside the Laravel application boundary.
    • Optional capability ships through packages instead of core patches.
    • Public rendering remains project-owned and testable.
    • Extension points make install impact clearer before teams adopt a package.

    Risks reduced

    • Custom Filament CMS sprawl
    • Untestable render paths
    • Forking core for project-specific behaviour
    • Package internals leaking into public output

    Recommended next

    Start with the code/editor boundary, then use the developer page, docs, and extension catalogue once the split is clear.

    Publish without breaking the design

    Use this path when the content team needs a Filament workspace for draft, preview, publish, URL, media, and approved page composition without gaining a design-breaking canvas.

    A structured Capell editing screen used to manage Page content and assigned media.

    Why this path fits

    • Editors compose pages from approved widgets instead of freeform templates.
    • Draft, preview, publish, media, and URL workflow live in one workspace.
    • The public site never exposes editor session details or admin structure.

    Risks reduced

    • Editors breaking the brand design
    • Publishing work split across disconnected tools
    • Admin details leaking into visitor output

    Recommended next

    Start with the editor path, then review the code/editor boundary before comparing install options.

    Launch with lower rebuild risk

    Use this path when the business needs safer page structure, clearer package choices, visible operations, and a migration path that does not copy old content problems into the new site.

    The published article “The estuary at first light” at phone width

    Why this path fits

    • Repeated pages share one structure, so future redesigns and content changes are not quoted page by page.
    • Owners can see where content, packages, support, and operations fit.
    • Migration work can separate content, URLs, media, redirects, and Laravel code before implementation starts.

    Risks reduced

    • One-off page drift
    • Unclear pricing and package decisions
    • Broken URL history
    • Copying legacy content problems into the new site

    Recommended next

    Start with the editable-pages path, then review the owner page, platform, pricing, and frontend ownership before choosing install or support.

    CMS features in Foundation and free packages

    Capell Foundation brings the CMS work Laravel teams keep rebuilding, and keeps your application in charge.

    Each of these is part of the free Foundation or a free optional package you choose to add.

    Upgrades

    Rehearse an upgrade before you commit

    Review the upgrade plan before it runs. A reversible upgrade step keeps a recorded rollback path, and capell:theme:doctor checks your theme afterwards.

    Read the upgrade guide

    Packages

    See what a package changes before you install it

    Each package declares what it adds in a readable manifest, so its impact is reviewable.

    See how packages work

    Editing

    Approved sections in every site and language

    Editors compose pages from approved sections, and one install runs many sites and languages, including right-to-left layouts.

    Explore page building

    AI

    Ready for AI tools

    Discovery documents and an agent interface let AI tools read and draft through Capell. People review each change before it is published.

    Explore AI readiness

    Themes and optional packages

    Three theme and demo examples, not customer case studies. Every package installs through Composer and says whether it is free or paid before you install it.

    Browse all themes

    The same Page in six themes.

    Each capture is the demo’s Fieldnotes home Page with the same content record. Only the theme changes.

    Choose a theme for the same Page

    The Fieldnotes home Page in the Foundation theme The Fieldnotes home Page in the Editorial theme The Fieldnotes home Page in the Broadsheet Morning Edition theme The Fieldnotes home Page in the Folio Letterpress theme The Fieldnotes home Page in the Paperdesk Midnight Atelier theme
    Homepage page in the theme-editorial theme, screenshot 1

    Editorial

    Editorial & publishing

    Newspaper-style home page theme with a lead story, shorter stories, opinion and a video row, in a red look or a blue one.

    £29.00 · 12 months

    View demo

    Prices are for 12 months, excluding VAT, with included standard support included. Regular price before promotions.

    Try Capell in a real project before you commit

    Run the install command, or try the editor in a private playground before you install anything.

    Capell Foundation is free and MIT licensed. Check the editor experience, shared page structure and public result against your own requirements.

    Loading footer