How azula9713/teyvat-archive-client-next works
Project Type & Purpose
• Teyvat Archive is a full-stack (front-end–focused) web application built on Next.js.
• Purpose: Provide an interactive UI for Genshin Impact fans to browse events, characters, weapons, artifacts, and Spiral Abyss stats.
File Structure & Architectural Patterns
• src/app/
• Next.js App Router: dynamic routes for /characters/[slug], /weapons/[slug], /artifacts/[slug], /spiral-abyss, etc.
• Layout, loading, and error components handle SSR/SSG page structure, data loading states, and error boundaries.
• src/components/
• Organised by feature: characters, weapons, artifacts, events, spiralAbyss, plus common UI elements (common, layout, modals).
• Each feature subfolder splits mobile vs. desktop views, filter sections, client fetchers, etc.
• src/atoms/
• Global state containers (using Jotai or Recoil patterns) for feature data: characters, artifacts, weapons.
• src/hooks/
• Custom React hooks encapsulate data fetching, filtering, infinite scrolling, etc.
• src/services/
• HTTP layer (axios.service.ts) → system utilities → Teyvat server API client (teyvatArchive.service.ts).
• src/utils/ & src/types/
• Pure utilities, formatters, parsers, and TypeScript type definitions for API payloads.
• public/ & src/assets/
• Configuration
• next.config.ts, ESLint, Prettier, Husky for code quality; GitHub Actions workflows for CI/version bump.
Key Elements to Capture
• Next.js SSR/SSG cycle
• App Router’s nested layout structure
• Data flow: Browser ↔ Next.js ↔ External API
• State-management central store
• Static asset delivery path
• CI/CD integration point (version bump, deploy)