How christiaan-fourie/ibean works
Project type and purpose
• This is a Next.js full-stack web application (React framework with built-in routing, SSR/SSG).
• From the components (ConfirmOrder, Dashboard, ManageProducts, etc.) and utils/firebase.js, it’s an e-commerce or POS admin dashboard that handles products, orders, refunds, and sales, backed by Firebase.
File structure
• Top-level files:
• next.config.mjs, tsconfig.json/jsconfig.json, postcss.config.mjs → build/config for Next.js and TypeScript/JavaScript tooling.
• package.json & lock → dependencies (Next.js, React, Firebase, etc.).
• app/ directory (Next.js 13+ App Router) contains:
• layout.js → wraps every page with common UI (header, menu).
• page.jsx → the root page entry.
• components/ → presentational and container components (Login, Dashboard, OrderCheckout, etc.).
• context/StoreContext.jsx → React Context for global state (e.g., user auth, cart).
• utils/firebase.js → abstraction over Firebase SDK (Auth, Firestore).
Key insights from the README
• Standard Create-Next-App bootstrapped project.
• Uses next/font optimization for Geist fonts.
• Intended to be deployed on Vercel (serverless hosts).
Main components & interactions
a. Frontend (Client Browser)
• React components within Next.js App Router.
• Global CSS (globals.css) and next/font for styling & performance.
b. Next.js Framework Layer
• App Router handles routing and SSR/SSG.
• layout.js injects shared UI.
c. State Management
• StoreContext provides auth state, cart data, product listings across components.
d. Data Service Layer
• utils/firebase.js manages connections to Firebase Auth and Firestore.
e. External Services
• Firebase Auth (user login, session).
• Firestore Database (products, orders, refunds, sales).
• Vercel CDN & serverless runtime for hosting.
Architectural patterns & design principles
• React + Next.js App Router (component-based, SSR/SSG, file-based routing).
• Provider-Consumer pattern via React Context for global state.
• Service abstraction over Firebase SDK for decoupling.
• Separation of concerns: UI components vs. data fetching logic.