Rich Text

A plain container for text. It has no design of its own — no background, no image, no columns. What it gives you is a full-width band with adjustable spacing, into which you drop as many text blocks as the page needs.

Use it for the passages of a page that aren’t a designed section: an introduction, a block of body copy between two feature bands, a disclaimer, a short list. Anything that would otherwise need a purpose-built section for the sake of a couple of paragraphs.

Everything visible comes from the blocks you add. An empty Rich Text section renders as nothing but whitespace.

Settings

Setting	What it does
Section ID	Optional anchor, so a link elsewhere on the page can jump here. Must be unique on the page and written in handle format (our-story, not Our Story).
Top / Bottom padding (mobile)	Space above and below the section on phones. 0–10rem in 0.5 steps, default 3rem.
Top / Bottom padding (tablet)	The same for tablet. Default 4rem.
Top / Bottom padding (desktop)	The same for desktop. Default 5rem.

That’s the whole section. There is no colour or background setting — it’s transparent, and picks up the text colour of the page around it.

Spacing between blocks is automatic

Blocks inside the section are spaced apart on their own. The padding settings control the gap between this section and the ones above and below it, not the gap between a heading and the paragraph under it.

Blocks

Add as many as you like, in any order:

• Title — a heading. Set its text, heading level (H1–H6), size at each breakpoint, and alignment.
• Rich text — a paragraph or several. Supports bold, italic, links and lists, plus its own size and alignment settings.
• Buttons — a row of Button blocks, with control over direction and alignment on mobile and desktop.
• List — a bulleted or numbered list, built from list item blocks.
• Jump Nav — a row of in-page links, for jumping to sections further down the page.

Tips

• Set the heading level to match the page, not the size you want. Size and heading level are separate settings on the Title block. A page should have one H1, and levels below it shouldn’t skip — an H2 followed by an H4 is a structural mistake even when it looks right. Use the size setting to get the look you want.
• Don’t paste styled text from Word or Google Docs. It brings hidden formatting that fights the theme’s own type styles. Paste as plain text and re-apply bold and links in the editor.
• Zero out one side of the padding when stacking sections. Two Rich Text sections in a row give you the bottom padding of the first plus the top padding of the second. Set one of them to 0 rather than halving both.
• Use the Section ID whenever a Jump Nav points here. In-page links need something to aim at, and this is the only place to set it.
• Reach for a designed section first. If what you’re building has an image beside the text, or sits on a coloured band, there is probably a section built for it. Rich Text is for the copy that has no better home.