How limjiajun990701/cheerful-webspace-68 works
Project Type and Purpose
• This is a full-stack, single-page portfolio application with an integrated admin dashboard.
• Purpose: Showcase professional content (projects, blog, resume, certifications) and provide an authenticated admin panel to manage that content.
Main Components
a. Frontend (Client Application)
• Built with React 18 + TypeScript
• UI layer: Tailwind CSS + shadcn/ui
• Routing: React Router
• Data fetching: Tanstack React Query
• Core code lives under src/ (pages, components, hooks, utils).
b. Backend as a Service (BaaS)
• Supabase provides:
• Authentication (supabase.auth)
• Postgres database for content tables (blogs, projects, certifications, resume metadata, cheat sheets, etc.)
• Storage buckets for file uploads (resume PDF, images)
• Row-level security policies protect admin data
c. Build & Hosting
• Development: Vite dev server (hot reload)
• Production: Vite build → static assets (dist/) → deploy to any static host (Netlify, Vercel, S3)
d. Developer Tools & Config
• package.json, bun.lockb, vite.config.ts, tailwind.config.ts, ESLint, TypeScript configs
e. External Dependencies
• NPM packages: React, React Router, React Query, Supabase JS client, shadcn/ui, Tailwind, etc.
Relationships & Data Flows
• User (Browser) ↔ React App: UI interactions, page navigations
• React App ↔ Supabase API:
• Authentication requests (login, session)
• CRUD calls for content (via supabase.from(…) queries wrapped in src/utils & React Query hooks)
• File uploads/downloads to Supabase Storage
• Deployment pipeline: local machine → Vite build → static host
Architectural Patterns & Principles
• SPA with clear separation: Presentation (components/UI) vs. Data Layer (hooks, utils)
• “Feature folder” structure (components grouped by domain: admin, ui, cheatsheets, etc.)
• BaaS microservices model—delegates auth, DB, storage to Supabase
• Secure client-side routing with protected admin routes