prayag29-sahu/prayagsahuportfolio

1. This repository is a personal portfolio site built with Next.js using the App Router. The top-level structure is very small: app/ defines the route shell and landing page, while components/ holds the reusable page sections and UI pieces.

2. The application entry points are app/layout.jsx and app/page.jsx. layout.jsx provides the global document structure and site-wide wrappers, and page.jsx is the main single-page portfolio surface that composes the landing experience from section components.

3. The page is organized as a vertically stacked, mostly static marketing/portfolio layout. The major content blocks live under components/sections/ and include:

- HeroSection

- AboutSections

- Education and Education2

- SkillCard

- ProjectCard

- AchievementCard

- CTA

- ContactSection

4. Navigation and framing are separated into components/layout/. Navbar.jsx and Footer.jsx handle the persistent top and bottom chrome around the section content, so the architecture is “shared shell + composed sections” rather than a routed multi-page app.

5. There are a couple of reusable interaction/UI primitives in components/ui/. CursorBubble.jsx and ParallaxSection.tsx suggest the portfolio uses small motion/scroll-affordance effects. These are supportive UI utilities rather than core data holders.

6. Styling is primarily global and utility-driven. app/globals.css sets application-wide styles, while tailwind.config.js and postcss.config.* indicate Tailwind CSS is the main styling system. components/sections/About.css shows there is at least one section-specific stylesheet layered on top.

7. The app is asset-heavy and mostly static. public/ contains the CV PDF and many image folders for certificates, school/college records, project screenshots, and other portfolio evidence. These assets feed the section components directly and are a key part of the content model.

8. There is no sign of a backend, CMS, database, or API layer in this repo. The data flow is essentially: static content and media from public/ and JSX props/component composition -> rendered portfolio sections -> one scrollable page.

9. The stack mixes JavaScript and TypeScript. Most components are .jsx, but components/ui/ParallaxSection.tsx and next-env.d.ts indicate TypeScript support is enabled for at least some UI code. next.config.ts and tsconfig.json reinforce that the project is set up for a typed Next.js build.

10. Tooling is standard frontend lint/build tooling: ESLint (eslint.config.mjs), type checking, and PostCSS/Tailwind processing. README.md is minimal, so the repo is largely self-describing through its file structure rather than documented subsystems.

11. For an architecture diagram, the key boundaries are:

- App shell (layout)

- Single landing route (page)

- Section components

- Shared layout/navigation

- Shared motion/UI primitives

- Static asset store in public/

12. In practice, the site is best drawn as a one-page portfolio composition pipeline: layout wraps the page, the page assembles section modules, the sections consume static media/content, and shared UI components provide consistent interaction and visual effects.