How tomokino2015/area-guides works
Project type and purpose
• This is a Next.js 15.2.4 application that serves as a static/SSR “area guide” website for Tokyo’s 23 wards.
• It provides rental property info and living-environment guides via a file-based data layer and React components, styled with Tailwind CSS and using shadcn/ui + Radix for UI primitives.
File structure
• Top-level “app/” folder: Next.js App Router pages and layouts (dynamic routes under [ward]).
• “components/”: shared React components subdivided into “common,” “ward,” and “ui” libraries.
• “data/”: local data source for each ward (data/wards/*.ts) plus an index that aggregates them.
• “lib/”: utility and i18n helper functions.
• “hooks/”: custom React hooks for mobile detection and toast messaging.
• “public/”: static assets (images).
• Configuration files: next.config.mjs, tailwind.config.ts, tsconfig.json, plus build scripts in “scripts/.”
README insights
• The README explicitly calls out a “Data-Driven Architecture” where WardData objects in TypeScript drive dynamic routing and content rendering.
• Tech stack: Next.js App Router, TypeScript, Tailwind, shadcn/ui + Radix UI, React Hook Form + Zod, Vercel Analytics.
• It describes the branching strategy, deployment on Vercel, and future CMS/API integration plans.