About this block

Topic Columns lays a whole FAQ out flat. A centered headline and lede sit above three question groups, each opened by a small uppercase topic label on a hairline rule, with bold one line questions and short muted answers arranged in a two column grid. Nothing folds and nothing hides, so a reader can sweep the section in seconds and land on the answer they came for.

A soft, bordered contact panel closes the section with a short reassurance line and a secondary pill button for anything the grid does not cover. The topics, questions, and answers live in one typed array, so adding a group or reordering questions is a data edit rather than a layout change, and every color comes from theme tokens so the block adapts to light and dark.

When to use

Reach for this block when your answers are short enough to show in full and hiding them behind an accordion would just add clicks. It fits a self serve billing or subscription product well, where buyers arrive with the same predictable questions about payment, data safety, and how fast they can start, and being able to skim every answer at once builds more trust than a tidy list of closed rows.

A natural flow around it on a Marketing Pro page:

Before

• A pricing section to set out the plans the questions refer to
• A testimonials section to back the plans with social proof

After

• A closing CTA to capture the click
• A footer to close the page

What you can display

The obvious fit is billing, security, and getting started questions with four answers each. A few other ways to use the frame:

• Policy summaries. Turn each group into a plain language digest of your terms, privacy, and acceptable use so legal answers stop hiding in PDFs.
• Onboarding checkpoints. Label the groups by week and answer the questions new customers ask at each stage of rollout.
• Feature clarifications. Group questions by product area so evaluators can confirm the details that matter to their team.

Tip: keep every answer to two lines at desktop width. When one grows past that, the detail probably belongs in your docs with a link, not in the grid.