How srijani-chakroborty/my-portfolio works
Project Type and Purpose
• This is a full-stack (mostly front-end) portfolio website built with Next.js, styled via Tailwind CSS, with animations provided by Framer Motion.
• There is a minimal API layer (src/pages/api/hello.js), but the primary focus is on server-side-rendered (SSR) and statically-generated (SSG) pages.
File Structure
• Top-level configuration:
• .eslintrc.json, jsconfig.json for linting and path aliases
• next.config.js, postcss.config.js, tailwind.config.js for build and styling
• src/components/: reusable React components (e.g., NavBar, Footer, AnimatedText, custom hooks)
• src/pages/: Next.js page-based routing (index.js, about.js, projects.js, articles.js) + API routes
• src/styles/: CSS modules and global styles
Main System Components
A. Browser / Client
• User’s web browser interacting via HTTP/HTTPS
B. Next.js Serverless Runner
• Handles SSR and SSG pages
• Serves dynamic content from src/pages/*.js
C. Static File Server / CDN
D. API Layer
• Next.js API Routes (src/pages/api/hello.js)
• Node.js process running next build/next start
• PostCSS & TailwindCSS integration
F. External Libraries
• Framer Motion (animations)
• Tailwind CSS (utility-first styling)
• PostCSS, ESLint, jsconfig
Architectural Patterns & Design Principles
• Component-Based UI: modular React components under src/components/
• Page-Based Routing: automatic file-system–based routing in src/pages/
• Hybrid Rendering: SSR for dynamic pages, SSG for static pages (e.g., projects, articles)
• Separation of Concerns:
• Components vs. Pages vs. Styles vs. Public assets
• Build configuration vs. source code