Designing a More Complete Recipe Website

Simeon Griggs has published a set of UX ideas for recipe websites. Common to all of them is doing a number of things the user would otherwise do by hand.

  • No math. Unit swapping and serving adjustments should happen on the fly.
  • Alternative ingredients should be offered as a matter of course.
  • Ingredient amounts should be re-listed wherever the instructions reference them.

That last suggestion draws particular agreement, and Griggs calls it his favorite of the improvements. His argument: a standard recipe opens with a list of ingredients and their amounts, followed by a bulleted sequence of method steps, but those steps usually never mention the quantities again. Anyone who hasn't weighed out everything up front — which, as Griggs puts it, is what you're supposed to do but not something people actually do — is left scanning back and forth through the page.

Whether these features are feasible depends in part on the underlying data model. If an ingredient is stored as an Array rather than a String, for instance, the site is positioned to offer alternatives from the start.

CSS-Tricks star logo