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

Find the repetition before choosing fields

Start with a set of real pages, circle what repeats, and separate required content from optional sections. That exercise produces a useful page type more reliably than copying the first page’s current layout.

Reusable page types Shared layouts No one-off rebuilds
Trace the responsibility map See content management
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.
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.
CMS capture: package inventory Installed capabilities stay inspectable. The real extensions screen makes package ownership, version state, and operational actions visible inside the CMS.

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

Good content modelling is what separates a site that ages well from one that needs a rebuild. The trick is to notice that most pages are variations on a few shapes, then model those shapes once.

Capell uses page types for exactly this. Articles, landing pages, documentation, and product or service pages each become a reusable type with shared fields and layout.

Why this matters

  • The tenth article reuses the first article's structure.
  • A redesign improves every page of a type at once.
  • A new field is added to the type, not to each page.
  • Developers keep the model in code where it can be reviewed.

Start from these examples, adapt them to your content, and the site will keep its shape as it grows.

Model four familiar page families

Each model below is a starting model, not a fixed schema: developers define the blueprint in code, so its fields, groups and validation are reviewed like any other change. An article usually needs predictable editorial fields; a campaign page needs bounded composition; documentation needs durable anchors and hierarchy; a catalogue record needs consistent attributes.

Editorial and blog content Shared fields: title, standfirst, body, author, publish date, cover image. Optional: a related-articles section. Model the URL pattern once at type level and every listing and feed has a stable shape to query, so a new article is content entry, not template work. See content management
Campaign and conversion pages Shared fields: campaign name, headline, standfirst, primary call to action. Optional: approved page sections composed per campaign. The type supplies the bounded set editors may choose from, so a new campaign is assembly inside a reviewed design system instead of a new template. See page building
Structured reference content Shared fields: title, summary, body, the version it applies to, last reviewed date. Optional: a prerequisites block and a related-guides section. The type supplies the heading structure the anchors are built from, so links into a section keep working as the guide grows. See the platform
Catalogue-style detail pages Shared fields: name, summary, description, key attributes, media, primary call to action. Optional: a specification table and a related-items section. The type supplies the shared detail layout, so a hundred records stay consistent and one new attribute reaches all of them at once. Developer path

How reuse keeps cost down

Reusable models are where long-term cost is won or lost. When a page type carries the structure, a new field, a redesign, or an SEO change lands once and applies everywhere, instead of being repeated page by page.

Improve many pages in one edit Shared layouts mean a redesign updates every page of a type, not each page individually. See page building
Add structure without a rebuild A new field on a page type flows to every record of that type, so growth does not mean re-templating. See content management
Plan for the years after launch Reusable models are what keep a site maintainable once campaigns, redirects, and content volume accumulate. Plan year five
Follow the implementation path Developers can build and extend page types using the documented concepts and reference. Read docs
Questions

Modelling questions?

Do I define content types in code or the admin?
Developers define page types and fields in the Laravel codebase, then editors create and manage records for those types in the admin. Developer path
Can one page mix several content shapes?
Yes. A page composes approved page sections, so a landing page can combine editorial, media, and call-to-action blocks within its type. See page building
What happens when I need a new field later?
Add it to the page type and it applies to every record of that type, so adding structure does not force a rebuild. See content management
How does this hold up over years?
Reusable models are the durability story. The year-five page covers why shared structure keeps a site maintainable. Plan year five
Next step

Decide what shares a page type, then define it in code.

If your site is built from repeating shapes, the platform overview and developer path show how Capell page types keep those shapes reusable as the site grows.

Reusable models Define a shape once, then change every page of that type together.

See the platform Developer path
Loading footer