Docs Map
Capell is a Laravel CMS built on Filament, for teams building applications that outlive their first release. It ships the structure every Filament CMS project ends up rebuilding — page types, layouts, URLs, redirects, previews, undo history and publishing — so the work you do is the work only your application needs.
New here? Start with the verified quickstart, or use the paths below to find your next task.
Choose Your Path
Section titled “Choose Your Path”| I want to… | Start with | Then read |
|---|---|---|
| Evaluate or install Capell | Why Capell | Compare Capell with WordPress and Craft, then choose an install path |
| Build and edit a site | Your first session | Create your first page, then choose a page-building path |
| Build an extension | Build an extension end to end | Host, package, or app code, then the extension point chooser |
| Operate a production site | Going live | Operations, then back up the site and follow the upgrade runbook |
| Maintain the Capell host repo | Development | Local development, then CI and test shards |
Visual Tour
Section titled “Visual Tour”Use these pages to see a workflow before reading its implementation details.
| Screen or flow | Start with | What to look for |
|---|---|---|
| Admin workspace | Admin interface | Dashboard, Pages, Media, Settings, Theme Library, and Site Health. |
| First page authoring | Create your first page | Site and parent selection, URL preview, content editor, draft actions, settings. |
| Theme management | Theme Library | Installed and available themes, diagnostics, customization, preview, and apply. |
| Operations diagnostics | Site Health | Cache status, public-output safety, static generation, optimizer, server checks. |
| Real content model | Music store CMS example | Pages, articles, events, products, artists, and navigation working together. |
Documentation Sections
Section titled “Documentation Sections”| Section | Covers |
|---|---|
| Getting Started | Evaluation, installation, first authoring tasks, core concepts, and interactive build paths. |
| Admin | Content, media, users, settings, themes, the dashboard, and admin extension points. |
| Frontend | Site and page resolution, public HTML safety, themes, media, render hooks, assets, and frontend tests. |
| Packages | Package ownership, manifests, providers, extension points, admin and frontend contributions, migrations, and tests. |
| Performance | Page and fragment caches, model URL caches, ETags, critical assets, and lazy hydration. |
| Package authoring | Platform authoring surfaces and durable package operations. |
| Operations | Site Health, backups, Lockdown, upgrades, Marketplace connection, and production troubleshooting. |
| Development | Host repo setup, commands, configuration, seeders, diagnostics, and CI. |
| Reference | Glossary, relationship maps, architecture diagrams, credits, and package boundaries. |
High-Risk Decisions
Section titled “High-Risk Decisions”| Before I… | Read |
|---|---|
| Move or rename published content | Page management: URL history and redirects |
| How should I build this page? | Build a page |
| Put feature code in the host, an add-on, or an app | Host, package, or app code |
| Change anonymous frontend output | Public HTML safety contract |
| Add or change an extension point | Extension point chooser and unsafe patterns to avoid |
| Change production package or database state | Backups and restore and upgrades |
| Restrict traffic during a suspected compromise | Lockdown |
| Plan a reversible move away from Capell | Export and exit plan |
Published URLs are durable. Capell creates redirect Page URLs when a published page URL changes because its slug or parent path changed. Add a manual redirect when replacing content, consolidating pages, or importing legacy routes.
Host Packages
Section titled “Host Packages”The host repo owns these five packages. Optional add-on behavior belongs to the package that provides it.
| Package | Composer name | Package documentation |
|---|---|---|
| Core | capell-app/core | Core overview |
| Admin | capell-app/admin | Admin overview |
| Frontend | capell-app/frontend | Frontend overview |
| Installer | capell-app/installer | Installer overview |
| Marketplace | capell-app/marketplace | Marketplace overview |
Use Packages and extensions for add-on boundaries and authoring entry points.
Documentation Ownership
Section titled “Documentation Ownership”Update an existing page before adding a new one, and link every new page from the narrowest relevant index. Keep optional-package behavior with its owning package and public frontend safety rules beside rendering guidance.
Use Docs ownership rules to choose the right location and avoid duplicate or orphaned pages. Use the documentation visual standard for screenshots, linked galleries, theme-aware pairs, diagrams, captions, and regeneration ownership.