DEV Community

Cover image for I designed a comfort-food landing page for the person who feeds everyone else first
ANIRUDDHA ADAK
ANIRUDDHA ADAK

Posted on

I designed a comfort-food landing page for the person who feeds everyone else first

Frontend Challenge Perfect Landing Submission 🍲🥧

Sometimes the most humane thing a food site can say is, you have already done enough today.

For the Comfort Food Perfect Landing prompt, I built Noodle Note, a polished landing page for a comforting bowl of sesame ramen. It is aimed at the person who remembers to feed the dog before themselves, the person who wants something warm but does not need a brand to make a spectacle out of being tired.

The page is part of Comfort Paws Lab, but it works as its own focused experience. It has a clear route back to the broader field guide, a singular recipe story, a useful save interaction, and a visual system built from paper slips, kitchen labels, warm table tones, and one ink-blue bowl.

A landing page that starts with a feeling, then earns the function

The first screen has one job: make the visitor feel expected. The headline is specific, the CTA is clear, and the illustrated bowl provides a visual answer before the page asks for attention. The next section gives the central idea room to breathe before the recipe card introduces time, location, ingredients, and a practical action.

I avoided a centered stack of generic feature cards because comfort is not generic. The layout uses an editorial reading path instead. A slim field-kitchen rail grounds the opening, a side note overlaps the bowl, and the recipe becomes a large paper card on a kitchen-table background. Each shift in composition gives the visitor a different kind of information without making them hunt for it.

The useful interaction

The “Keep this bowl close” button changes to a saved confirmation. It is small, but it respects the promise of the page. A visitor can acknowledge that this is a recipe they want to return to without being pushed into an account flow or a fake confirmation toast.

const [saved, setSaved] = useState(false)

<button onClick={() => setSaved((current) => current ? false : true)} aria-pressed={saved}>
  {saved ? <Check size={17} /> : <Bookmark size={17} />}
  {saved ? "Saved for another night" : "Keep this bowl close"}
</button>
Enter fullscreen mode Exit fullscreen mode

The copy changes, the icon changes, and the button keeps its place in the reading flow. Nothing jumps, disappears, or asks the visitor to learn a new control.

Accessibility and code quality

I treated accessibility as part of the aesthetic rather than a final checklist. Keyboard focus is visible, navigation uses real links, buttons expose their pressed state, the layout stays readable at smaller widths, and motion is limited to details that can safely stop. The content hierarchy is semantic and the route has a clear escape back to Comfort Paws Lab.

The illustration is composed from CSS shapes, which keeps the page lightweight and gives the food visual a direct relationship with the CSS Art submission. That relationship is deliberate, but the two entries are separate. The art study asks how a bowl can be made from CSS. Noodle Note asks how a food page can make someone feel less hurried.

Demo

The dedicated landing page is here: Noodle Note. The source-and-asset archive includes the route, all original cover art, and the shared design system.

If you have ever opened a recipe site and felt like it was yelling at you, I would love to know what made it feel that way. I am interested in the opposite: the smallest detail that makes a page feel like it saved you a seat.

Top comments (0)