How itzdineshx/pick_me_a works
Project type and purpose
• This is a single-page, front-end application (“Pick Me A”) built with React + TypeScript, bundled by Vite, styled with Tailwind CSS, and deployed as a static site (e.g., Netlify).
• Its purpose is to present an immersive “entertainment discovery hub” (anime, movies, music) featuring 3D portal effects, dynamic themes, and responsive design.
File structure
• Top level:
• package.json, bun.lockb, tsconfig*.json, vite.config.ts, tailwind.config.ts, postcss.config.js, eslint.config.js (build- & lint configs)
• public/, index.html (static assets & HTML entry point)
• src/:
• main.tsx → mounts the React tree into index.html
• App.tsx → top-level component with routers & providers
• pages/ → route views (Index.tsx, NotFound.tsx)
• components/ → reusable UI and 3D components
• components/ui/ → base UI primitives (shadcn/ui wrappers around Radix UI)
• hooks/ → custom React hooks (useToast, useMobile)
• lib/ → shared utilities
README for technical stack & architecture hints
• React 18 + TypeScript, Vite, Tailwind CSS
• Deployment: static hosting (Netlify, Vercel, S3+CloudFront)
a. External Clients & Hosting
• Users’ browsers
• CDN/Static site host (Netlify/Vercel) serving index.html + JS/CSS bundles + assets
b. Application Shell
• index.html → main.tsx
• React root (QueryClientProvider, ThemeProvider, Router)
c. UI Layer
• Routing layer (React Router)
• Pages (Index, NotFound)
• Layout & theming (Tailwind + custom design tokens)
d. Component Layer
• Base UI components (shadcn/ui + Radix primitives)
• Custom widgets (PortalCard, CinematicTitle, Portal3D, etc.)
• Hook abstractions (useToast, useMobile)
e. Data Layer
• TanStack Query client caches & manages all REST/GraphQL calls
• External content APIs:
• Anime API (AniePick)
• Movie Database API (CinePick)
• Music Service API (MeloPick)
f. 3D Engine
• React Three Fiber + Three.js under the hood for immersive portal effects
g. Build & Deployment
• Vite (dev server, HMR, build pipeline)
• Tailwind CSS / PostCSS processing
• GitHub → Netlify CI/CD pipeline
Relationships & interactions
• Browser requests index.html → loads JS/CSS bundles → React app boots
• React Router switches pages → page mounts pull data via TanStack Query → queries hit external APIs → responses populate React state & UI
• Components render UI & 3D scenes → Three.js canvas embedded in React tree
• ThemeProvider supplies HSL tokens for dynamic light/dark mode theming
• shadcn/ui primitives ensure consistent design system usage
Architectural patterns & design principles
• SPA (Single-Page Application) with component-driven architecture
• Atomic/Composable UI (base primitives → higher-order components)
• Declarative data fetching (TanStack Query)
• Separation of concerns:
• Presentation (components/ui, styling)
• Composition (components/*)
• Data (lib/utils + hooks + query client)
• Build-time optimizations via Vite, tree-shaking, CSS purging