The Content Model In Four Distinctions

Four pairs of terms are easy to mix up. Each pair below says which one you have on a stock Capell install, which needs an optional package, and where the full guide lives. If another page uses a word differently from this page, the linked guide for that behaviour is the authority.

1. Draft versus workspace

Term	What it is	Needs
Draft	A saved page that visitors cannot see yet. Use Save as draft, review with Preview draft, then publish. A draft is decided by the page’s publishing state, not by a workspace.	Foundation
Workspace	An isolated sandbox in which many edits are staged, reviewed, approved, scheduled and published together as one versioned release.	Publishing Studio

An ordinary draft does not need Publishing Studio. The Foundation publishing state, with its draft, scheduled, published and expired values, is separate from a workspace. When the developer glossary defines Draft by a non-zero workspace_id, it is describing the Publishing Studio storage model, not what the word Draft means on a page in a Foundation install. The admin treats a page as a draft if either condition holds.

Read next: Create your first page for drafts, and the Publishing Studio overview for workspaces.

2. Page versus page type, blueprint and layout

Term	What it is
Page	One routable record on a site. It has translated URLs, content, a publishing state and a layout.
Page type / blueprint	Reusable editing, rendering and behaviour rules. You choose a page type when you create a page; its blueprint decides which fields you see. Admin labels use Page blueprint.
Layout	The theme-scoped template a page renders into. Several pages can share one layout.

Changing a blueprint rule affects every page of that type. Editing a page’s content affects that page.

Read next: Blueprints and How Capell works.

3. Body block versus layout widget

Term	What it is	Needs
Body block	A typed, reorderable unit inside the page body. The page type sets the default content structure; one page can opt out with content_structure_override. Blocks are a body-authoring choice, not a replacement for a layout.	Block Library for the block types
Layout widget	A reusable rendered unit placed in a named area of a layout. Composition follows page -> layout -> containers -> widgets -> widget assets.	Layout Builder
Content section	A reusable, publishable section that is built once in the Sections library and inserted into pages.	Content Sections

Layout Builder and Content Sections are different packages. Layout Builder composes the page structure with containers and widgets. Content Sections provides a library of ready-made sections that editors reuse. Older text that says “Site, Page, Section, Widget” or “Layout Builder is provided by ContentSections” is a simplification of these two packages together, and neither is present on a bare Foundation install. Start with HTML, move to blocks when the body needs typed units, add Layout Builder when you need approved section composition, and use a dedicated Blade layout only for a bespoke page.

Read next: Build a page, which includes the decision diagram.

4. Shared versus page-specific

Before editing, ask what else uses the thing you are about to change.

You change	It affects
A page’s title, slug, body or content_structure_override	That page only.
A page type’s blueprint or default content structure	Every page of that type.
A layout, including its containers	Every page assigned to that layout. Clone the layout first when the change should not spread.
A widget’s reusable content	The widget itself. A widget owns its content and assets, so check where it is used before editing it.
A saved Content Section	Every page that resolves that section.
A page’s assigned layout	That page only.

Changing a published slug or parent changes the public URL; Capell creates a redirect from the old one.

Where each definition is maintained

This page is a reading guide. The wording in the Core glossary and First Session guide is maintained in the Core repository and may lag these distinctions until it is revised there.

GlossaryPlain-English editing terms and developer terms.

Build a pageChoose HTML, blocks, Layout Builder widgets or a custom Blade layout.

First named page exercisePut these terms to work on one About page.