Features
Laravel CMS features beyond CRUD.
Start here when you want the basics: what Capell stores, what editors can change, what packages can add, and what operators can inspect after launch. It uses familiar Laravel CMS terms: pages, layouts, preview, media, multi-site, packages, and public output.
Laravel and Filament CMS structure
Visual LayoutBuilder with design guardrails
Package manifests and install impact
Feature groups
Grouped around the work most CMS projects need.
Most Laravel CMS options cover a clean admin, flexible content, plugins, media, multilingual sites, preview, and developer control. Capell turns those into concrete Filament work: page structure, editor workflow, package install impact, publishing checks, cache, and operating controls.
Start
Understand what Capell is.
Capell starts with Filament-powered CMS records: pages, URLs, translations, layouts, media, navigation, reusable sections, and package contracts your team can inspect.
What is Capell?
Authoring
Visual page composition without a free-for-all.
Editors compose approved layouts, widgets, and reusable sections while public Blade keeps a clean rendering contract and does not leak admin state.
LayoutBuilder
Publishing
Preview, approval, scheduling, cache refresh, and rollback.
Publishing work can move through preview links, compare views, review assignments, scheduled releases, static cache refresh, version history, and recovery notes.
Publishing workflow
Packages
Install focused features without plugin mystery.
Packages declare what they add before they are installed: admin screens, migrations, widgets, routes, policies, frontend output, compatibility, support state, and install impact.
Package system
Operations
Keep live sites visible and maintainable.
The package set covers static HTML cache, diagnostics, redirects, migration reports, deployment connections, access gates, forms, search, SEO, analytics, and dashboard signals.
Site operations
Reading path