How pratham82/portfolio-v5 works
Project type and purpose
• This is a full-stack portfolio website built with Next.js and TypeScript.
• Front-end: React components styled with Tailwind CSS.
• Back-end: GraphQL API (in a separate repo) providing blog posts, projects, and contact data.
• Dev-ops: Uses ESLint, Prettier, Husky, and GitHub Actions for CI.
File structure
• pages/ – Next.js routes:
– pages/*.tsx are used for SSG/SSR page rendering (home, about, blogs, projects).
– pages/api/ implements serverless functions (e.g., blogPosts.ts) that proxy or enrich data.
• components/ – Reusable UI pieces (cards, header, footer, theme switcher).
• content/blogs/ – Markdown files for statically generated blog posts.
• lib/apollo/ – Apollo Client setup for GraphQL queries.
• src/graphql/queries/ – GraphQL operations used at build time or runtime.
• interface/, src/data/, src/utils/, src/hooks/ – Structured data models, helpers, and custom hooks.
• public/ – Static assets.
• styles/ and tailwind.config.js – Global CSS and Tailwind configuration.
• Config files (.eslintrc.json, .prettierrc, husky hooks, GitHub workflow ci.yml) manage code quality and CI/CD.
README for additional insights
• Confirms this is a Next.js TS template with built-in tooling.
• Points to a backend “portfolio-api” GraphQL service.
Detail
• Every distinct layer (UI, data fetch, serverless, backend).
• Don’t lump everything under “Next.js”—split out SSG, SSR, and API routes.
• How interfaces and GraphQL queries map to data sources.
• Call out tooling (ESLint/Husky, GitHub Actions) as part of the overall pipeline.