singhaakashdeep/softwarestacked

1. Repository shape

- This is a single Next.js 16 frontend application (softwarestackedfrontend) that acts as a static portfolio site.

- The repo does not contain the AI, backend, or infrastructure systems described in the content; those are presented as portfolio case studies.

2. Primary runtime boundary

- The application is built with React + TypeScript + Next.js App Router and is intended to be statically exported for deployment on static hosting/cPanel.

- That means the architecture is mostly client-side presentation plus build-time rendering, not a server-driven app.

3. Route structure / page subsystem

- The src/app directory defines the site’s top-level routes:

- / home page

- /about

- /resume

- /work/[slug] dynamic project detail pages

- src/app/layout.tsx is the global shell for shared site structure, metadata, and layout-wide providers/styles.

4. Content flow

- The core content flow is data-driven rather than fetched from an API.

- src/data/projects.ts is the key content source for featured projects and likely feeds both the homepage project section and the dynamic work pages.

5. Dynamic project details

- src/app/work/[slug]/page.tsx is the main dynamic boundary in the app.

- It likely resolves a project slug against the local projects dataset, which keeps the portfolio fully static while still supporting per-project detail pages.

6. Shared layout and navigation

- src/components/layout/Navbar.tsx provides the persistent navigation layer across pages.

- src/components/PageTransition.tsx adds route transition polish, indicating the app emphasizes presentation and motion rather than complex state management.

7. Homepage composition

- The homepage is assembled from reusable section components:

- Hero.tsx

- FeaturedProjects.tsx

- ArchitectureDiagram.tsx

- This suggests the landing page is a section-based narrative: introduce the author, surface key work, then reinforce systems-thinking visually.

8. UI component layer

- src/components/ui/* contains reusable primitives such as button, card, badge, dialog, and sheet.

- These are a design-system layer used to keep the portfolio consistent and reduce page-specific markup duplication.

9. Styling and presentation

- Styling is handled with Tailwind CSS plus global stylesheet entry points in src/app/globals.css and src/styles/globals.css.

- tailwind.config.ts, postcss.config.js, and components.json indicate a componentized Tailwind setup, likely influenced by shadcn-style conventions.

10. Assets and downloadable content

- public/Aakash_S_resume.pdf is a static asset exposed directly by the site.

- The /resume route likely wraps this asset in a presentation page, separating the downloadable document from the browser-rendered resume view.

11. External systems shown in the portfolio

- The site describes external technologies and deployments such as FastAPI, PostgreSQL/pgvector, MCP, LangChain, Docker, AWS, and Kubernetes.

- These are reference architectures in the content, not runtime dependencies of the frontend itself.

12. Operational posture

- The repo is optimized for fast static delivery and portability: no database, no app server, and no runtime API dependency inside this codebase.

- The deployment model is therefore “build once, host as static files,” which fits the cPanel/public_html workflow described in the README.