Community MeetupsUX direction
CTFtime-inspired, India-first

Simple public boards first. Deep workflows only after intent.

The platform can handle registrations, CFPs, venues, check-in, badges, email, sponsors, and trust. The public experience should still start like a calm calendar: upcoming, city, topic, date, seats, and one action.

Primary navigation
Keep the header small. These six doors cover normal public discovery before exposing the larger product surface.
Top level
What to borrow from CTFtime
Use the information architecture discipline, then apply a more modern, responsive, multi-color visual system for Indian tech communities.
UX source
Stable small nav

Keep public doors predictable: upcoming, calendar, cities, CFPs, communities, and archive/product map.

Timely lists first

A visitor should see what is running, upcoming, open, or closing before operational tools.

Archive creates trust

Past events, talks, materials, reviews, and community history should remain searchable.

Signals stay separate

Registration status, capacity, ratings, reliability, and community trust need clear labels.

Normal attendee flow
This is the path that should stay obvious even as the product grows.
1LandSee what is next, which cities are active, and where to browse.
2ScanRead compact rows before opening details: date, city, topic, seats, status.
3DecideOpen details for agenda, speaker, venue, trust signals, and materials.
4RegisterUse one profile, add to calendar, check route, and keep the ticket ready.
5ReturnAccess slides, rate verified sessions, and follow the community history.
Color roles
Multi-color themes should guide meaning, not become noise.
GreenOpen, ready, primary action
BlueCities, logistics, navigation
SaffronDeadlines, capacity, payments
CoralChanges, risk, human follow-up
VioletCFP, archive, reputation
Build rules for the next slices
These rules keep PRD features usable across mobile, iPad, desktop, light mode, and dark mode.
Calendar first

The first question is always what, where, when, and whether registration is open.

Progressive depth

Public discovery stays simple; account, speaker, organizer, and ecosystem tools open after intent is clear.

Rows before cards

Events, CFPs, schedules, and queues should scan like boards. Cards are reserved for decisions and summaries.

Permanent history

Past events, talks, slides, recordings, feedback, and community history remain findable.

One obvious action

Every row should make the next action clear: register, save an alert, apply, review, check in, or export.

Responsive by default

Phone, tablet, and desktop use the same information model, with controls collapsing instead of disappearing.

Reference memo: docs/design-language.mdApply it to discovery
Community MeetupsIndia tech calendar