Skip to main content
Capell home
Live demo

We use cookies for essential features and optional analytics.

Manage cookie preferences

Choose which optional cookies Capell may use.

Essential
Always on

Required for Capell to work — login, security, page rendering.

Analytics

Anonymous usage telemetry to improve editor performance.

Marketing

Personalisation for the Capell marketing site.

Cookie policy

Your pages, with an undo you can trust

Editors work in Filament, Laravel's admin framework, with clear screens for the content they manage.

The frustrating part of editing is rarely the writing. It is finding the right place, guessing what a field controls, waiting for a preview, or asking a developer to fix a small mistake.

Each kind of page has a clear shape, with design decisions kept outside the content form. Editors can move from change to checked result without being handed a blank canvas.

Clear page fields Preview before publish Recoverable page history
Plan the editor workflow Open the read-only editor demo
CMS capture · Layout Builder Editors compose approved widgets inside named layout areas. A real Layout Builder capture showing the visual canvas, its container tree, assigned widgets, responsive preview controls, and selected container settings.
Recorded workflow: review Move the draft through review. Frame two keeps the approval state, reviewer context, and next action visible in the actual CMS interface.
Recorded workflow: publish Publish the approved version. The final annotated frame closes the sequence with the controlled publish action in the real product.

Actual Capell Layout Builder showing Main and Sidebar containers, assigned widgets, responsive preview controls, and selected container settings.

An editor's day is made of small, important changes: correct a product detail, replace an image, prepare a campaign page, check a link, schedule a release, and fix something that slipped through. Those jobs should have a clear beginning and end.

Different kinds of pages get different shapes. An article can ask for article content; a product page can ask for product details; a flexible campaign can be assembled from page components the team has already approved. Editors do not have to work out which design controls are safe each time.

A publishing path you can explain

  • Find the page and change fields that match the work.
  • Preview the result in context before it is public.
  • Publish through the process chosen for the site's risk.
  • Compare saved page versions and validate a restoration when needed.

Every Capell site includes drafts, preview, Page History, and validated page restore. The licensed Publishing Studio adds assignments, comments, approvals, scheduling, and coordinated releases. Page History applies to pages; design, accessibility, and code changes still belong with the development team.

The public demo is read-only: editors can open an article, understand its fields, preview it, and inspect Page History and restore validation, but cannot save or restore demo content.

Make the change. Check it. Put it back.

The admin is designed around recognisable tasks: find, update, preview, publish, compare, and correct. The exact fields and components depend on the site, so editors get useful freedom within agreed design rules.

Open the right page quickly Pages, media, links, and reusable content have named places, so an update does not begin with a search through code or old tickets. See the full editor path
Change fields that explain themselves An article, product page, and campaign can each ask for the content that belongs there, without exposing the site's design controls. See the Filament workspace
Build with approved page components Flexible pages can use sections the site team has already designed, so campaigns can move without inventing a new layout each time. See page-building choices
Check the page before visitors see it Preview lets editors check content in context before publication, using the preview rules configured for the site. Open the publishing path
Compare and restore a page version Page History keeps saved versions so an editor can inspect a change, validate a restoration, and move backwards or forwards without deleting the trail. See Page History
Add approvals when the team needs them Publishing Studio can add assignments, comments, approvals, scheduling, and coordinated releases. Those controls are optional rather than part of every editing flow. See team publishing

A publishing day, from edit to recovery

Find the page, change clear fields, preview the result, publish, compare saved versions, and restore when needed. Publishing Studio adds assignments, comments, approvals, scheduling, and coordinated releases for larger teams.

Reusable page structure
Outcome
Edit pages in one consistent admin, without changing how the site looks.
Source
Foundation
Maturity
Released
View evidence
Page history and recovery
Outcome
Compare revisions, roll back, and roll forward from standard Page History.
Source
Foundation
Maturity
Released
View evidence
Team publishing workflow
Outcome
Move drafts through assignments, comments, approvals, scheduling, and release.
Source
Optional package
Maturity
Released
View evidence
AI and agent delivery
Outcome
Track reviewed assistance that keeps editorial decisions explicit.
Source
Roadmap
Maturity
Labs
View evidence
Automation and integrations
Outcome
Track auditable automation that connects content operations to the wider application.
Source
Roadmap
Maturity
Labs
View evidence
Experimentation and growth
Outcome
Track approved campaign and experiment workflows around reusable content.
Source
Roadmap
Maturity
Labs
View evidence
Trust, compliance, and operations
Outcome
Track operational trust and governance capability for long-lived applications.
Source
Roadmap
Maturity
Labs
View evidence
Customer self-service
Outcome
Track managed knowledge and service content alongside the customer experience.
Source
Roadmap
Maturity
Labs
View evidence

Role scenarios

What to inspect in editorial workflows

Prompts for testing everyday editing, preview, recovery, approval, and escalation.

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

Content editor representing this editorial scenario.

Inspect Role Editors from the editor perspective

Change a field on the live page while authenticated, then request the page anonymously. The edit should persist through the normal content model while the public response contains ordinary HTML and no authoring controls.

Read more

Editors can inspect a change in a real preview before it ships, and the readiness check must hold a publish with a broken link or missing alt text. Deliberately trigger both failures and confirm that neither reaches the public site.

Decision note: Some design and structure decisions still sit with developers, on purpose. If teams expect to freely redesign every page themselves, this shared structure will feel like a fence, not a floor.

Editor

Evaluator scenario for an editor

Questions

Questions that come up before publish

How do I know what each field changes?
Each page type can present only the fields that belong to that kind of page, with labels and validation set by the site team. See the editing workspace
Can I see the page before I publish?
Yes. Preview lets you check the result in context before making the change public; the site team configures which route, language, and surrounding page state it uses. Walk through preview
What can I restore after a mistake?
Page History lets you compare, preview, and restore saved page versions. It covers pages; other records may have different recovery rules. See Page History
Can several people approve one release?
Publishing Studio adds assignments, comments, approvals, scheduling, and coordinated releases when the team needs more than the standard page workflow. See team approvals
Loading footer