Skip to main content
Cookie preferences

Capell uses essential storage for sessions, security, and interface preferences. Analytics and marketing storage stay off unless you accept them.

Cookie Policy

Laravel CMS for Complex, Changing Sites

Laravel CMS for medium-large applications

A Laravel CMS built to last.

Capell exists so the CMS site you ship today doesn't become a maintenance nightmare later. It's well-structured Laravel all the way through: tested code, clear package boundaries, and page structure you can extend and rework for years.

Install Capell Explore platform
Architecture /architecture

Editors compose pages from approved layouts, with previews, media, URLs and workflow.

Filament Workflow

Blade, Livewire, Inertia or Vue render the structured data Capell prepares.

Blade Livewire

Search, SEO, forms and themes arrive as Laravel packages, not core bloat.

Search SEO Suite Themes

Not just another CMS

Layered question mark made from Capell CMS architecture panels.
Follow the platform map
Built because custom CMS work keeps repeating

Laravel teams often rebuild the same CMS foundations across products and client sites: pages, URLs, layouts, media, editor workflows, publishing controls, and frontend rendering.

Capell standardises that recurring work so the next site starts with a known shape instead of another custom admin from scratch.

Read the platform map Explore platform
Different because capability arrives as packages

Capell is not trying to ship every CMS feature in one core bundle. Search, SEO, forms, themes, workflows, diagnostics, publishing tools, and project-specific features can arrive through Laravel packages.

That keeps the foundation understandable while giving growing sites a clean path to add more capability.

Browse extensions See themes
Still Laravel where it matters

The public frontend stays in the Laravel project. Developers keep routes, policies, queues, tests, assets, rendering, deployment, and package installs visible in the codebase.

Editors get a clearer workspace without admin concerns leaking into public output.

For developers For editors
Built for long-running Laravel sites

Set up the structure once. Editors run the site from there.

Page types and layouts live in your code, so a change you make once shows up everywhere it should. Editors publish day to day from a Filament admin, and when the site needs search, forms, or SEO, each one installs as a Laravel package.

Explore platform Follow the CMS flow
  1. Structure

    Product pages, case studies, articles, docs, and landing pages share a page type instead of drifting into separate one-off builds.

  2. Editors

    Editors get approved structures, layouts, previews, media, URLs, and workflow without needing to understand the implementation underneath.

  3. Developers

    Blade, Livewire, Inertia, Vue, or a custom stack keeps owning public output while Capell prepares the structured render data.

  4. Growth

    Add search, SEO, forms, themes, workflows, diagnostics, and publishing tools as Laravel packages instead of bloating core.

Change once

A change you make to a page type shows up everywhere it should.

Publish safely

Editors run the day to day from a Filament admin with guardrails.

Package-led CMS capability

Capell keeps the foundation understandable by letting deeper features arrive as focused Laravel packages. That is the core homepage story: add capability without turning every site into a fork of the product.

Browse extensions See themes
Page building and workflow packages Layout Builder, Publishing Studio, blocks, approvals, and reusable content surfaces can be installed when a site needs more editorial control. Explore publishing packages
Search, SEO, and URL capability Search, SEO Suite, URL Manager, tags, feeds, and structured data can be added without making the core CMS carry every concern. Browse discovery tools
Themes belong in the extensions path Themes are important, but the homepage should route to them instead of becoming a carousel. Keep the homepage focused and let themes carry their own detail. See themes
Custom capability stays package-shaped Project-specific CMS behavior can use Capell extension points, service providers, Actions, policies, tests, and normal Laravel deployment practices. Read docs

Choose the next page by what you need

Capell has more detail than a homepage should carry. Use these routes to go deeper without making the first page feel like documentation.

Explore platform Install Capell
See the product shape Use /platform for architecture, fit, comparisons, and the broader capability overview. Open platform
Follow how Capell works Use /learn/platform-map for Core, Admin, Frontend, packages, public output safety, and ecosystem responsibilities. Open platform map
Start the preview path Use /install for preview access, installer expectations, verification, and the handoff into a Laravel project. Open install path
Add CMS capability deliberately Use /extensions for packages, themes, suites, recommender flows, trust signals, and extension detail pages. Open extensions
The proof is in the pudding

Try Capell against a real Laravel project.

Build a page, install an extension, inspect the public output, and see how the CMS boundaries hold. No mock data: your routes, your Blade, your deploy.

Install Capell Open the install path
§ 04 — Quality console

Built for teams who read the code

Capell treats coding standards as product infrastructure. Strict typing, PHPStan, Pest, Actions, data objects, and package-level checks keep CMS features reviewable before they reach editors or public pages.

Release gate

91%

Test coverage across the full Pest suite before release work is trusted.

8

PHPStan level

Capell Core runs PHPStan through the shared configuration before release work is trusted.

91%

Test coverage

Capell package coverage from the full Pest coverage suite.

4044+

Pest tests

Combined test count reported by Capell and Capell package workflows.

17530+

Assertions

Combined assertion count reported by Capell and Capell package workflows.

Release channel

Know what ships now and what comes next

The homepage should prove Capell is active, then route the detail to What's New and the roadmap. Use those pages to see what ships today, what is being worked on, and what is planned next.

Core 01

Shipped

  • Content model & Filament admin
  • Frontend delivery & installer
  • Marketplace + package lifecycle
Packages 02

Now

  • Layout Builder & Publishing Studio
  • Form Builder, Search & SEO Suite
  • Diagnostics & AI Orchestrator
Roadmap 03

Next

  • Deeper docs & demos
  • Community surfaces
  • Comparison pages & clearer pricing