How adityacodes-root/portfolio works
1. Project type and runtime
- This is a Next.js + React + TypeScript portfolio site built as a mostly static, client-friendly presentation app.
- There is no visible backend, API layer, database, or server-side domain model in the repo tree; the architecture is centered on rendering and interaction.
2. Route structure
- The app uses the Next.js App Router under app/.
- app/page.tsx is the main landing page and likely assembles the one-page portfolio sections.
- app/layout.tsx provides the root shell for all pages, while app/not-found.tsx handles fallback routing.
- This suggests a small route surface with a primary homepage and a custom 404.
3. Page composition model
- The homepage is organized as a section-based single-page experience.
- Individual content areas live in components/sections/: hero, about, skills, experience, projects, testimonials, and contact.
- components/section-wrapper.tsx likely standardizes spacing, anchors, or layout behavior across these sections.
4. Global app shell and cross-cutting UI
- components/header.tsx and components/footer.tsx define persistent site chrome.
- components/loader.tsx, components/cursor-wrapper.tsx, components/custom-cursor.tsx, and components/theme-fade.tsx indicate the experience includes global transitions and interaction polish layered across the page.
- These are presentation concerns, not business logic, but they shape the user flow significantly.
5. Theme system
- The repo has a dedicated theme layer: components/theme-provider.tsx and components/theme-toggle.tsx.
- The README explicitly mentions multiple themes; combined with styles/theme-transitions.css, this implies theme switching is a first-class architectural concern.
- The theme provider likely wraps the app at the layout level so theme state is available globally.
6. Project details interaction
- components/project-modal.tsx suggests projects can be expanded into a modal dialog rather than only being displayed as cards.
- This creates a local interaction boundary: the projects section renders summaries, and the modal presents deeper details when a user selects an item.
7. UI component foundation
- components/ui/ is a large design-system layer built from Radix UI primitives and styled wrappers.
- It includes common primitives such as dialog, dropdown, tooltip, sheet, tabs, accordion, toast, form controls, and more.
- This layer separates low-level accessible interactions from page-specific sections, so the portfolio content can stay relatively clean.
8. Shared utilities and hooks
- lib/utils.ts is the main shared utility file, likely for class-name composition or small helpers.
- hooks/use-mobile.tsx and hooks/use-toast.ts support responsive behavior and ephemeral notifications.
- The same hooks also appear under components/ui/, which suggests some UI primitives are generated or re-exported in a shadcn-style structure.
9. Styling architecture
- Styling is split across app/globals.css, styles/globals.css, and styles/theme-transitions.css, with Tailwind CSS as the primary utility system.
- tailwind.config.ts and postcss.config.mjs indicate a conventional Tailwind build pipeline.
- The presence of both app-level and styles-folder CSS suggests a mix of global base styles and specialized theme transition rules.
10. Asset and content boundaries
- Static assets live in public/, including public/AdityaDubey_Resume.pdf, public/images, public/logos, and public/site.webmanifest.
- This points to content being delivered mostly from the filesystem rather than fetched dynamically.
- The resume PDF and imagery are part of the site’s outward-facing content surface.
11. Responsive and interaction-heavy behavior
- The README emphasizes a “smooth and responsive experience for all devices,” and the code structure supports that with a mobile hook, cursor components, and UI primitives for overlays and drawers.
- The UI stack includes Framer Motion per the README, so animations are likely used for transitions, section reveals, modal behavior, and theme effects.
12. What an architecture diagram should show
- A good diagram would place app/layout.tsx at the top as the root shell.
- Under it, show app/page.tsx composing the section components and shared chrome.
- Add a separate cross-cutting band for theme, cursor/loader, and UI primitives.
- Show static content flowing from public/ into the sections and modal, with Tailwind/CSS and Radix-based primitives supporting the presentation layer.
Main entry points: page.tsx Home Page · ui UI Primitives · layout.tsx Root Layout · projects-section.tsx Projects
Components 29
App Router
Next.js root shell, routes, and page entrypoints
- Root Layout · Top-level application shell and providers for every route
app/layout.tsx - Home Page · Main landing page that assembles the portfolio experience
app/page.tsx - 404 Page · Custom not-found route for missing pages
app/not-found.tsx
Page Sections
One-page portfolio composition and content blocks
- Section Wrapper · Shared framing for anchors, spacing, and section layout
components/section-wrapper.tsx - Hero · Lead introduction and first-screen messaging
components/sections/hero-section.tsx - About · Personal background and summary section
components/sections/about-section.tsx - Skills · Capabilities and technical skill presentation
components/sections/skills-section.tsx - Experience · Work history and timeline content
components/sections/experience-section.tsx - Projects · Project showcase that can open detailed overlays
components/sections/projects-section.tsx - Testimonials · Quotes and social proof section
components/sections/testimonials-section.tsx - Contact · Contact call-to-action and outreach section
components/sections/contact-section.tsx
Interaction Layer
Theme, motion, cursor, modal, and persistent chrome
- Header · Persistent top navigation and branding
components/header.tsx - Footer · Persistent bottom site information
components/footer.tsx - Theme Provider · Global theme context and switching support
components/theme-provider.tsx - Theme Toggle · User-facing control for changing themes
components/theme-toggle.tsx - Theme Fade · Visual transition effect during theme changes
components/theme-fade.tsx - Loader · Global loading or intro animation layer
components/loader.tsx - Cursor Wrapper · Wraps cursor-enhanced interactions across the app
components/cursor-wrapper.tsx - Custom Cursor · Custom pointer treatment for the presentation UI
components/custom-cursor.tsx - Project Modal · Expanded project detail view launched from the projects section
components/project-modal.tsx
UI Primitives
Shared accessible component foundation
- UI Primitives · Shared accessible component library used by sections and overlays
components/ui - UI Hooks · Shared client hooks for mobile behavior and toasts
components/ui/use-toast.ts - Mobile Hook · Responsive breakpoint helper for client interactions
hooks/use-mobile.tsx - Toast Hook · Ephemeral notification state and helpers
hooks/use-toast.ts
Content & Assets
Static files and global styling inputs
- Global CSS · App-wide global styles for the Next.js shell
app/globals.css - Styles Globals · Additional global styling layer
styles/globals.css - Theme Transitions · Theme transition-specific CSS rules
styles/theme-transitions.css - Static Assets · Resume, images, logos, and web manifest delivered from public files
public - Utils · Common helper functions such as class composition
lib/utils.ts
Connections 37
- Root Layout → Theme Provider: wraps · Layout installs global theme context
- Root Layout → Cursor Wrapper: wraps · Layout applies cursor interaction shell
- Root Layout → Global CSS: loads · Root app shell imports global styles
- Root Layout → Styles Globals: loads · Additional global style layer is included by the app
- Root Layout → Theme Transitions: loads · Theme transition styles are made available globally
- Home Page → Header: composes · Home page includes persistent header chrome
- Home Page → Footer: composes · Home page includes persistent footer chrome
- Home Page → Hero: composes · Landing page starts with the hero section
- Home Page → About: composes · Landing page includes about content
- Home Page → Skills: composes · Landing page includes skills content
- Home Page → Experience: composes · Landing page includes experience content
- Home Page → Projects: composes · Landing page includes project showcase
- Home Page → Testimonials: composes · Landing page includes testimonials
- Home Page → Contact: composes · Landing page ends with contact section
- Home Page → Section Wrapper: uses · Sections share a common framing component
- 404 Page → UI Primitives: uses · Fallback route can rely on shared UI components
- Theme Toggle → Theme Provider: controls · Toggle updates global theme state
- Theme Fade → Theme Provider: reacts to · Theme transitions depend on shared theme state
- Loader → Root Layout: signals · Loading state is part of the global shell experience
- Cursor Wrapper → Custom Cursor: contains · Wrapper provides the custom cursor implementation
- Projects → Project Modal: opens · Project cards expand into a modal detail view
- Project Modal → UI Primitives: builds on · Modal is implemented using shared dialog and overlay primitives
- Hero → UI Primitives: builds on · Content sections use shared UI components for presentation
- About → UI Primitives: builds on · Content sections use shared UI components for presentation
- Skills → UI Primitives: builds on · Content sections use shared UI components for presentation
- Experience → UI Primitives: builds on · Content sections use shared UI components for presentation
- Projects → UI Primitives: builds on · Project cards and controls rely on shared primitives
- Testimonials → UI Primitives: builds on · Content sections use shared UI components for presentation
- Contact → UI Primitives: builds on · Contact section uses shared UI components for input and layout
- UI Primitives → Utils: uses · Shared components rely on helper utilities
- UI Hooks → Mobile Hook: includes · Responsive hook is part of the shared UI support layer
- UI Hooks → Toast Hook: includes · Toast hook is part of the shared UI support layer
- UI Primitives → UI Hooks: depends on · Primitive components use shared hooks for behavior
- Static Assets → Hero: feeds · Images and resume assets support the landing content
- Static Assets → Projects: feeds · Project visuals and logos support showcased work
- Static Assets → Contact: feeds · Static assets support contact and branding content
- Theme Provider → Theme Toggle: exposes · Provider makes theme state available to the toggle