Trace every page decision to one clear owner
When content rules are spread across models, resources, templates and add-ons, a change becomes a search for the real owner. Capell assigns each concern to Core, Admin, Frontend or a package.
Use the four boundaries below to see what Capell maintains, what stays in your application, and how one Page moves from definition and editing to public response and recovery.
Trace the Core, Admin, Frontend, and Packages boundaries through one maintainable Laravel CMS.
Watch on YouTubeA CMS becomes expensive when nobody can say where a page rule belongs. Capell makes the four owners visible, then follows one page through the running application so the boundary can be judged from real work.
The four parts of a Capell application
Core
Pages, URLs, revisions, translations, media, layouts, and extension points form the durable content model.
Filament Admin
Approved fields, media, composition, preview, and Page History give editors a focused publishing workspace.
Your frontend
Blade, Livewire, Inertia, Vue.js, or a custom Laravel stack turns hydrated content into clean anonymous HTML.
Packages
Composer-installed packages add manifest-declared capability without moving project rules into Core.
One page, from draft to live
Define the page and its type
Core connects the page to a reusable type, URL, translation, and layout before composition begins.
See page-building pathsEdit and preview in Filament Admin
Editors change approved fields and composition, then preview the real page shape before the public version changes.
Follow the publishing workflowPublish with recovery visible
Page History records the change and supports validated rollback or roll-forward; Publishing Studio adds coordinated review when installed.
Watch draft to rollbackServe the public response
The Laravel application returns clean visitor HTML through its own frontend, cache policy, URLs, metadata, and navigation.
See public deliverySee what a package adds
A package can add a bounded feature such as scheduled access while its manifest, install impact, public surface, and removal path stay inspectable.
Trace the package lifecycleChoose the decision you need to make
Start with the change that has to remain maintainable: a repeatable page family, a higher-risk publish, a public response, a discovery requirement, a growing set of sites, or a new package. The right detail page gives the team a smaller evaluation surface and a direct route back to the platform map.
Next step
See the platform boundary before you install it
Use the read-only demo to follow content from the admin to the published page, then decide whether the split suits your team.
In the demo, find a page structure, inspect Page History, open the public result, and identify which capability comes from a package. Use the route map above for the deeper evaluation before installation.
What is included, optional, or planned
Foundation capability ships with the standard stack. Optional capability is named only when its approved Marketplace record is publicly available. Roadmap work links to its current public item.
Reusable page structure
- Outcome
- Own structured pages, layouts, and public rendering inside the Laravel application.
- Source
- Foundation
- Maturity
- Released
Page history and recovery
- Outcome
- Compare, restore, and roll forward page changes without erasing history.
- Source
- Foundation
- Maturity
- Released
Team publishing workflow
- Outcome
- Add isolated workspaces, review, approvals, scheduling, and atomic releases.
- Source
- Optional package
- Maturity
- Released
AI and agent delivery
- Outcome
- Track safe discovery, validation, preview, and controlled agent-assisted delivery.
- Source
- Roadmap
- Maturity
- Labs
Automation and integrations
- Outcome
- Track auditable automation that connects content operations to the wider application.
- Source
- Roadmap
- Maturity
- Labs
Experimentation and growth
- Outcome
- Track structured experimentation and measurement without presenting Labs work as shipped.
- Source
- Roadmap
- Maturity
- Labs
Trust, compliance, and operations
- Outcome
- Track operational trust and governance capability for long-lived applications.
- Source
- Roadmap
- Maturity
- Labs
Customer self-service
- Outcome
- Track customer-facing account capability integrated with the application the customer owns.
- Source
- Roadmap
- Maturity
- Labs