Brunch covers the weekend menu spread: eggs benedict, frittata, avocado toast, cinnamon rolls, smoked salmon bagels, French toast, breakfast tacos, mimosas. The dishes range from sweet to savory and from quick to leisurely, but each recipe carries the same fields: name, type, time, ingredients, steps, photo, nutrition. The serving occasion is what unifies them.

SleekRank reads a brunch sheet and ships one URL per row at /recipes/brunch/{slug}/. Tag mappings carry the title, list mappings render ingredients and steps, selector mappings drop the photo and the sweet-or-savory badge, meta mappings handle Recipe JSON-LD.

Sweet and savory clusters stay separated automatically. Pairing suggestions, like which mimosa goes with which savory dish, surface as a per-row pairing field that links across the corpus.

Brunch is a serving occasion that crosses every cuisine and every prep style. The shared format is the menu spread, not the cook time or ingredient list. Hand-built brunch sections struggle to surface that shared structure because each post is written independently, with pairings buried in body copy and serving sizes hidden in prose.

Programmatic generation forces the structural fields into named columns, which means filtering, pairings, and scaling become real features instead of editor-dependent prose. The Recipe schema stays valid, the sweet and savory clusters stay distinct, and the menu navigation reads from the same row set that powers the page content. The site grows in step with the source sheet rather than in step with editor availability, and pairings turn a flat archive into a connected menu.