Give editors the smallest useful set of page choices

An ordinary article may need basic HTML. A repeated campaign body may need typed blocks. A landing-page family may need approved Layout Builder widgets. A genuinely singular product experience may deserve custom Blade.

Capell does not promise an unrestricted blank canvas. The editing surface should stay smaller than the design system, accessibility rules, and performance contract the team must maintain.

Registered LayoutBuilder widgets Reusable sections Frontend-owned output

Compare the four paths Editor path

An editorial team composing structured page sections, media, and revision layers in a Capell workflow.

Learn
/
Content
/
Choose the smallest useful Laravel CMS page builder

Choose the lightest path that covers the editor's real job. Basic HTML handles prose. Structured blocks add typed, reorderable content. Layout Builder adds approved widget composition across named containers. Custom Blade handles a deliberately bespoke public page.

The limit matters: there is no promise of a blank canvas that can invent arbitrary frontend behaviour. Developers define and test the supported components; editors arrange or fill the parts the page family is prepared to render.

A good choice makes the next redesign easier because repeated structure still has one owner.

Four paths, chosen by editing need

Start with basic HTML, add structured blocks for typed repeatable content, use Layout Builder for approved section composition, and reserve custom Blade for a deliberate one-off public experience.

Read the page-building guide

Basic HTML content Use normal rich text for an ordinary page body: headings, prose, lists, and links without editor-managed modules. View this item Reusable content blocks Use typed, reorderable content units when the page body needs more shape than a single HTML field. View this item Layout Builder widgets Use named containers, approved page sections, and assigned assets when editors need controlled section composition. View this item Custom Blade rendering Use a dedicated Blade layout when one page needs a bespoke public implementation. Widgets can use their own Blade views when needed. View this item

Prove the editor freedom against a real page family

Senior Laravel teams usually do not object to editors moving sections around. They object to inheriting a visual canvas where every page can become its own implementation. Capell keeps composition useful by making the editable choices explicit: known containers, approved page sections, assigned content, page-level metadata, and a frontend renderer the application team can test.

Before giving editors a new page-building surface, decide what the team is prepared to support:

which page families need composition instead of a fixed page type;
which components can be reused without weakening accessibility or performance;
which media, forms, search, and package-backed blocks the team is prepared to expose; and
which preview, review, and cache behaviour must run before public release.

That framing turns page building into a product workflow instead of a shortcut around engineering. Editors get speed, but the public site still goes through the same design system, review habits, and deployment discipline as the rest of the Laravel app.

Follow publishing workflow See media handling

Start with the page family Use composition when a family of pages needs controlled variety, not when every page should become a bespoke design surface. View this item Expose supported parts Make the editable blocks match the frontend components your team is willing to maintain, test, document, and improve later. View this item Treat preview as part of the contract Composition should be checked with real content, media, language state, links, and publish effects before stakeholders approve it. View this item Keep visitor output anonymous-controlled The rendered page should contain useful public content and no editor-only context, regardless of how many blocks the page uses. View this item

Next step

Choose the path for one representative page

Choose a page-building path, document why it is the smallest useful option, and follow the page into the publishing workflow.

Approved composition Editors choose sections. Developers own the rendered HTML, CSS, assets, and tests.

Choose a page-building path Price a page-building setup

Role scenarios

What to inspect in Capell Admin

Checks for editing, preview, publishing, recovery, and role boundaries.

Role-based checks drawn from product capabilities and fit boundaries.

Content editor representing this editorial scenario.

Test Capell Admin with an editor

Change a price and heading in one save, then select only the price from activity history. The price should revert while the valid heading edit remains.

The log is not a flat audit dump. It expands nested changes into readable before-and-after rows, then lets editors pick individual changed fields from a past entry and roll back exactly those, with a note for anything that cannot be reverted.

Choose a lighter option when: If teams want to redraw every page by hand, a freeform builder feels quicker. This is for people who publish real content on a regular loop and occasionally need one mistake undone cleanly.

Laravel developer representing this editorial scenario.

Roll back one changed field, not the whole record — what to verify

Change two nested fields, then authorise an editor to revert only one from the activity log. The selected value should roll back with authorisation enforced and the other change preserved.

Inspect this behaviour: It is not just an audit list: the detail view expands nested JSON diffs into readable before-and-after rows, and a selective revert skips fields it is told it cannot touch rather than failing the lot. That is a chunk of review plumbing developers no longer rebuild on every project.

A different tool may fit when: If their admin is one editor pushing low-stakes content, the extra review machinery is more than teams need. The value climbs with the number of people who can hit publish.

Agency team member representing this editorial scenario.

Test Capell Admin with an agency director

Start an impersonation session for a client account, make a support change and end the session. The audit trail should record explicit start, action and stop events under the acting identity.

The demonstration should show: Impersonation is not a silent session swap: it carries its own log name, so the audit trail identifies exactly when the delivery team acted on a client's behalf. Support access is therefore evidenced by explicit start, action and stop events rather than an unexplained session change.

Scope check: A solo client on a simple site may never need agency teams in their seat. This is built for agencies supporting many sites, not the lone editor running one.

Put each change at the narrowest reusable level

Capell keeps editing flexible without hiding where a future change belongs. Editors compose approved parts; developers keep the public renderers, design system, accessibility, performance, and tests in Laravel.

Scroll horizontally to view the full table.

Area	Capell shape	Developer check	Team outcome
Page	The authored content and assigned layout for one URL.	Use it for a page that needs different content or a dedicated layout.	One page changes without rewriting a whole page family.
Page type	The default content structure and editing rules for a repeatable class of pages.	Use it when articles, services, or case studies should start from the same shape.	Repeated content stays consistent as the site grows.
Layout	Named containers, widget placement, and the shared public shell.	Use it when several pages should share the same composition and public layout.	One layout change improves every page assigned to it.
Widget	A reusable rendered unit with its own assigned content and assets.	Use it for a hero, gallery, form, or CTA, with a custom Blade view when needed.	Editors reuse trusted parts instead of creating arbitrary markup.

Manage cookie preferences

Give editors the smallest useful set of page choices

Four paths, chosen by editing need

Prove the editor freedom against a real page family

Choose the path for one representative page

What to inspect in Capell Admin

Put each change at the narrowest reusable level

Capell

How it works

Why Capell

Extensions

View all 78 extensions

Extensions

Extension suites