Skip to main content
Capell home
My account

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

Personalization for the Capell marketing site.

Cookie policy

Content models for real sites

Most sites are built from a small number of repeating shapes: articles, landing pages, documentation, and product or service pages. Capell models each as a page type so the tenth article or landing page reuses a known structure instead of becoming another one-off build.

Reusable page types Shared layouts No one-off rebuilds
Capell content model surface showing article, landing page, documentation, and product page types sharing reusable structure.
See the platform See content management

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.

Four shapes most sites need

Defining a shape once means a redesign or a new field improves every page of that type at once. The examples below are the patterns teams reach for most often when modelling content in Capell.

Editorial and blog content A title, body, author, and media model that powers news, blog posts, and field notes from one reusable type. See content management
Campaign and conversion pages Composed from widgets you approve so marketing can assemble campaign pages without a bespoke template each time. See page building
Structured reference content Sectioned, linkable pages that keep guides and reference material consistent as the docs set grows. See the platform
Catalogue-style detail pages A repeatable detail shape for products, services, or case studies, with shared fields and layout across the set. 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.
Can one page mix several content shapes?
Yes. A page composes widgets you approve, so a landing page can combine editorial, media, and call-to-action blocks within its type.
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.
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.
Next step

Model content once, reuse it for years.

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 improve every page of that type together.

See the platform Developer path

Capell learning journey

Step 1 of 4: Learn

Guides for evaluating, planning, and operating Capell.

Keep moving through Foundations

Fit, architecture, content model, and output quality.

Loading footer