Skip to main content
Learn Capell

How Capell Works

Capell is a Laravel and Filament CMS toolkit for teams who want content, rendering, packages, and operations to stay inside their app.

Most Laravel teams eventually rebuild pages, redirects, publishing, SEO, admin workflows, and cache rules in fragments. Capell gives that work a defined home.

Laravel and Filament Package-led capability Clean public HTML
Capell platform map showing Core, Admin, Frontend, packages, and operational boundaries.
Check project fit Install Capell
Fit matrix

Where Capell fits

Capell is not trying to be every CMS. It fits when the team wants content to stay in the app, frontend rendering to remain under project control, extensions to be reviewable, and operations to be visible.

Capell

Content in app
Native
Frontend control
Native
Package trust
Native
Operational health
Native

Strong fit for Laravel-owned CMS work.

Custom Filament admin

Content in app
Native
Frontend control
Native
Package trust
Custom work
Operational health
Custom work

Good start, but repeated CMS concerns become custom platform work.

WordPress

Content in app
Separate app
Frontend control
Depends
Package trust
Depends
Operational health
Possible

Mature CMS, weaker fit when Laravel is the product boundary.

Headless CMS

Content in app
Separate service
Frontend control
Native
Package trust
Depends
Operational health
Custom work

Strong API model, but the Laravel team rebuilds much of the site layer.

Ownership model

Keep your CMS inside Laravel

Capell is not a detached content service. It gives Laravel teams a CMS layer that uses the same codebase, deployment habits, queues, policies, Blade views, tests, and operational checks as the rest of the product.

Your app owns

Routes, Blade, policy, queues

The project keeps deployment, tests, public views, permissions, cache policy, and operational checks in Laravel.

Capell provides

Pages, URLs, languages, layout

Core CMS records, Filament screens, Layout Builder, frontend resolution, and package extension points have a reusable shape.

Editors control

Approved content composition

Editors compose pages from structured records and approved sections without owning the frontend contract.

Avoid scattered CMS glue across plugins, detached APIs, and custom admin hacks.

Keep product code, publishing code, and operational checks close enough to test together.

Package model

Core stays lean; capability arrives through packages

The important boundary is deliberate: Core, Admin, Frontend, and Layout Builder provide the stable CMS path. Growth, publishing, search, commerce, operations, and AI capability arrive through focused packages when a site needs them.

Base

Laravel and Filament

The trusted Laravel and Filament ecosystem remains the bedrock.

Host packages

Core, Admin, Frontend, Layout Builder

The required CMS path from modelled content to editor screens and public delivery.

Optional packages

Publishing, SEO, forms, access

Specialist packages plug in when a project needs deeper workflow, discovery, access, analytics, or theme capability.

Safety membrane

Public output stays public

Capell can support previews and in-page authoring, but public visitors and crawlers should receive ordinary public HTML. Editor controls are an authenticated post-load concern, not something baked into cached markup.

Admin editor

Editor state stays private

Permissions, locks, revision controls, and editor-only tools stay behind authentication.

Boundary

Public output checklist

No editor controls, model IDs, admin URLs, field paths, internal selectors, signed editor URLs, or package markers.

Frontend

Cached public HTML

The same clean markup works for CDNs, crawlers, anonymous visitors, and authenticated admins.

Workflow model

Daily work has a route through the system

Capell is content-first. Editors compose pages from approved records, sections, widgets, and layouts while developers keep public rendering predictable, testable, and fast.

Structure

Page tree and redirects

Content hierarchy, canonical URLs, aliases, and redirect history stay visible.

Composition

Layout Builder

Approved containers and widget assets create responsive pages without copied markup.

Performance

Cache and lazy hydration

Static HTML, fragments, URL caches, and lazy client behaviour are part of the rendering contract.

Target a sub-2.0s LCP budget for public pages before adding heavier interactive packages.
Ecosystem map

The ecosystem grows around clear jobs

Capell packages should be grouped by the problem they solve, not by vague plugin categories. That keeps install decisions legible as the marketplace grows.

Authoring

Publishing Studio, Translation Manager

Editor packages add approvals, previews, scheduling, translations, and rollback without changing public delivery rules.

Discovery

SEO Suite, Site Discovery, Search

Discovery packages keep metadata, sitemaps, robots, search, and cache health near content records.

Interaction

Form Builder, Access Gate, Newsletter

Interaction packages add controlled visitor workflows and account-aware paths.

Operations

HTML Cache, Diagnostics, Deployments

Operations packages make cache, health, deployment, redirects, and upgrade work visible.

Roadmap governance

Roadmap promises stay labelled

Roadmap governance is part of the product story. Public pages should not blur shipped CMS capability, active package work, research, and future ideas.

Now

The core CMS path is the active evaluation surface.

Core, Admin, Frontend, Layout Builder

Shipped

CMS page routing and public rendering

Shipped

Package manifests and install impact

Active

Marketplace browsing and access

Active
Public roadmap labels distinguish shipped capability, active work, planned work, and research.
Evaluate

Choose the next step

If Capell looks like the right shape, start with the install path. If you are still comparing options, use the feature and extension pages to test fit before adopting packages.

Fit

Compare the options

Use the fit matrix and feature catalogue to decide whether Capell belongs in this project.

Install

Prove the base path

Install Core, Admin, Frontend, Layout Builder, and a theme before adding specialist packages.

Packages

Add capability deliberately

Choose packages by install impact, support path, and the job they own.

Operate

Keep public output safe

Check cache, redirects, package health, and roadmap state as part of the same CMS workflow.

Questions

New to Capell?

If you landed here without reading the homepage, start with these questions. Each answer is short, and each one points to the deeper Capell page that explains the idea properly.

What is Capell? Click to open the answer

Capell is a CMS foundation for content-heavy Laravel websites: structured pages, clean admin editing, public delivery, and package-led growth.

Tour Capell
Is Capell meant for designers? Click to open the answer

Designers can work with Capell through themes, approved layouts, visual direction, and frontend systems while the CMS keeps content structure stable.

View themes
Is Capell made for developers only? Click to open the answer

No. Developers get the Laravel architecture, but site owners and editors get the practical value: manageable pages, safer publishing, and visible site operations.

See owner fit
How can Capell help me out? Click to open the answer

Capell gives repeated CMS work a proper home so teams are not rebuilding pages, URLs, layouts, publishing, redirects, cache, SEO, and package logic from scratch.

Explore features
Can I use Capell with my existing website? Click to open the answer

Yes, when the project is a Laravel app or can move into one. Start with a verified install path, then migrate content and packages deliberately.

Read install path
What happens when I install Capell? Click to open the answer

You install the Core foundation, verify Admin and Frontend, add LayoutBuilder and theme output, then choose extensions only when the site needs them.

Read docs
How can we reach you? Click to open the answer

Use the contact path when you need help deciding fit, discussing a project, reporting a concern, or talking through package and marketplace work.

Contact Capell
How can I work with Capell? Click to open the answer

You can install Capell, build a site on it, author packages, create themes, or use it as the CMS foundation for long-running Laravel projects.

Developer path
How can I help Capell? Click to open the answer

Use Core, share feedback, donate, buy first-party packages, purchase marketplace extensions, or author trusted packages for other Capell teams.

Support Capell