← Back to Built Systems
Cities / Transit / SystemsLive2026

IndianTransit

A public transit reference platform for Indian cities, systems, lines, stations, maps, construction updates, and service changes.

Next.js 14TypeScriptTailwind CSSLeafletSanity CMSVercel

What it is

IndianTransit is a public reference platform for India’s transit networks. In its current model it covers 20+ Indian cities, 150+ transit lines, 900+ stations, and more than 3,000 generated pages. The point is simple: transit information should be browsable as a system, not hunted for as a one-off.

Why I built it

Indian transit information exists, but it rarely feels like a navigable reference system. I built IndianTransit so city pages, lines, stations, maps, service changes, and construction updates could live in one calm, structured place.

What problem it solves

Transit information in India is fragmented across operator sites, PDF timetables, and news posts. IndianTransit treats transit as a dataset you can browse, compare, and watch over time, rather than something you hunt for only when you need a ticket.

Stack

  • Next.js 14 for the app shell, with ISR and webhook-triggered revalidation so fresh service changes appear without a full rebuild.
  • TypeScript in strict mode end to end.
  • Tailwind CSS for the design system.
  • Leaflet + OpenStreetMap for the maps and station visualisations.
  • Sanity CMS as the structured content backbone for cities, lines, and stations.
  • Vercel for hosting and edge delivery.
  • A construction dashboard layer for ongoing transit construction and tender updates.

Current status

Live. Actively maintained; the live site is the primary surface.

What I learned

  • Treating transit as a dataset changes what you can show people. Once the model is clean, the pages almost write themselves.
  • The hardest part is not rendering. It is normalising station names, line aliases, and service states across operators that disagree with themselves.
  • A calm, systems-first reading of transit is more interesting than another news ticker.

What I would improve next

  • More automated ingestion so the reference stays fresh without manual passes.
  • Better cross-city comparison views (lines, stations, service states).
  • A clearer editorial layer for construction and tender updates.