Skip to content
Capell CMS

Capell CMS Documentation

Capell is a CMS platform for Laravel teams who need content modelling, editorial workflows, package-led extensions, and production publishing to live in one maintainable system. It gives developers a clean Filament admin foundation without asking them to rebuild the same pages, media, approvals, redirects, domains, and rendering glue on every project.

Capell is built around a small core and a package shelf. The core owns the stable CMS primitives. Packages add focused capabilities such as layout building, blogs, hero content, addresses, forms, AI assistance, and operational tooling. The docs below are pulled from the source repositories so package documentation stays close to the code that ships it.

Install Guide

Get Capell running in a new or existing Laravel application with clean defaults. Install

Feature Map

Review the pages, media, approvals, redirects, domains, and publishing tools in core. Review

Extension Structure

Choose the right package boundary, runtime provider, and extension point before writing code. Extend

Package Shelf

Browse generated package docs by product group, context, and tier. Packages

Documentation Structure

See where docs live, how sync works, and which repository owns each page. Source

What Capell gives you

Section titled “What Capell gives you”
  • A Laravel-native CMS foundation built for applications that already rely on Laravel conventions, queues, storage, authorization, and deployment workflows.
  • A Filament admin experience for editors and operators, with structured resources instead of a loose page builder bolted onto the side.
  • Content primitives that projects keep needing: pages, media, approval flow, redirects, domains, publishing state, and extension hooks.
  • Package-led growth so optional features can stay modular, documented, and testable without bloating the core.
  • Developer-owned extension points for page types, schema extenders, settings, render hooks, and package manifests.

How to read these docs

Section titled “How to read these docs”

Start with the install guide if you are setting up a new project. Use the feature map to understand what the core CMS already owns before adding packages. When you need to customise behaviour, start with the extension structure guide, then move into the specific admin, frontend, package, or core extension point.

The Packages section is generated from package manifests, package READMEs, and public docs in the source repositories. If a package is missing from the shelf, check its capell.json, README.md, and docs/ directory in the package repository.

Source and operations

Section titled “Source and operations”

The public documentation is assembled from:

  • capell-app/capell for the core CMS and core package docs.
  • capell-app/packages, locally synced from capell-4/packages, for add-on package docs.
  • capell-app/capell-docs for this Starlight site, navigation, design, and high-level overview pages.

The docs deploy automatically from GitHub Actions. Updates to this docs repo deploy directly from main; updates in source repositories notify this repo so the latest public package docs are rebuilt and published to docs.capell.app.