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

See what changed, who published it, and put it back

The costly part of a growing website is rarely the first launch. It is the campaign that needs twenty pages updated, the new page type that does not match the old ones, and the redesign quote that charges for the same decision again and again.

Repeated pages share a common shape, so the team can improve it once and carry the result across the site.

One change across repeated pages Visible publishing history A handover people can follow
Plan the owner handoff Follow a publishing day
CMS capture: page structure Page families are defined once. A real Filament screen showing the registered page structures editors use instead of rebuilding content rules inside each page.
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.
Public output: cache hit Public HTML stays separate from the admin. This anonymous frontend capture shows the output boundary: cached public HTML with no editor selectors, model identifiers, or signed authoring URLs.

Actual Capell CMS page types screen showing registered content structures and their available editor actions.

Owners feel a poor CMS choice through invoices, delays, and uncertainty. A campaign needs the same correction on twelve pages. A redesign becomes a manual audit. Nobody is sure which account, supplier, or workflow owns the next step.

Capell reduces that uncertainty by giving repeated pages a common shape and editors a clear place to manage them. When a product page, article, or case study needs to change, the team can improve the shared pattern instead of treating every page as a separate build.

Use the year-five questions now

  • Can a redesign update repeated page families in one place?
  • Can an editor preview a change and recover a previous page version?
  • Can an owner see what the team needs before launch and who controls each account?
  • Can a new supplier understand the site's page shapes and publishing responsibilities?

The honest fit matters. A small brochure site with a few settled pages may be better served by a lighter setup. Capell is useful when the site will keep changing and the cost of repeated work, unclear ownership, or a poor handover is already visible.

Where owners feel the difference

A maintainable site makes common change predictable. The team knows which pages move together, who can publish, what changed, and where to look when something needs correcting.

Change a repeated page pattern once When product, article, or case-study pages share a shape, a redesign updates the common pattern instead of reopening every page. See the publishing path
See and recover page changes Page History shows saved versions so the team can compare a change, validate a restore, and move backwards or forwards without erasing the trail. See Page History
Launch within agreed design rules Editors can assemble approved page components for new campaigns while the brand and accessibility rules stay consistent. See the editor view
Give the next team a map Named page types, publishing responsibilities, owner-controlled accounts, and visible checks make the site easier to understand after a supplier or staff change. Review ownership checks
Scope additions before buying them Optional features have a clear purpose, price, support route, and impact the team can discuss before they become part of the site. Compare access and costs
Use less structure for a small, settled site A short-lived brochure site with a handful of stable pages may be cheaper and clearer with a simpler setup. Check whether Capell fits

What owners can expect

Start with clear ownership, safe publishing, and reusable page patterns. Add more process only when the team has a reason for it.

Reusable page structure
Outcome
Keep the website in a client-owned Laravel application that remains maintainable as it grows.
Source
Foundation
Maturity
Released
View evidence
Page history and recovery
Outcome
Recover page changes safely without losing the audit trail.
Source
Foundation
Maturity
Released
View evidence
Team publishing workflow
Outcome
Add controlled review and release workflows when the team needs them.
Source
Optional package
Maturity
Released
View evidence
AI and agent delivery
Outcome
Track safe discovery, validation, preview, and controlled agent-assisted delivery.
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 measurable growth capability while keeping adoption and ownership explicit.
Source
Roadmap
Maturity
Labs
View evidence
Trust, compliance, and operations
Outcome
Track stronger governance and operational evidence without implying a complete compliance programme.
Source
Roadmap
Maturity
Labs
View evidence
Customer self-service
Outcome
Track self-service journeys without splitting customer data into a disconnected CMS.
Source
Roadmap
Maturity
Labs
View evidence
Questions

Questions to settle before you commit

Will a redesign require every page to be changed?
Repeated page families can share one structure, so common design changes are made to that structure. Deliberately unique pages still need individual work. Apply the year-five test
Can we see and undo a page change?
Yes. Page History lets the team compare saved page versions, preview a restoration, and move backwards or forwards. It applies to pages rather than every record in the system. See Page History
What should the next team inherit?
Put the named page families, deliberately unique pages, source and data access, hosting and domain account owners, publishing and recovery owner, optional-package register, release checks, and exit owner into the proposal and handover. Review the ownership checks
When is Capell more structure than we need?
Choose a simpler setup for a small, stable brochure site or a project with little ongoing publishing. Capell fits when repeated pages and future change have real cost. Check the fit guide
Loading footer