Products Template

A P1 Template (Content Type) for individual product pages. See Concepts for what a Template is, and Templates for how structural changes to it get migrated across existing pages later.

Reference structure

Read directly from a live Herradura product page (herradura.com/en-us/blog/product/blanco/), genuinely more structured than what we found on Jack Daniel’s equivalent (three loose “feature pills”):

• Name: “Blanco”
• Intro copy: a short paragraph
• Product Profile: a labeled key-value block, not free text:
  • Aroma: “Agave, herbs, and citrus fruit”
  • Color: “Sparkling platinum”
  • Flavor: “Toasted agave, fresh agave, herbal tones, spices, and fresh fruit notes”
  • Finish: “Sweet, brilliant, and delightfully persistent”
  • Aged: “unaged, a true blanco”
• Featured recipes: a carousel of cocktail cards that use this product, each linking to a Cocktail page
• “Buy Now” CTA: opens the retail locator

This “Product Profile” block (Aroma/Color/Flavor/Finish/Aged) is a better reference than the JD-style three pills: it’s already a fixed, labeled schema rather than freeform marketing copy, which maps directly onto Puck fields with no interpretation needed.

Proposed field shape

interface ProductFields {
  name: string;
  introCopy: string;             // richtext
  heroImage: MediaValue;         // p1-media field
  profile: {
    aroma: string;
    color: string;
    flavor: string;
    finish: string;
    aged: string;                // e.g. "Unaged" / "45-day barrel aged" / "25 months"
  };
  category: string;              // select: Blanco / Reposado / Añejo / etc.
  buyNowEnabled: boolean;        // toggle the retail-locator CTA per product
  legalDisclaimer?: string;      // falls back to a template-level default if unset
}

The Featured Recipes relationship is real, and bidirectional

Confirmed on both a product page (Blanco → its recipes) and a cocktail page (Horseshoe Margarita → “Best With: Silver, Reposado”): products link to the cocktails that feature them, and cocktails link back to the products they recommend. This is the same cross-document relationship question flagged in Cocktails Template; see that page for the mechanism (or lack of a native one).

Pinned vs. editorial

• Pinned: hero image position, the “Buy Now” CTA block, and the legal disclaimer footer; these shouldn’t be removable by a content editor per page; the disclaimer in particular is a compliance requirement, not a style choice.
• Editorial: name, intro copy, profile fields, category; normal content editing.