How 16sulphur/higgs works
Project type and purpose
• This is a full-stack, multi-tenant booking and event management web application built on Next.js 13 (App Router).
• It provides two role-based front-ends: a “Members” dashboard for booking meeting rooms, events, tickets, support, etc., and an “Admin” dashboard for managing organizations, users, plans, room types, rooms, events, bookings, tickets, etc.
• It also exposes internal RESTful API routes (in app/api) and uses NextAuth for authentication, plus PWA features (service worker, workbox, install prompts).
File structure
• Top-level: package.json, next.config.ts, tsconfig.json, public assets, and globals.css.
• src/app: contains the entire UI and server-side code.
• app/(members)/dashboard: “Members” area with nested pages (book, find-room, events, profile, support, etc.).
• app/admin/dashboard: “Admin” area with nested pages for organizations, users, plans, rooms, room-types, events, bookings, tickets.
• app/api: Next.js serverless API routes under /auth, /login, /logout.
• app/login & app/admin/login: authentication pages.
• app/layout.tsx & middleware.ts: global layout, routing, and session enforcement.
• app/actions: client-side modules encapsulating API calls for each domain (bookingActions.ts, eventActions.ts, orgActions.ts, etc.).
• app/lib: shared utilities for auth, API client wrapper, session handling, date formatting, time-slot generation.
• app/components: UI components organized by domain (bookings, events, orgs, rooms, tickets, common, auth, admin, etc.).
README
• Confirms this is a Next.js project created with create-next-app.
• Deploys on Vercel by default (serverless or Edge Functions).
Capturing essential details
• Domain boundary (Auth, Booking, Events, Room Management, Ticketing, Organizations).
• PWA service worker and public asset flow.
• Middleware.ts enforcing session on protected routes.
• Where app/lib utilities are used by both pages and API handlers.