How st1llwater/otakunote-revamp works
Project type and purpose
• OtakuNote is a full-stack, server-rendered & client-hydrated web application built on Next.js (v14).
• Its purpose is to let users browse, search, and manage an anime watchlist via a rich, interactive UI. It fetches data from an external GraphQL anime API, persists user session/status client-side, and is deployed as a serverless app (e.g. Vercel).
File structure
• Top-level files: next.config.mjs, tailwind.config.ts, codegen.yml, package.json – define build, styling, GraphQL codegen.
• src/app/ → Next.js App Router pages (home/trending, search, watchlist, calendar).
• src/app/components/ → React UI components (cards, carousels, modals, reusable UI primitives under ui/).
• src/app/lib/graphql/ → GraphQL client setup + generated queries/types, plus REST API wrapper (animeApi.ts).
• src/app/providers/ → Context providers: React Query, Session (next-auth?), Theme.
• src/app/store/ → Jotai atoms for managing local UI & user data.
• public/ → static assets (fonts).
README for technical stack & patterns
• Next.js + React 18 with SSR/SSG + client hydration
• Tailwind CSS for styling, Framer Motion for animations
• Jotai for client state
• GraphQL (code-generated) as primary data layer
• Radix UI & Sonner for UI primitives
Elements
• Blue rectangles for compute nodes (Browser, Next.js Server)
• Yellow circles or rectangles for state layers (Jotai, React Query)