Workspaces
Pages and reusable sections
Plan page composition with visual cards, reusable section definitions, workflow state, and AI handoff context.
Pages combines page composition with the shared Section library. Plan the order of content on each page, define the reusable sections it needs, and track progress without leaving the workspace.
A definition describes a reusable section, such as Two Column Content. A placement is one use of it on a page, which can have a page-specific title such as Business Services and its own status.
Page nodes come from Structure. Use Structure to change the page map and Pages to plan what each page contains.
Open and build the Section library
Choose Sections in the Pages quick bar. The library opens on the right while the page canvas stays available.
Use New section to create a reusable definition, or create one through a page's add-section menu. Use New group for a labelled divider, then reorder library items with their handles to organise definitions under useful headings.
Definitions include a shared name, pattern preview, purpose, content fields, tags, build guidance, usage count, and their own workflow status. Select a section on a page to open its details directly, or open it from the Section library:
- Content: pattern, name, description, and ordered content fields and groups.
- Settings: the definition's status, additional tags, and build guidance.
Valid edits apply automatically after a short pause and when you close or switch sections. Choose Done to close the editor, then wait for project autosave to show Saved. If validation prevents saving, correct the highlighted fields. Discard pending edits, when offered after an error, discards only the pending changes; it does not undo edits already saved.
Search the library, choose Unused, or filter by status to narrow the list. Unused shows definitions not yet placed on a page. Library filters are independent of the page canvas filters.
Drag a definition onto a page, or select a page and use the definition's quick-add action. The library scrolls independently of the canvas. Close it when you need more room for page composition.
Changing a reusable definition updates linked placements. Its library status remains separate from each placement's status. To change only the label or progress of one placement, use that placement's controls instead.
Deleting a definition requires a second click to confirm. Linked placements are detached as local page sections. Check the usage count and the affected pages before removing a definition that is still in use.
Page cards
Each card represents one page or route. Cards show:
- The page name.
- The number of planned sections.
- Section order from top to bottom.
- Completion progress for sections tagged green.
- The linked library definition name, or a Legacy marker for older embedded data.
New page cards are placed around the current pointer position when possible. Move them freely across the Pages canvas; Skafold preserves manual positions instead of recalculating them on the next import or reload. Use the zoom controls and minimap to navigate a large plan, and page search in the quick bar to find a specific route. The Details control changes how much section information the page cards show. Shortcut 1 opens the page picker.
The Pages quick bar also filters by section status. A page matches when at least one of its sections has the selected status. The whole page composition stays visible, including its other sections. No status includes pages with unstarted sections and empty pages. Combine this filter with page search, or clear the filters to show all pages again. The page filter and library filter work independently.
Add section patterns
Use the add-section control on a page card or between existing sections to insert a section at the exact point it belongs. Search the Patterns library for the section you need, then select its preview. Common patterns appear first. Choose Base blocks for a plain starting layout with no starter fields.
Choosing a pattern creates a new reusable definition and adds its starter fields. To reuse a section you already defined, drag or quick-add that existing definition from the Section library. Choosing the same pattern again creates a separate definition; matching patterns do not link their content.
Patterns cover familiar sections such as headers, footers, FAQs, forms, pricing, testimonials, galleries and team profiles, plus longer content and utility sections:
| Need | Patterns to look for |
|---|---|
| Long-form content | Rich text, blog and editorial articles, contents sidebars |
| Policies and project stories | Terms and policies, case studies, author biographies |
| Resources and contact | Downloads, contact details and maps |
| Listings and states | Events, job listings, search results, empty and not-found states |
Pattern previews are abstract composition hints, not finished UI components or generated copy. Content fields can be edited independently of the preview. Plain Base blocks remain available across these layouts:
Full width sm,Full width md,Full width lg,Full width xl2 cards row,3 cards row,4 cards row,5 cards row2 columns,2 columns 1:2,2 columns 2:1,2 columns 3:53 columns,4 columns,5 columns- Grid patterns such as
2 x 1 grid,3 x 2 grid, and3 x 5 grid
Use compact card rows for shallow strips of cards. Use grid patterns for square or multi-row compositions. Use full-width sizes to indicate vertical weight, from a thin strip through a large hero-like band.
Section names
The section name communicates purpose. Prefer recognised names when one fits:
- Top Nav
- Hero
- Features
- Cards
- Product Grid
- CTA
- FAQ
- Contact Form
- Footer
Choose a more specific name when it helps explain the section, such as Service comparison or Article body. The name does not need to match the pattern. Use notes, field guidance and build guidance for implementation detail.
Content structure
Select a section on a page or open its definition from the Section library. The Content tab brings the pattern and content structure together. Changes to a reusable definition apply to every page using it.
Start with a pattern to get useful fields, then adapt them. An FAQ starts with an eyebrow, title, description and repeating questions and answers. Rename or remove the eyebrow, add a field, or change the group to fit your project: the pattern stays as selected. Starter fields are a starting point, not a requirement.
Use Add field for common fields such as Eyebrow, Title, Short description, Body, Image, and Button / link, or add a custom field. Add group creates a repeating group. The former content-preset dropdown has been replaced by patterns. Existing and imported structures keep their fields until you choose to change them.
Change a pattern
Choose Change pattern in the Content tab and search for a new option. If the structure is empty, a different pattern adds its starter fields. Selecting the current pattern again does not restore fields you deliberately removed.
If fields already exist, Replace content structure? offers three choices:
- Keep existing fields: change the pattern and retain your current fields and their settings.
- Replace fields: replace the structure with the new pattern's starter fields. For a plain Base block, this action is labelled Clear fields because it removes the current structure.
- Cancel: leave both the pattern and fields unchanged.
Review the fields before replacing a structure, especially when the definition is shared across pages.
Edit fields and groups
Fields appear in an ordered list. Drag the handle beside a field or group to change its order; fields inside a group have their own handles. With a handle focused, use the up/down arrow keys, or choose a move action from the row menu. Rename fields and search the type picker. The Required checkbox shows the current requirement: checked means required, unchecked means optional. New fields start required. Add field → Field types also creates a field with a specific type. Expand the field options to add guidance such as “roughly 30 words.”
Cards and other repeating groups contain their own fields. Set an optional item count, then choose what each item needs. Object / field group defines a single set of related fields, such as an address. Both support one level of child fields, with up to 50 fields per list. Repeating groups support counts from 1 to 100; objects have no item count. Leave the count blank when it has not been decided.
Field types and inputs
| Category | Available types |
|---|---|
| Text | Short text, Long text, Rich text, Heading |
| Values and contact details | Number, Email, URL, Phone, Slug |
| Author choices | Checkbox / toggle, Radio buttons, Select dropdown, Checkbox group |
| Dates and appearance | Date, Date and time, Time, Color |
| Media and connections | Image, File upload, Video, Audio, Button / link, Content reference |
| Structured content | Object / field group, Repeating group |
| Custom requirements | Custom |
Choose Custom from the type picker when none of the standard types fits. Selecting it preserves the field's name. Set Custom type name to describe the type you need, such as Geopoint or Product picker, and use the visible Guidance field for context, data shape, and implementation requirements. You can still rename the field independently. The type stays Custom; its name and guidance are included in JSON and Markdown handoffs. Leaving the custom type name blank keeps the requirement undecided.
Checkbox / toggle represents a single true/false value. Radio buttons and Select dropdown represent one selection, while Checkbox group allows multiple selections. Use Add choice and enter a label for each choice. Drag its handle to reorder, or focus the handle and use the up/down arrow keys. Remove a choice with its cross button. Up to 50 choices are supported; leave the list empty if the choices are still undecided. Changing between choice types preserves the choices. Changing to another data type removes them. If a specific CMS value matters, record the requirement in Guidance.
These types describe the required content and intended authoring control. They inform the eventual CMS schema or component data model; Skafold does not generate the finished implementation automatically.
Use guidance for HTML heading levels, numeric ranges, reference target types, media sources, and other project-specific constraints. A Heading field holds text; guidance can specify how it should render. These definitions inform implementation without assuming a particular CMS plugin or generating a complete Sanity schema automatically.
Image fields request an image brief, alt text, and an optional caption in the handoff. Button / link fields request a label and destination. Content structure defines the section's schema: its fields, types, order, required or optional values, and repeating groups. This gives developers and AI tools a more accurate basis for CMS schemas and component data requirements, while guiding content collection. Finished copy is authored separately.
AI Context includes the shared content structure. Republish after editing so trusted AI tools can read the latest requirements. Keep missing facts, unspecified choices, and undecided item counts as open questions.
Notes and additional tags
Edit the pattern and description in Content, and additional tags and build guidance in Settings on the section definition. Each page placement keeps its own title and content workflow status.
Use notes for the section's purpose and handoff context:
Compare the three service tiers and route visitors to the relevant enquiry path.
Use additional tags for quick implementation cues. Prefer content structure fields for copy requirements; older content tags are preserved:
- Content:
title,eyebrow,summary,price,author - Media:
background image,video,gallery,icon - Structure:
grid with cards,card row,split content,accordion - Controls:
search,filter,sort,pagination - Actions:
primary cta,add to cart,submit - States:
empty state,loading state,validation message
Tags are intentionally lightweight. They should help the handoff without turning the planner back into a long form.
Workflow status colors
Select the status control on a library card to open its color palette. Choose a color to make workflow state visible at a glance, or clear the color when no status is needed. The palette closes after a selection, when you click elsewhere, or when you press Escape.
In Pages, individual sections retain their own status controls. Use the completion counter in a page header to set or clear the status of every section on that page. If that page belongs to a multi-selection, the action updates every section in all selected, visible pages. The menu indicates mixed statuses when the sections differ, and the counter continues to count only green sections as complete.
Each bulk status change is one undoable action. Updating page sections leaves the reusable definition and placements on unselected pages unchanged.
The suggested meanings are intentionally flexible:
- Blue: work in progress.
- Purple: review or signoff.
- Amber: needs attention.
- Red: blocked.
- Green: complete.
No explicit status is treated as not started.
Only green counts toward the page-level completion rollup. The other colors remain flexible visual tags, so a team can adapt them to its own stages without changing the page model.
Status is intentionally isolated by context. A reusable definition has its own status in the Section library, while every page placement has its own status. This lets a team track the shared structure through design, build, and approval while separately tracking page-specific content or implementation readiness.
Reusable-by-default sections
All sections use the same reusable model, whether they currently appear once or many times. Typical repeated definitions include:
- Top navigation
- Footer
- Announcement bar
- Repeated CTA
- Shared product teaser
- Reused service proof block
The stable name, notes, tags, structure pattern, and build guidance come from the library definition. A placement can have a page-specific title without renaming that definition—for example, Two Column Content - Business Services can reference Two Column Content.
Older embedded sections can display with a Legacy marker. Check whether a section is linked before expecting a library edit to change it. Matching names alone do not mean two sections share a definition.
Saving, history, and AI Context
Pages has one history for page composition and its shared Section library. Open History in the main header to review changes, save a milestone, or inspect saved pages. Restoring Pages restores both composition and definitions together; it retains Structure graph content and positions. See History, milestones, and restore.
After reviewing saved changes, choose AI Context → Update AI Context when available. The published snapshot includes reusable definitions, content requirements, page placements, and their independent statuses. AI Context is read-only; focused updates happen in the signed-in editor, not through a bulk update file.
Build an accurate section schema
- Define the fields the section needs, with clear names, appropriate types, and an intentional order.
- Mark fields as required or optional, and model repeated content as groups with their own fields and item counts where known.
- Add guidance for content constraints and implementation requirements that the field controls do not express.
- Reuse a definition when its schema and purpose fit; create a distinct definition when the content requirements differ.
- Choose a layout pattern that communicates the intended composition, and review imported fields and groups before handoff.
The goal is a precise section schema that can inform CMS models, component interfaces, and content authoring. Capture the detail needed to implement each section accurately, and use notes and build guidance to record requirements beyond the available schema controls.