pom://theme/mergetags/archive: structured archive values

This JSON resource is the machine-readable source of truth for archive merge tags. Its payload contains the archive context, a mergetags map, and syntax rules.

Available archive concepts

The catalog exposes:

• common output: icon, translatable_string;
• archive identity: archive_title, blogname;
• term data: term_id, parent_term_id, term_description, term_thumbnail, term_bg_image, term_color;
• result insertion: archive_results.

Archive templates do not advertise the if, else, and /if control tags available in single and feed contexts. Do not copy those controls into an archive template unless a later live catalog explicitly adds them.

Choosing tags

Use archive_title for the current archive heading. Term-specific tags may return no content when the current archive is not backed by a queried term. parent_term_id supports its documented fallback behavior; inspect the live tag definition before relying on it. Use archive_results for the loop rather than attempting to query or render posts inside the template.

Merge tags use double braces:

{{term_thumbnail}}
{{icon family="feather" name="grid"}}
{{translatable_string text=%%Browse this category%%}}

Use the returned attribute definitions exactly. When an attribute contains long copy, quotes, HTML, or another merge tag, wrap its literal value in %%...%%.

The catalog tells the client what can be rendered, not whether a particular archive has populated term metadata. Validate the markup, then preview both a term archive and any non-term archive to which the template will be assigned.

Related guides: archive template resource, merge-tag authoring tool, and template validation.