Layout demo
A fuller demo layout for side-by-side editorial content.
Use the two-column blueprint when two related explanations should be compared, balanced or read in parallel. The left column can carry the reasoning, the positioning or the editorial framing.
This works well for service pages, onboarding content, implementation guides and pages that need a clear “why” next to a concrete “how”.
Feature cards can live inside a column when the explanation needs structure without becoming a separate full-width section.
The right column can carry the practical checklist, the implementation notes or the operational detail. Each column uses the same Bard fieldset, so editors can mix prose with structured sections.
Keep both columns balanced. If one side needs to become much longer, it is usually a sign that the topic belongs in a full-width section below.
Skill bars are useful for compact status, capability or maturity signals inside structured pages.
After the paired columns, the page can return to full-width Bard sections. That keeps the layout useful for comparison or onboarding while still allowing richer content below.
This demo uses the follow-up area for visual explanation, a timeline, selected tags and a final action. In real projects, that same pattern can become a service page, process page or compact documentation hub.
The image-led block should carry more than a decorative pause. It explains why the rigid two-column intro is only the start of the page, not the whole page. Once the comparison has done its job, the full-width content can provide detail, process and navigation without forcing every section into the same split layout.
That makes the blueprint more realistic: structured above the fold, flexible below it and still coherent enough for editors to understand where each content type belongs.
The Timeline set demonstrates process content with logos, labels, timing and internal links.
Selected tags keep the page connected to the same taxonomy vocabulary as articles and videos.
Switch back to a normal page when the content should read linearly, or use the hero blueprint when the opening visual needs to carry the first impression.
