How danny-ssong/book-journey works
Project type and purpose
• This is a full-stack web application built on Next.js 14, using the App Router (src/app).
• It’s a “Book Journey” social/review platform where users can search book metadata (via Kakao Open API), create posts/reviews, view feed/statistics, and manage profiles.
• Supabase provides authentication, database, and edge functions; Tailwind CSS handles styling.
File structure
• Top-level config: next.config.js/mjs, tsconfig.json, tailwind.config.ts, supabase/config.toml.
• “src/app”: the Next.js App Router with nested folders for each route (/, /books, /posts, /users, /search, /manage, etc.).
• Each route contains page.tsx entrypoints, server-actions (src/app/actions), dynamic segments ([isbn], [postId], [userId]).
• Shared UI components under src/app/_components and route-scoped components under route/_components.
• Hooks (src/app/_hooks) for infinite scrolling, data fetching, theming, user state.
• Library functions (src/app/_lib) for server-side data access (getPostsGroupBy, getMe, revalidatePath).
• API routes under src/app/api (revalidate).
• “src/components/ui”: a design-system layer of generic UI primitives (buttons, cards, popovers).
• “src/lib” and “src/utils”: generic utilities (auth, caching, middleware).
• “supabase” folder: database schema (seed.sql), Supabase CLI config (config.toml).
• Types in “src/types” for domain objects (book, post, user, profile).
README for additional insights
• Confirms tech stack: Next.js, Tailwind CSS, Supabase, Kakao Open API.
• Indicates environment setup necessary for Supabase and Kakao credentials.
Detail without over-splitting
• Logical groupings (e.g., “src/app/_components” as UI layer vs “src/app/actions” as Mutation layer).
• Dynamic routes and server-side data fetching.
• Convey how the design system (ui primitives) underpins all client UIs.