How munishmummadi/portfolio works
Project type and purpose
• This is a monolithic, full-stack “personal portfolio” website built with Next.js (React framework) and styled via Tailwind CSS.
• Purpose: display a developer’s projects, timeline, status, and personal information in a modern, responsive, SEO-friendly site, hosted (e.g., on Vercel).
File structure
• Top-level folders:
• public/ – static assets (images, favicons, sounds, shaders)
• src/pages/ – Next.js file-based routes (404, index, projects, status, timeline, error)
• src/components/ – reusable UI components (Button, Navbar, List, Status widgets, Background)
• src/layouts/ – page wrappers (Default and Error layouts)
• src/lib/ – utility modules (SEO, navigation, sounds, API calls such as lanyard.ts for Discord status)
• src/data/ – local JSON data (projects.json, timeline.json)
• src/types/ – TypeScript type definitions
• Configuration: next.config.js, tailwind.config.js, tsconfig.json, vercel.json
README for additional insights
• Architecture: Next.js 14, SSR by default, static generation for data-driven pages.
• Tech stack: React + TypeScript on the front end; Tailwind CSS for styling; no external database—data is read from JSON or fetched at runtime via lanyard API.
Main components
a. Client Browser
b. CDN (e.g., Vercel Edge Network)
c. Next.js Server (Node.js runtime)
d. React Components & Layouts (UI layer)
e. Data Sources
• Local JSON files (projects.json, timeline.json)
• External API (Discord status via Lanyard)
f. Static Assets (public/)
g. Build & Deployment Pipeline (Vercel, pnpm/npm scripts)
Relationships and data flow
• Client → CDN → Next.js server / cached static page
• Next.js server
• At build time: reads src/data/*.json → generates static HTML/JSON
• At runtime (SSR): processes React components, may call lanyard API → HTML + props → client
• Public assets served by CDN directly
• Client sends interactions/events (e.g., dark mode toggle) to React state (src/lib/state.ts)
Architectural patterns and design principles
• Component-Based UI (src/components)
• File-Based Routing (src/pages)
• Hybrid Rendering:
• Static Generation (SSG) for projects & timeline
• Server-Side Rendering (SSR) for dynamic status page
• Utility modules (src/lib) for cross-cutting concerns (SEO, navigation, state)
• Type-Safe code (TypeScript + src/types)
Relevant technologies/frameworks
• Next.js (routing, SSR/SSG, API routes)
• React (UI library)
• Tailwind CSS (utility-first styling)
• TypeScript
• Vercel (hosting & CDN)
• Lanyard API (Discord presence integration)
Elements
• Clear labels for nodes (Browser, CDN, Next.js Server, JSON Data, External API, Static Assets)
• Blue for client-side components
• Green for server/runtime
• Orange for data sources
• Gray for static assets/CDN
• Rectangles for services/components (Next.js, React)
Detail
• React component category (UI widgets, layouts, pages) if needed for a deep-dive
• SSR vs. SSG pathways distinctly
• Call out configuration & deployment (vercel.json, next.config.js) as part of the pipeline