Editor showcase hero landscape

[Editor Demo] Block Tour

A seeded post that walks through hero, rich-text, feature-grid, CTA, FAQ, and testimonial blocks.


Post demo

A blog post can be block-first without losing its legacy body

This is useful when you want editorial framing, pullout structure, or a conversion block before the long-form body starts.

What to inspect in the editor

Check the hero actions, the lead rich-text variant, feature-grid columns, CTA style, FAQ presentation, and testimonial layout on a post instead of a page.

Suggested inspection checklist

Open this post in the editor and compare each field with public output.

Hero

Variant, description, actions

Rich text

Title plus body variant

Grid

Columns and item descriptions

Post CTA

Posts can still end with a conversion block

Use CTA blocks for newsletter signup, next-step navigation, or documentation handoff.

Editorial note

Having both page and post examples matters because the editing context is different.

Editor showcase favicon mark

Content lead

Editor

This post is intentionally concise so the block structure is easy to inspect.

Editor showcase inline graphic

QA lead

Reviewer

Quick post questions

Should every post use blocks?

Not necessarily. This sample only demonstrates that posts support them when useful.

Does the legacy body still matter?

Yes. The body remains valuable for long-form writing and fallback behavior.

Use this post when you want a blog-specific sample that still shows multiple structured blocks above the legacy body.