Skip to main content

Capell CMS Glossary

Capell CMS Glossary

Plain definitions for Capell terms such as Core, Admin, Frontend, LayoutBuilder, packages, install impact, operations, and verified domains.

Capell terms in plain language

This page helps you decode the words used across the Capell site before you read architecture, package, or operations detail.

Core
The package layer that stores the main CMS records: sites, pages, URLs, translations, media, layouts, and related content state.
Admin
The Filament-powered editing surface where editors and maintainers manage content, settings, package screens, publishing work, and operational checks.
Frontend
The public rendering layer. It receives approved CMS records and turns them into Blade, Livewire, cached HTML, API-fed output, or a custom project frontend.
Site
A site-scoped publishing context, usually tied to a domain, language setup, navigation, theme defaults, package availability, and operational settings.
Page
An editable public content record. A page usually has URLs, translations, sections, layouts, media, and publishing state.
URL
The public path or redirect attached to a page. Capell treats URLs as CMS records so aliases, redirects, and canonical paths can be managed deliberately.
Translation
The language-specific title, description, body, and metadata for a page or record.
LayoutBuilder
The visual page building layer where editors compose approved rows, columns, widgets, and reusable sections while developers keep the rendering contract.
Section
A structured content block such as a hero, feature grid, CTA, package card, comparison panel, or operations panel.
Widget
A registered renderable element that can place CMS content into a layout container.
Content collection
A reusable record set such as articles, people, resources, locations, case studies, or package records.
Package
A focused Laravel extension that can add CMS capability through migrations, models, Filament screens, widgets, views, routes, config, commands, or marketplace metadata.
Manifest
The package metadata that declares capabilities, install impact, compatibility, support context, and other marketplace trust signals where available.
Install impact
The practical effect of installing a package: admin surface, frontend output, schema changes, commands, settings, permissions, extension points, queues, cache effects, and rollback expectations.
Marketplace
The package catalogue and account layer where users browse, evaluate, access, and review Capell extensions.
Publishing workflow
The path from content edit through preview, review, approval, publish, cache refresh, and rollback context.
Operations
The maintenance surface for cache, redirects, imports, package health, upgrades, broken links, missing translations, incidents, and recovery notes.
Lockdown
An incident control that can close normal public frontend output while preserving trusted admin access and recovery paths.
Multi-site
A Capell setup where one Laravel CMS supports more than one site, domain, language, theme, or site-specific package configuration.
Verified domain
A domain proven by an account user so package access, licences, install receipts, advisories, feedback, and support context can be tied to the right site.

Next steps