Appearance
Source:
docs/adr/0003-product-brand-catalog.md. Edit it there; this page is generated at build time.
First-class Product/Brand catalog, not embedded per-content fields
We considered embedding product details (name, image, affiliate link, price) directly as fields on each Review/Listicle/Comparison versus a shared Product/Brand catalog referenced by content. We chose the shared catalog: it's what makes first-party Click logging, consistent Affiliate Links, and Product/Offer schema.org markup work without duplicating data across every piece of content that mentions the same product, and it lets a price or affiliate link be updated once and reflected everywhere that product is referenced. The trade-off is a small amount of extra indirection (content references a Product rather than owning its fields directly), which we accept for that reuse.