Four sections. Everything an airport has to say.
An airport website. One designer. Who also learned the CMS.
- Role
- Sole UX/UI designer
- Year
- 2025 — 2026
- Domain
- Public airport website
- Status
- Live at niairport.in
Context
The problem
The screens weren’t the hard part. The information architecture was.
What I noticed
The temptation with an airport is to structure the site the way the airport is structured. Departments make tidy navigation and terrible websites. Nobody arrives at an airport website looking for "Commercial Operations" — they want to know where to park and whether their flight is late.
Decisions
- 01
Four top-level sections, named the way a passenger thinks: Fly · At NIA · Transport · Shop & Dine.!
- 02
Learn Sitecore and publish the pages myself. Not for the CV — the pages weren’t going to upload themselves.!
What I changed
Underneath the four sections: departures and arrivals, destinations, flight search · lost and found, security and packing rules, special assistance for reduced mobility, lounges · parking, taxis, public transport · shops, food, FAQs.
Two constraints shaped it. Everything had to sit inside the Zurich design guidelines — someone else’s system, no licence to redesign it. Working inside a system you didn’t write teaches you which of your habits were only preferences.
And it had to work in English and Hindi, and as a PWA with its own bottom navigation — back, home, flights, shops. Because a passenger checking a gate number is standing up, one-handed, in a hurry.
What happened after
Live at niairport.in — which is more than most portfolio work can say.
Departments make tidy navigation and terrible websites.