Advanced Layout Syntax

This page is about writing the modules correctly, not about visual theory.

The most common failures are not "the layout feels weak." They are:

• wrong field names
• the wrong colon character
• missing columns in row-based modules
• the wrong module name
• missing required fields that make the whole block disappear

The base pattern

Every advanced module must use a triple-colon block:

:::module-name
field: value
:::

Row-based modules can also carry a bracket title:

:::metrics[Core numbers]
Retention | 42% | Readers finished more often after the structure cleanup | accent
:::

The rules that fail most often

1. Fields must use the English colon

Correct:

title: Put the conclusion first

Wrong:

title：Put the conclusion first

2. Row-based modules must use pipes

Correct:

Release post | Lead with the change | Do not hide the point below the fold | accent

Wrong:

Release post - Lead with the change - Do not hide the point below the fold

3. Required columns cannot be empty

Correct:

Tutorial | Completion rate +31% | Split steps are easier to follow | accent

Wrong:

Tutorial |  | Split steps are easier to follow

4. Module names must match the documented form

For example:

:::image-text

not:

:::image_text

Smallest working example

If this is your first advanced layout block, start here:

:::hero
title: Tell readers on the first screen why this is worth reading
subtitle: The goal is not to make the page busier. The goal is to make the point easier to catch.
tags: modules | wechat | structure
:::

:::cards[What this piece will solve]
Decision | Lead with the conclusion | Readers should not scroll for the point | accent
Reading | Make phone reading lighter | Layering beats decoration | default
Action | End more clearly | Save, follow, ask, or buy should have a place to land | default
:::

The agent rules that matter most

If an agent is generating this Markdown, the core rules are:

• judge the content task before choosing modules
• prefer 3 to 6 modules in one article
• keep one main judgment per screen
• use modules to clarify information before using them to vary visuals

Common failure checks

The whole block disappears

Check:

• whether the module name is correct
• whether a required field is missing
• whether the colon is the wrong character

The frame appears, but the content feels empty

Check:

• whether a row-based module is missing a column
• whether an image URL is empty
• whether both title and body were left blank

The page feels noisy

Check:

• whether too many modules were stacked
• whether the opening tried to carry judgment, data, cases, and action at once
• whether normal body text was forced into modules for no reason

Next step

Once the syntax is clean, the next question is selection.

Continue with:

• Advanced Layout Recipes
• Convert