Build pages you can recover

Before and after

Move recurring CMS work out of the project backlog.

BeforeEvery project invents the contracts around its first Filament resource.

Page families, honest preview, revision ownership, recovery and upgrades become custom application work.

AfterCapell Foundation provides one maintained CMS contract.

Blueprints, real-theme preview, append-only Page history and repeatable upgrades arrive together. Editors recover pages in Filament while developers keep the frontend.

Choose your path

Find the docs by what you are trying to do.

01Start Here

Install Capell, create the first editable page, and verify its preview and recovery path.

02Build A Site With Capell

Move through content types, page management, themes, frontend rendering, and media.

03Understand Capell Core

Learn the page, URL, layout, theme, history, and upgrade contracts before adding optional capabilities.

04Extend Capell

Choose admin, frontend, schema, render hook, or core extension points.

05Build Capell Packages

Author reusable Capell Extensions with manifests, providers, migrations, settings, and tests.

06Explore Capell Extensions

Browse generated extension docs by product area, runtime context, and tier.

System map

How Capell fits together.

Core CMSpages, content, sites, cacheAdminFilament resources, tools, workflowsFrontendrendering, themes, widgets, public safetyExtension Pointsadmin, frontend, schema, hooksCapell Extensionsinstallable capabilities and product areas

Popular next steps

Jump straight to the pages people need most.

Decide If Capell FitsCompare the work a custom Filament build keeps owning with the contracts Capell provides.

Build And Recover Your First PageInstall Foundation, publish a Page, compare its history, and preview page-only recovery.

Content TypesUnderstand how Capell models structured content.

Frontend ThemesWork with public rendering, themes, and frontend presentation.

Admin ExtensionsAdd fields, tools, pages, resources, and widgets to the admin.

Package AnatomyUnderstand the shape of a Capell package before building one.

Source-owned documentation

Docs live next to the code they describe.

Capell public docs are assembled from source repositories so implementation docs stay close to the code: capell-app/capell owns core CMS and core package docs, capell-app/packages owns add-on Capell Extension docs, and capell-app/capell-docs owns this site shell, homepage, navigation, and sync logic. When generated extension docs look wrong, fix the package capell.json, README.md, or public docs/** files in the source repository.