How saptarshi-chakraborty/arcade-progress-tracker works
Project type and purpose
• This is a full-stack web application built with Next.js that serves both static and server-rendered React pages.
• It uses Appwrite as its backend (authentication, database, storage) and is intended to track Google Cloud Arcade participants’ progress, offering dashboards and reports for participants and facilitators.
File structure
• Top-level: package.json, next.config.mjs, public (static assets), src (React code), .env for secrets.
• src/pages: Next.js page routes (/_app, /login, /admin, /facilitator, /example, /my-account, /index).
• src/components: All UI broken down into common, page-specific, and low-level ui/ controls (ShadCN & Tailwind).
• src/contexts: React Context providers for global state and theme.
• src/lib/appwrite.js: Appwrite client configuration for API calls.
• src/data: Static routes list and mock data.
• src/styles: Tailwind global styles.
• No custom backend code beyond next.js API surface; Appwrite handles backend.
README
• Appwrite is the backend & database.
• Features for participants vs facilitators with dashboards, chart visualizations, and CRUD-style operations via Appwrite.
Main components & interactions
a. Frontend (Browser)
• Next.js rendering (SSR & CSR)
• React pages & components (pages → components → UI)
• React Context for global state & theme
b. Next.js Hosting Layer
• Vercel (or any Next.js-capable host) managing SSR, static builds, and caching
• /.app and /.document customizations
c. Appwrite Backend
• Auth endpoint (signup/login tokens)
• Database collections (participants, progress records, facilitators)
• Storage (if report uploads are stored)
d. Third-party Services & Libraries
• React Hot Toast (notifications)
• Google Cloud Arcade external links (Skill Boost profile)
• Fonts via next/font (Geist)
e. Data Flow
• User interacts via browser → Next.js pages.
• Next.js uses lib/appwrite.js to call Appwrite REST or SDK.
• Appwrite returns data → React Context or page state → UI updates.
• Optional report file uploads → Appwrite storage.
Architectural patterns & design principles
• Component-based architecture (common ← page-specific ← pages).
• Separation of concerns: UI components vs data-fetching and Appwrite client config.
• CSR + SSR hybrid (Next.js).
• Context API for global state.
• Tailwind + design system (ShadCN) for styling consistency.