Docs Map

Use this page as the route map. The docs are intentionally small: each page should answer a busy developer’s next question without sending them through a chain of fragments.

Start Here

Job	Read
Try Capell quickly	Quickstart
Pick the right install path	Install matrix
Decide whether Capell fits	Why Capell
See interactive page experiences	Capell Interactions
Understand the AI-ready path	AI-ready Capell
Learn the core concepts in order	Capell Learn
Install it in a real Laravel app	Install guide
Understand the model	How Capell works
Use the admin panel	Admin
Work on public rendering	Frontend
Build or maintain an extension	Packages
Build an extension from scratch	Build an extension end to end
Decide where a feature belongs	Host, package, or app code
Work in this repo	Development
Debug production behavior	Operations
See a realistic content model	Music store CMS example

Main Docs

Page	Covers
Admin	Filament resources, settings, users, media, recovery shell, dashboard widgets, admin extension points.
Frontend	Site/page resolution, public HTML safety, media output, render hooks, Tailwind assets, server rules, frontend tests.
Packages	Package shape, manifests, service providers, extension points, Actions/Data/settings, admin/frontend contributions, migrations, tests.
Performance	Page cache, fragment cache, model URL cache, ETags, critical assets, lazy hydration.
Operations	Site Health, Lockdown, upgrades, Marketplace connection, install/admin/frontend troubleshooting.
Development	Local repo shape, commands, configuration, seeders, diagnostics, settings migrations.
Reference	Glossary, ERD, credits, package catalogue.

Common Decisions

Question	Read
Which install path should I use?	Install matrix
Does this belong in the host repo, a package, or an app?	Host, package, or app code
Which extension point should a package use?	Extension point chooser
What exact contract/tag/test should I use?	Extension point API reference
Why is my package contribution missing?	Extension troubleshooting
What can public HTML expose?	Public HTML safety contract
How do lazy widgets and fragments work?	Capell Interactions
Which patterns are forbidden?	Do not do this
Where should a new doc go?	Docs ownership rules

URL Preservation

Treat published URLs as durable. When replacing, moving, or rebuilding an old page, keep the new page clean and preserve the old address with a Page URL whose type is Redirect. The redirect record owns the legacy source path and points it at the current page URL, so visitors, bookmarks, inbound links, and search engines still reach the right content without keeping a duplicate page around.

Capell also creates automatic redirect Page URLs when a published page URL changes because a slug or parent path changed. Add a manual redirect when you are creating a new page to replace an existing URL, consolidating old content, or importing legacy routes from another CMS.

For the detailed model, read Page management: URL history and redirects.

Host Packages

Package	Composer name	Package doc
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

First-party add-ons live in the sibling ../capell-packages-4 repository for local development. Use Approved packages for the current package catalogue.

Rules For New Docs

• Update an existing page before adding a new file.
• Link every new doc from this page, a section index, a package overview, or another doc.
• Put historical plans outside the public docs tree.
• Do not keep “moved” stubs unless a published URL needs a temporary redirect.
• Keep extension-point examples beside the reader task that needs them.
• Do not document optional packages as built-in host behavior.
• Public frontend docs must preserve the safety rule: anonymous HTML must not expose authoring controls, model IDs, selectors, signed editor URLs, or package internals.