Product note: clearer recipe pages for faster cooking

First, it helps someone decide whether the recipe fits. Second, it helps them cook without hunting for information. Those jobs are connected, but they happen at different speeds.

The recent recipe page work focused on putting decision details near the top: image, title, time, servings, difficulty, and planning actions. Once someone commits, the ingredients and steps should be easy to follow.

A finished-dish image should answer a basic question: what am I making? If the image is too small, too cropped, or visually unrelated, the page loses trust. Better image treatment gives users a faster read on the recipe before they open the details.

This is especially important for browsing and planning. A clear image can help someone choose between two similar titles without reading both recipes line by line.

When someone decides a recipe fits, the next actions are predictable: save it, plan it, or adapt it privately. Keeping those actions near the top reduces the gap between discovery and use.

That is the larger product direction: recipes are not static pages. They are inputs into planning, shopping, and cooking.