How a price gets on this site

Files, not a database

A brand lives in content/brands. An item, a deal, and a news post each live in their own file. The next build turns that file into a page, adds it to the sitemap, and links it from the brand menu. There is no admin login and no database.

Example until proven

Seed prices, calories, dates, and cities are placeholders. They exist so the tables, FAQ, and structured data have a shape. The banner on those pages says so, and the price column is labeled example. Change dataStatus to verified only after you have checked the figure against the chain's app, a nutrition calculator, or a menu board.

What still varies

Even a verified national advertisement can miss your store. Delivery apps, airport counters, and the restaurant down the street often disagree. A test menu can exist in one city and never leave it. Treat every page as a briefing, then look at the menu in front of you.

What we will not pretend

Illustrations are original menu-card art, not official logos or product photos. Names of chains and items are used so people can find the briefing. That is not a sponsorship.

A new trending page is a copied file: start from content/_templates/item.json, save it under content/items/<brand>/<slug>.json, and rebuild. The README walks through that in one sitting.