pom://theme/mergetags/single: fields for one content item

Read this JSON catalog before generating a POM single template. It advertises only the merge tags accepted in the single context.

Single-context catalog

The current resource includes:

• flow control: if, else, /if;
• shared rendering: icon, translatable_string;
• navigation and media: posts_nav, gallery, image_from_meta, featured_image, featured_image_url;
• custom data: meta;
• content identity: post_id, title, content, excerpt, permalink.

Every tag definition can include supported attributes and usage guidance. Use that live definition instead of inventing attributes from a similarly named shortcode.

Conditional structure

Single templates can test a meta field:

{{if meta="event_date" value="not_empty"}}
    <p>{{meta name="event_date" type="date" only_content="true"}}</p>
{{else}}
    <p>{{translatable_string text=%%Date to be confirmed%%}}</p>
{{/if}}

The value comparison supports an exact value plus the documented empty and not_empty modes. Always close the block and keep else between its matching opening and closing tags.

meta reads a value; image_from_meta and gallery interpret media-oriented field content. Choose the semantic tag that matches the stored field rather than formatting an attachment ID as visible text.

The resource cannot prove that a meta key exists on every item. Verify the content model, validate the template, and preview different records before assignment.

Related guides: single template guide, content-model guide, and available merge tags tool.