A full-stack food ordering demo — customer-facing storefront, kitchen dispatch view, and driver delivery view — built to prototype how a township takeaway could run end-to-end on a single Next.js app.
This is a demo project. Default credentials (
staff123,drive123) are for local evaluation only. Replace viaNEXT_PUBLIC_KITCHEN_PW/NEXT_PUBLIC_DRIVER_PWenv vars if you deploy. Real production auth would move this server-side.
- Customer browses a menu, builds a cart, places an order
- Kitchen sees new orders live, flips tickets through prep → ready
- Driver picks up ready tickets, marks delivered
- Catalogue admin (separate
FoodCatalogueapp) manages menu items and pricing
| Layer | Tech |
|---|---|
| Framework | Next.js + TypeScript |
| UI | Tailwind · Radix primitives · shadcn/ui |
| State | React Context (per-role auth) |
| Structure | Two-app monorepo (foodiezone + FoodCatalogue) |
git clone https://github.com/ChumaMike/Foodiezone.git
cd Foodiezone/foodiezone
npm install
npm run devThe catalogue admin app lives at ../FoodCatalogue/ — same flow.
- Move role auth server-side (current client-side gating is demo-only)
- Real payments (Yoco / Peach integration)
- Driver location tracking
- WhatsApp receipt delivery via Twilio
MIT · Demo by Chuma Meyiswa