Skip to content
Capell CMS

Glossary

Quick definitions for the terms used across the Capell documentation. Terms are grouped by topic, with links to where each concept is explained in depth.

Editorial model

Section titled “Editorial model”
  • Workspace — an isolated sandbox where edits are staged. One workspace may hold a single page change or hundreds of coordinated edits. See PublishingStudio & Versions.
  • Live — whatever rows are currently published. Every draftable table marks live rows with workspace_id = 0.
  • Draft — a row that exists only inside a workspace, identified by a non-zero workspace_id.
  • Draftable model — any Eloquent model that participates in the workspace system. Draftable models use the BelongsToWorkspace trait. See the Draftable contract.
  • Version — an immutable snapshot of the live manifest at a point in time. Publishing a workspace creates a new version and flips it live.
  • Publish — the atomic flip that promotes a workspace’s draft rows to live. Runs publish-checks (freshness, URL collisions, release windows) inside a single transaction.
  • Rebase — bringing a stale workspace up to date after another workspace has published. See Rebase flow.
  • Rollback — restoring the previous live version after a publish. Also available per-row via EntityRollbackAction.
  • Approval level — an integer count of approvers required before a workspace can publish. Defaults to 2; override via settings.required_approval_levels.

Extension points

Section titled “Extension points”
  • Schema — a Filament field schema class that defines the form for a blueprint, setting, or resource.
  • Schema hook extender — a class that injects extra form fields at named positions in an existing schema, without overriding the full schema. See Extending Capell §4.
  • Render hook — a registered extension that injects HTML into a named location inside a frontend Blade component. See Render Hooks.
  • Event registry — the Admin package’s event bus for subscribing to admin lifecycle events (e.g. afterSave). See Extending Capell §5.
  • Settings Schema Registry — runtime registry of settings form-builder shown on the admin Settings page. See Settings Schema Registry.

Content model

Section titled “Content model”
  • Site — a top-level publishing surface with its own domain(s), languages, and settings.
  • Page — the primary routable content entity. Pages belong to a site and can have one or more language translations.
  • Blueprint — reusable configuration that shapes how content is edited, rendered, and reused. Blueprints can apply to pages, elements, sections, sites, themes, and package-owned content models.
  • Layout / Element — page composition primitives provided by the ContentSections approved package. Not part of core.
  • Backup package archive — a portable archive containing exported content, manifest data, payloads, and integrity checks that can be re-imported through the Recovery Center when capell-app/backup is installed. See Recovery Center.

Infrastructure

Section titled “Infrastructure”
  • Static HTML cache — rendered HTML written to disk and served directly by the web server before PHP runs. See HTML Caching.
  • Render hook context — the RenderHookContext DTO passed to every render-hook extension, exposing the location, the current item, and any extra data the host component provides.
  • Workspace context — the active workspace for a request, set either by the admin switcher (session) or a signed preview link (cookie). Driven by the ResolveWorkspaceContext middleware.