pom://theme/mergetags/feed: the listing-item catalog
This JSON resource describes the widest of the three POM template merge-tag sets because a feed item may represent regular content, media-rich records, nested relationships, or WooCommerce products.
Catalog groups
The current feed context contains:
- control and shared tags:
if,else,/if,icon,translatable_string; - nested and field-driven output:
feed_from_meta,gallery,video_from_url,button_from_meta,image_from_meta,meta; - engagement:
add_to_favorite,like_button,comments; - content:
post_id,title,post_content,excerpt,permalink; - dates and author:
date,date_updated,author,author_url; - media:
featured_video,featured_image,featured_image_url,video_thumbnail; - taxonomy:
taxonomy_terms; - WooCommerce:
price,display_attribute_info,stock,e_commerce_product_time_slots,e_commerce_product_btn,e_commerce_product_img_from_gallery,sale_text,sale_amount.
This list is a runtime contract. Read each tag’s advertised attributes rather than copying an example from another context.
Practical distinctions
post_content is the feed-context content tag; the single catalog uses content. price renders product pricing, while meta reads a stored custom field and should not be used as a substitute for the WooCommerce-specific contract. feed_from_meta can render related post IDs through another feed template and therefore needs a deliberate non-recursive template choice.
Use conditionals around optional fields, keep buttons linked to real URLs, and validate nested blocks. Product-specific tags may render empty content for non-product items, so do not assign a commerce card to mixed content without checking its fallback design.
Related guides: feed template guide, WooCommerce product review, and template markup validator.