Adding Text & Content Sections — Quick Guide

This covers the Content group sections in the page builder (Sanity Studio → your page → Add section → Content) — 14 sections total, the largest group. For the full section catalog including Media, Social Proof, Conversion, and Layout, see docs/sections-reference.md; for the general workflow, see docs/how-to-use-the-sanity-new-features.md.

Which one do I want?

If two of these feel interchangeable, the quick way to tell them apart: Feature Grid and Icon Cards and Pillar Grid all look similar (card grids) — the difference is whether each card needs an icon (Icon Cards), an icon-or-image (Feature Grid), or neither (Pillar Grid).

How to add any of these

1. Open the page in Sanity Studio.
2. Click Add section — these are grouped under Content.
3. Pick the section from the list.
4. Fill in the fields — every field has a description under it in the Studio.
5. Click Publish.

Section-by-section details

Rich Text

• Full paragraph editor: headings (H2/H3), bullet and numbered lists, blockquotes, bold/italic, and links.
• No images and no tables here on purpose — use Full-Bleed Image Band or Image Gallery for images, and Comparison Table for tables.
• Best for: the "read this" parts of a page — explanations, longer copy, legal-adjacent notes.

Feature Grid

• A grid of cards, 2 to 8 of them. Each card has a title, a description, an optional link, and either an icon or an image (your choice per card).
• Columns follow the space available to the section. A narrow Sticky Two-Column area can show three features as 2 + 1; a full-width section uses three across when there is enough room. GTM does not set the column count. Exact thresholds are in the section reference.
• Best for: "here's everything the product does," laid out evenly.

Feature Callout

• One heading, an optional body paragraph, up to 3 optional supporting points (each just a title + short description), and an optional button.
• The left-aligned variant stacks proof points. The centered variant uses a responsive grid that follows the number of points. Both can omit points or the button.
• Best for: a single strong claim you want to slow the reader down for.

FAQ

• A list of question/answer pairs. Needs at least 1 question.
• Answers support the same rich text as the Rich Text section — bold, links, lists.
• Best for: objection-handling near the bottom of a page.

Process Steps

• Numbered steps shown in a row, 2 to 4 of them.
• Each step: a number (you control the format — type "01", "1", or "Step 1", whatever fits the page), a title, and a description.
• Columns: choose how many steps sit side-by-side on wider screens.
• Best for: "how it works" walkthroughs.

Feature Rows

• A plain list of title + description rows, divided by thin lines. No icons, no images — see Feature Rows with Images (in the Media group) if you want a picture per row.
• Optional intro paragraph under the heading.
• Title column width: Narrow or Wide — controls how much space the title takes versus the description.
• Best for: dense, scannable lists of capabilities.

Related Content

• A row of cards linking to existing blog posts or case studies — you search and pick them, you don't write new copy here.
• Needs 1 to 6 items. Titles and images update automatically if the linked post is ever edited — you never have to keep this section in sync by hand.
• Heading defaults to "Related" if you leave it blank.
• Best for: "keep reading" sections that always stay accurate.

Audience Cards

• Image cards for different segments you serve (e.g. "For brokers," "For importers"), 2 to 8 of them.
• Each card: an image, a label, optional bullet points, and a link.
• Columns: 2, 3, or 4 across.
• Best for: "which of these is you?" navigational sections.

Link List

• A vertical list of links with a chevron arrow, at least 1.
• Each link: a label, optional meta text (shown on the right — e.g. a location or department), optional supporting text, and the link itself.
• Best for: resource indexes, open job listings, a list of downloads.

Icon Cards

• Cards with an icon, title, and description, 2 to 8 of them, each with an optional link.
• Icons come from an approved set inside the Studio — you can't upload a custom icon here, which keeps the visual language consistent across the site.
• Columns: 2, 3, or 4 across.
• Best for: feature/benefit summaries where an icon adds more than a photo would.

Bullet Columns

• Two to four labelled bullet lists side by side, e.g. "Capabilities" next to "Outcomes."
• Each column: a label (shown in caps above the list) and its own list of bullet points.
• Needs 2 to 4 columns.
• Best for: side-by-side comparisons that aren't quite a full table.

Pillar Grid

• A grid of title + description cards, 2 to 8 of them, with no icons and no images — plainer than Feature Grid or Icon Cards.
• Columns: 2, 3, or 4 across.
• Best for: summarising a handful of themes or pillars without visual clutter.

Comparison Table

• A hand-built table. You define the column headers first (the options being compared — the first column is always the row label), then add rows.
• Each cell in a row can be either free text or a marker: Yes (tick), No (dash), or Partial.
• Needs at least 1 row.
• This is for an editor-authored table only — it's separate from the pricing/feature-comparison tables elsewhere on the site that pull from the billing system; those aren't editable here.
• Best for: a simple "us vs. them" or "plan A vs. plan B" comparison.

Filterable Cards

• A card grid with clickable category pills above it, so a visitor can narrow down what they see.
• Needs at least 2 cards. Each card has a title, description, optional categories, and an optional link.
• Filtering happens in the visitor's browser — every card is still present on the page (good for SEO), it's just hidden until its category is picked.
• Label for the "no filter" pill — customize what the "show everything" button says (defaults to "All").
• Best for: a resource library, use-case index, or anything with more than ~6 cards where a visitor benefits from narrowing down.

A few tips

• Studio enforces the published item limits. Runtime handling of incomplete or older content depends on the section: Feature Grid can render one valid feature as a fallback, while sections such as Process Steps are omitted below their minimum. Check the section reference's Skipped when column if something isn't appearing.
• No maximum on most sections beyond what's listed — if you add more than 8 to a grid, everything still renders (just a bit tighter), nothing gets silently cut off.
• Related Content stays in sync automatically — it's the one content section where you're not typing copy directly; you're linking to something that already exists elsewhere.
• If a section you added doesn't seem to appear on the live page, check the minimum item count for that section above, or see docs/sections-reference.md for the exact condition.

*Questions or something not covered here? Ask engineering — new section types are easy to add if none of these quite fit what you need.*