md2wechat Agent API markAgent API Docs
md2wechat Agent API markAgent API Docs
Homepage

Start

Markdown to WeChat API DocsQuickstartAuth

APIs

Integrations

Operations

ErrorsPricingContact
X (Twitter)

Advanced Layout Recipes

Scenario-based recipes for choosing advanced layout modules with restraint, especially for agents and API workflows.

Advanced Layout Recipes

This page is not about "what modules exist." It is about "which few modules this piece actually needs."

The rule is simple:

judge the content task first, then choose the smallest accurate module set.

Four questions before you choose anything

Ask:

  1. do readers need help deciding whether this is worth reading
  2. will this feel tiring on a phone
  3. what judgment, person, or brand should remain after reading
  4. what action should happen next

Those four questions are enough to make the module choice much cleaner.

Scenario 1: release post

Goal:

  • explain quickly why the update matters
  • make the change easy to understand
  • land the next action clearly

Recommended set:

  • hero
  • cards
  • compare or steps
  • summary
  • cta

Avoid:

  • opening with metrics, pricing, and faq all at once

Scenario 2: long-form method piece

Goal:

  • establish the judgment early
  • keep phone reading light
  • leave the reader with a distinct position

Recommended set:

  • verdict
  • toc
  • part
  • bridge
  • quote or summary
  • author-card

Avoid:

  • using a heavy module for every small section

Scenario 3: tutorial

Goal:

  • make the process followable
  • reduce navigation fatigue on mobile
  • avoid crushing the page with long instructions

Recommended set:

  • hero
  • steps
  • image-text or image-steps
  • notice
  • checklist

Avoid:

  • interrupting the workflow with too many opinion modules

Scenario 4: service or conversion page

Goal:

  • qualify the reader
  • explain the difference clearly
  • land trust and action together

Recommended set:

  • audience-fit
  • verdict
  • cases
  • pricing
  • faq
  • subscribe or cta

Avoid:

  • talking about yourself before telling the reader whether the offer fits

Scenario 5: brand or series article

Goal:

  • make the judgment memorable
  • make the author memorable
  • create a reason to stay with the series

Recommended set:

  • hero
  • manifesto
  • quote
  • series
  • author-card
  • subscribe

Avoid:

  • turning the article into a company bio

The most reliable agent selection order

If you are writing agent instructions, the safest order is:

  1. classify the piece as release, tutorial, method, service, or brand content
  2. pick one opening module
  3. pick one or two modules for the body
  4. pick one closing module

That is enough for most articles.

A very practical upper bound

Unless this is a white paper or a long guide, most pieces should stay around:

  • 3 to 6 advanced modules

Less than that and the structure may not register.

More than that and the phone reading experience often becomes fragmented.

Final judgment

Advanced layout is not about making the article more complicated.

It is about helping both humans and agents land emphasis, rhythm, brand, and action in the same WeChat piece.

Continue with:

  • Advanced Layout
  • Advanced Layout Syntax
  • Convert

Table of Contents

Advanced Layout Recipes
Four questions before you choose anything
Scenario 1: release post
Scenario 2: long-form method piece
Scenario 3: tutorial
Scenario 4: service or conversion page
Scenario 5: brand or series article
The most reliable agent selection order
A very practical upper bound
Final judgment