Vegan restaurants live on seasonal turnover. The spring menu shifts to summer in three weeks, the tasting menu rotates monthly, and a new feature dish lands every Wednesday. Each of those changes is a marketing event, because regulars and food press are watching the feed and the website for the next thing. The OG card on each dish page is the single image that shows up when anyone shares the link, and a default site-header card forfeits the surface entirely.

SleekPixel reads the dish post in WordPress. Plate name, plating notes, allergen list (nuts, gluten, soy), price, course position in a tasting menu, chef quote. The template composes a 1200 by 630 card with the plate name in a strong typographic position, the allergen row in a quiet but visible band, the price in a corner, and the chef notes as a short sub-line.

For tasting menus, the same engine renders a tasting menu card that pulls the course list from related dishes. Reserve buttons, press feature links, and Instagram shares all preview as the actual menu rather than the homepage header. The conversion from share to reservation jumps the moment the share looks like the food, not the building.

Vegan restaurants over-index on share traffic because the audience is community-driven and the discovery loop runs through Instagram, food press, and recommendation threads on Reddit. A shared dish page is a marketing surface that the restaurant doesn't have to pay for, but it only converts if the preview shows the food. A default homepage banner card forfeits that surface entirely.

A rendered dish card with allergens, price, and chef context turns the share into a reservation. Templated cards remove the operational impossibility of designing per-dish cards on a small marketing team, so every dish, every season, every press feature gets the right artwork without a designer in the loop.