How w3di/n-kolmykov-frontend works
Project Type & Purpose
• This is a frontend‐only, Next.js 15 application (App Router) written in React & TypeScript.
• It serves as an open-source “quiz” site: static/dynamic pages (Home, About Me, Quiz) with client-side state and SSG/SSR.
File-Structure Analysis
• app/ – Next.js App Router pages & layouts (page.tsx, layout.tsx, subroutes like /about-me, /quiz).
• src/features/quiz/ – domain feature module: API stubs, React context & hooks for quiz state, UI components & styles.
• src/shared/ui/ – shared design system: kit components (Accordion, Button, Toast, etc.), layout (Header, Footer), page sections (Hero, Stats, AboutMe, etc.).
• config & tooling – ESLint, Stylelint, Prettier, Husky hooks, Dockerfile, GitHub Actions workflow.
README Insights
• No backend yet—quiz data is mocked and consumed client-side.
a. Main Components
• User Agent (Browser)
• Next.js Server (Node/Vercel)
• Page Router & Layout (app/layout.tsx, page.tsx)
• Feature Module: Quiz (src/features/quiz)
• Shared UI Library (src/shared/ui)
• Static Assets Store (public/) – fonts, images, SVGs, animations
• Build & Deploy Pipeline (Dockerfile, GitHub Actions)
b. Relationships & Data Flows
• Browser <–> Next.js Server: initial SSR/SSG + hydration
• Browser pulls static assets from CDN/public folder
• Client-side React (Quiz Context & Hooks) manages quiz state, navigation, stats
• Build pipeline compiles TS/SCSS, runs lint & tests, outputs production bundle
• CI/CD pipeline triggers on git push → deploy to hosting
c. Architectural Patterns
• Component-based (atomic UI kit → sections → pages)
• Feature-based modules (quiz logic isolated under src/features)
• App Router (Next.js v15 folder-based routing + layouts)
• CSS Modules & SCSS (scoped styling by component/section)
d. Key Technologies
• Next.js, React, TypeScript, SCSS Modules
• React-Toastify (notifications)
• Lottie for animated assets
• GitHub Actions (CI/CD), Husky (pre-commit), Docker (containerization)
Detail & Clarity
• Data flows (e.g., “fetch mock questions” → “Quiz Context”).
• Related components with container boundaries (e.g., Next.js App Router).
• Notes for future backend integration and AI-powered extensions.