How k4yseer/pc_playground_frontend works
Project type and purpose
• This is a SvelteKit-powered, front-end web application for PC part browsing and a 3D PC-building simulator.
• It uses:
– SvelteKit’s file-based routing and SSR/hydration
– A client-side Three.js simulation engine
– A thin “API” layer (lib/api) that fetches part data
– Svelte stores to manage app state
– Static assets (textures, videos) under “static/”
File structure
• Top-level:
– src/routes → SvelteKit pages: /, /simulator, /webpages/*
– src/lib/api → modules to load CPU, GPU, RAM, etc., from a data service
– src/lib/simulator → Three.js engine classes (SceneManager, RendererManager, ControlsManager, etc.), Svelte components for tutorial/UI, stores
– src/lib/webpages → site UI components: navbar, cards, sidebar
– static/assets, static/textures, static/videos → 3D model textures and tutorial videos
– config: svelte.config.js, vite.config.ts, tsconfig.json
• No server-side source code beyond SvelteKit – likely all logic runs in the browser (SSR only for initial HTML).
README for architecture hints
• It’s a standard SvelteKit/Vite project
• No custom backend adapter shown – probably relies on client-side fetch to some external part-data API.
Main components & their relationships
A. SvelteKit Router & SSR Server
– Serves initial HTML for each route (/, /simulator, /webpages/...)
– Hydrates to a SPA in the browser
B. UI Layer
– Route pages (src/routes/*.svelte) use lib/webpages components (navbar, cards, sidebar)
– Simulator page uses lib/simulator UI components + hooks into Simulation Engine
C. Simulation Engine (lib/simulator)
– Three.js managers: SceneManager, RendererManager, ControlsManager, etc.
– TutorialManager orchestrates on-screen guides + video playback
– ModelsManager loads 3D models & textures (static/textures)
– AnimationManager, PostProcessingManager handle visuals
D. State Management (Svelte Stores)
– recommendation.ts, selectedPart.ts, etc. feed both UI and simulator
E. API Layer (lib/api)
– Exposes functions (cpu.ts, gpu.ts, etc.) that fetch part data from an external REST service
– Called by UI components and possibly by simulation logic to fetch compatibility data
F. Static Assets
– Textures & videos served as static files by SvelteKit
G. External Services
– Third-party/data service for PC-part metadata
Architectural patterns & design principles
• Separation of concerns:
– Routing/SSR vs. client-side SPA
– UI components vs. simulation engine vs. API modules
• Modular Three.js engine:
– Each Manager class encapsulates one subsystem
• Unidirectional data flow:
– UI dispatch → API fetch → Svelte store update → UI/simulator react
– “SvelteKit Server / Router (SSR + Hydration)”
– “Browser Client”
• UI Layer (Route Pages + Webpage Components)
• Simulation Engine (Three.js Managers)
• State Store Layer (Svelte stores)
• API Client Module (lib/api)
– “Static Assets” (textures, videos)
– “External Part-Data Service”
– “Build & Deployment” (Vite bundler, adapters)
– Browser → SvelteKit Server: initial page request
– SvelteKit Server → Browser: HTML + JS bundle
– Browser UI → API Client → External Service → API Client → Store → UI/Simulator
– UI controls → Simulator Managers → WebGL Canvas
– Simulator Managers → ModelsManager → Static Assets
– Build & Deploy → produces CDN-served JS/CSS/HTML
c. Patterns:
d. Technologies:
– SvelteKit, Vite, TypeScript, Three.js, Svelte stores