Dynamic Content

Dynamic Content

Use GenerateBlocks V2 query blocks when content should come from WordPress records instead of being copied into a static layout.

Query hierarchy

generateblocks/query
├── generateblocks/looper
│   └── generateblocks/loop-item
│       └── Text, Media, Element and other content blocks
├── generateblocks/query-no-results
└── generateblocks/query-page-numbers

The Looper owns the grid or flex layout. The Loop Item is the repeated template. Empty-state and pagination blocks are siblings of the Looper, not children of the repeated item. Avoid the legacy generateblocks/query-loop name for new V2 output.

The Query block uses WordPress query arguments. For example, this is the query input, not a complete serialized block:

{
  "post_type": "post",
  "post_status": "publish",
  "posts_per_page": 6,
  "orderby": "date",
  "order": "DESC",
  "ignore_sticky_posts": true
}

For an archive template, inherited query behavior should follow the actual archive context instead of replacing it with a fixed list of posts. See Building a Website.

Exact dynamic-tag syntax

{{tag_name option:value|option2:value}}

There is a space after the tag name, pipes separate options and values are not quoted.

Need	Example
Title	{{post_title}}
Destination	{{post_permalink}}
Excerpt	{{post_excerpt length:20}}
Featured image	{{featured_image size:large}}
Custom field	{{post_meta key:field_name}}
Categories	{{term_list tax:category}}
Formatted date	{{post_date dateFormat:M j, Y}}

Do not invent aliases such as post_url, featured_image_url or acf, and do not use key="field" syntax. Use the tag catalog for supported options.

Custom fields and repeaters

Ordinary custom-field values use post_meta. ACF field return formats still matter: a URL, attachment ID and array require different handling. Pro adds array-oriented query sources such as post meta and options; these are not identical to a normal post query.

Resolve the actual field key and data shape before building a repeater template. A four-digit layout scope never substitutes for the real record or form referenced by dynamic content.

Verify with actual records

Check at least a populated result, a long title, a missing image/field where relevant, and the no-results state. Verify destinations, ordering and pagination. Placeholder text in the editor is not proof that a tag resolves on the frontend.

Continue with the query guide and custom-field guide.

---

Back to wiki home · Reference library