Does a landing page actually need to be a summary

The core concept is built around Shadrasa—sweet, sour, salty, pungent, bitter, and astringent. Instead of dumping a grid of food photos on the user immediately, I structured the flow as a narrative progression: Rasa, then taste, then the tongue, and finally the exploration. It’s a deliberate mental model that guides the user from the abstract concept to the specific story of a dish.

One of the more controversial design choices I made was using a tongue map. Now, anyone who's paid attention in biology knows that the "taste map" (where specific tastes are only felt in certain zones) is scientifically inaccurate. I knew that, but I used it as a visual metaphor rather than an anatomy chart. It serves as a zoomable, keyboard-accessible navigation hub. When you click a rasa, the camera pans to that region and opens the field notes.

To keep this from feeling like a sterile catalog, I focused on the "field journal" aesthetic. India's culinary landscape is too massive for a simple list—you've got temple food, street food, coastal specialties, and Adivasi traditions. I ended up cataloging 84 dishes across eight macro-regions. To make the data digestible, I avoided the standard card-grid layout and built a two-page notebook interface where you actually turn the pages to read about ingredients and regional history.

I also added "guides" to give the UI some personality. Each of the six tastes has a character—like a Fermentation Botanist for sour or a Coastal Navigator for salty. I used DiceBear Open Peeps SVGs for the portraits, but I intentionally limited their animations. Constant idle movement is distracting; I wanted them to feel responsive, not noisy.

From a technical perspective, this was a great exercise in prompt engineering for the content and CSS for the mandala and layout. If you're looking for a practical tutorial on how to move away from "Bootstrap-style" landing pages, the key is to stop thinking about the hero section as a billboard and start thinking of it as a prologue.

For those interested in the logic behind the interactive elements, here is a glimpse of how I structured the guide data:

[
  {
    "taste": "Madhura",
    "flavor": "sweet",
    "guide": "Guddi",
    "role": "Culinary Archivist"
  },
  {
    "taste": "Amla",
    "flavor": "sour",
    "guide": "Ami",
    "role": "Fermentation Botanist"
  }
]

The result is a site that prioritizes exploration over consumption. It's less about "here is a list of food" and more about "here is a journey through flavor."