How jane-does-coding/portfolio-peep works
Project type and purpose
• This is a frontend-heavy, single-page/interactive website built with Next.js (App Router) that presents “pages” as levels in a mini “game” about the author’s skills and personality. It’s a static-first site (no custom backend or database) deployed on Vercel, with interactive components (Framer Motion), styling (Tailwind + CSS), and packaged assets (fonts, images, sounds).
File structure
• Top-level directories:
• app/ → Next.js App Router directory containing layout.js, global CSS, and per-route page.jsx files (pages 1–6, intro, outro, quick-tour).
• components/ → React components for TheGame wrapper, GamePages, QuickTour, GameFooter, etc.
• data/ → Static JavaScript data (skillsAndRiddles.js).
• public/ → Static assets served from CDN: fonts, images, sounds, resume PDF.
• Config files: next.config.mjs, jsconfig.json, postcss.config.mjs, vercel.json.
• No database or external API dependencies; all content is either code or static data/assets.
README for additional insights
• Confirms Next.js, Tailwind, Framer Motion tech stack.
• Mentions inspiration from Nicky Case’s “Evolution of Trust” game and a code-size error when combining pages into one file (hence the per-page route files).
a. Main components:
• Browser (client) running the React/Next.js UI
• Next.js serverless/runtime (on Vercel) that performs routing, SSG/SSR as configured
• Static data layer (skillsAndRiddles.js)
• Public CDN for static assets (fonts, images, sounds, resume)
• Component hierarchy (Layout → TheGame/QuickTour → GamePages → PageX, Footer)
b. Relationships & interactions:
• Browser requests a route → Next.js server resolves it (SSG/static page) → serves HTML/CSS/JS
• React components fetch or import data/asset files at build/runtime
• Framer Motion adds animation in the client
• Public assets are loaded via URLs (CDN)
c. Architectural patterns/design principles:
• Next.js App Router structure (file-based routing, per-route code-splitting)
• Static-first generation (SSG) for SEO/performance
• Component decomposition: TheGame root, subdivided into page-specific components
• Separation of concerns: data folder for content; public for assets; components for UI logic
d. Key technologies: Next.js, React, Tailwind CSS, Framer Motion, Vercel deployment
Detail without overthinking
• Component nesting: Layout → TheGame & QuickTour → each PageX → GameFooter
• Configuration files as side notes (next.config.mjs, vercel.json) indicating build/deploy settings
• Static data flow: data/skillsAndRiddles.js → imported by pages → rendered in UI