How mhussnainn/event works
This is a small Events App: visitors browse a hard-coded upcoming-events list, open an event detail page, or submit an event form. Submission currently shows a toast and returns home; it does not persist or add the event to the listing. The detail view independently contains the same sample data. The graph focuses on these routes and the shared notification runtime; source sampling does not establish a backend, store, registration flow, or broader UI-kit use.
Main entry points: add/page.tsx Create event form · toaster.tsx Toast host · app/page.tsx Browse events · use-toast.ts Toast state hook
Components 8
Event experience
- Browse events
app/page.tsx - Create event form
app/add/page.tsx - Event details
app/event/[id]/page.tsx
Notification runtime
- Toast state hook
hooks/use-toast.ts - Toast host
components/ui/toaster.tsx - Toast presentation
components/ui/toast.tsx - Root layout
app/layout.tsx
Other components
- Visitor
Connections 9
- Visitor → Browse events: browses
app/page.tsx - Browse events → Event details: links to
app/page.tsx - Visitor → Create event form: submits
app/add/page.tsx - Create event form → Toast state hook: shows toast
app/add/page.tsx - Create event form → Browse events: redirects to
app/add/page.tsx - Root layout → Toast host: renders
app/layout.tsx - Toast host → Toast state hook: reads state
components/ui/toaster.tsx - Toast host → Toast presentation: renders
components/ui/toaster.tsx - Toast state hook → Toast presentation: uses types
hooks/use-toast.ts