Skip to content

Glossary

Capell Glossary screenshot

Plain-English definitions for everyday content work.

TermMeans
DraftA saved version of a page that visitors cannot see yet. You keep editing until you publish.
Live (published)A page that is visible on the public site.
PublishMake a page live on the public site.
UnpublishTake a live page back down so visitors no longer see it.
SlugThe last part of a page’s URL (for example about-us). Keep it short, lowercase, and stable.
PreviewA private view of how a page will look before it goes live.
RedirectA rule that sends an old URL to a new one so old links keep working.
Alt textA short text description of an image, used by screen readers and when the image fails to load.
Site switcherThe admin control for choosing which site you are currently editing.
MediaUploaded files (images, documents) managed in the Media area.
BlueprintThe reusable definition behind a page, theme, site, element, or section. Admin labels: Page blueprint, Theme blueprint, Site blueprint.
SiteA top-level publishing surface with its own domain(s), languages, and settings.
PageThe primary routable content entity. Pages belong to a site and can have one or more language translations.
WorkspaceAn isolated sandbox where edits are staged. One workspace may hold a single page change or hundreds of coordinated edits.

Implementation-level definitions for package and theme authors.

TermMeans
DraftA page version scoped to a workspace, identified by a non-zero workspace_id.
LiveA page version with workspace_id = 0, served to the public.
Draftable modelAny Eloquent model that participates in the workspace system. Draftable models use the BelongsToWorkspace trait. See the Draftable contract.
WorkspaceAn isolated sandbox where edits are staged. Implemented via the BelongsToWorkspace trait. See PublishingStudio & Versions.
VersionAn immutable snapshot of the live manifest at a point in time. Publishing a workspace creates a new version and flips it live.
PublishThe atomic flip that promotes a workspace’s draft rows to live. Runs publish-checks (freshness, URL collisions, release windows) inside a single transaction.
RebaseBringing a stale workspace up to date after another workspace has published. See Rebase flow.
RollbackRestoring the previous live version after a publish. Also available per-row via EntityRollbackAction.
Approval levelAn integer count of approvers required before a workspace can publish. Defaults to 2; override via settings.required_approval_levels.
SchemaA Filament field schema class that defines the form for a blueprint, setting, or resource.
Schema hook extenderA class that injects extra form fields at named positions in an existing schema, without overriding the full schema. See Extending Capell §4.
Render hookA registered extension that injects HTML into a named location inside a frontend Blade component. See Render Hooks.
Event registryThe Admin package’s event bus for subscribing to admin lifecycle events (e.g. afterSave). See Extending Capell §5.
Settings Schema RegistryRuntime registry of settings form-builder shown on the admin Settings page. See Settings Schema Registry.
Layout (core model)The theme-scoped template structure a page renders into (Capell\Core\Models\Layout). An ordered, theme/site-scoped template record with a status flag, a default flag, and an attached image, selected per page. Part of core.
Layout Builder / Layout block (ContentSections)Page-composition block primitives editors drag and drop, provided by the ContentSections approved package. Distinct from the core Layout model above. Not part of core.
Migration package archiveA portable archive containing exported content, manifest data, payloads, and integrity checks that can be re-imported through the Recovery Center when capell-app/migration-assistant is installed. See Recovery Center.
Static HTML cacheRendered HTML written to disk and served directly by the web server before PHP runs. See HTML Caching.
Render hook contextThe RenderHookContext DTO passed to every render-hook extension, exposing the location, the current item, and any extra data the host component provides.
Workspace contextThe active workspace for a request, set either by the admin switcher (session) or a signed preview link (cookie). Driven by the ResolveWorkspaceContext middleware.