
Every test kitchen needs a tomato soup, and this is ours: completely fictional, aggressively seasoned, and engineered to touch as many pieces of the page as possible. Grouped ingredients, a callout, two story photos, a heading in the middle — if a piece of the layout can break, this post is here to break it before a real recipe does.
Why this soup exists
The honest answer is wiring. A recipe page is not one thing, it is a dozen small systems agreeing with each other: the card, the story stack, the pin, the catalogue, the exports. A soup with nothing to say can still say all of that. But since we are here, the soup itself is a good one — the kind built on a slow onion base and finished with cream, the kind that makes grilled cheese feel like a supporting act it was always meant to be.
The second photo is a plate of spaghetti, which is not soup. It is standing in for a process shot, the way half the photos in a test corpus have to. What matters is not the subject, it is the placement: a photo landing mid-story, after two paragraphs, with a caption, exactly where a real process shot will land someday.

Serve it in warm bowls if you are being nice to people. Add the basil at the very end, never during the simmer, unless grey-green basil is the look you were going for. It was not.