How hanneswidrig/tech-screener works
Project type and purpose
• This is a SvelteKit–powered single-page quiz application that runs entirely in the browser (no dedicated backend).
• The user takes a quiz using questions from a local question bank; the app manages state in client-side stores and displays scores and summaries.
File structure
• Top level:
• src/
– app.html, app.css: the HTML shell and global styles.
– lib/: reusable UI components (Button, Sidebar, ScoreSummary, etc.), data (question-bank.ts, topic-group.ts), state stores (quiz, questions, topic) and utility functions (calculate_score).
– routes/: file-based routing:
• +layout.svelte, +page.svelte for the main layout and home page
• /quiz/+page.svelte for the quiz UI page
• +error.svelte for error handling.
• static/: robots.txt and any other static assets.
• Config files for TypeScript, Vite, ESLint, Prettier, Playwright (e2e tests).
• e2e/: end-to-end tests written in Playwright.
• There is no separate “backend” directory; the entire logic lives client-side. The build system uses Vite and the SvelteKit adapter (presumably adapter-auto or static) to produce a static bundle.
README for additional insights
• The README is the default “create-svelte” template. It confirms that SvelteKit and Vite are the development frameworks, and that the project is intended to be deployed as a static or server-generated site.
→ from “Browser” to “Static Host” for initial GET
→ from “Bundle” to “Router” for runtime navigation
→ between components and stores to show reads/writes
• Blue rectangles for UI components
• Yellow rectangles for utility modules
• Gray clouds for external systems (e.g., static host, Playwright test runner)
Detailed capturing of essential elements
• Don’t overcomplicate: break the app into these main tiers—Hosting/Build, Client Runtime, Routing, UI Components, State, Data, Utilities, Testing.