How muhammadnoman2/my-portfolio works
1. This repository is a Next.js App Router project for a largely single-page, content-driven site. The file structure suggests a portfolio/marketing-style experience rather than a multi-page CRUD app or backend service.
2. The top-level application boundary is app/. app/layout.tsx defines the root shell and global metadata/styling, app/page.tsx is the main composition point, and app/globals.css provides the global theme/reset layer. In architecture terms, the page is assembled from reusable sections inside a single route.
3. The primary UI is broken into section modules under components/sections/: Hero, About, Skills, Experience, Projects, Testimonials, and Contact. These are the main content domains that would appear as blocks on the page and are the key units to use when drawing the page structure.
4. Shared content is centralized in constants/data.ts. That file likely serves as the content/data source for multiple sections, keeping copy, lists, and card data out of the visual components. This is the main data flow: constants feed sections, sections render UI.
5. The design system is split into two layers:
- components/ui/ contains reusable primitives like button, card, input, textarea, badge, and separator.
- components/icons.tsx centralizes iconography.
This is consistent with a shadcn/ui-style component setup, supported by components.json.
6. Motion and interaction are a distinct subsystem. components/animations/ contains reusable animation wrappers and effects such as AnimatedSection, Reveal, StaggerContainer, AnimeHeading, AnimeCounter, and MagneticButton. These are likely used by the section components to add entrance animations and micro-interactions.
7. There is also a dedicated motion utility layer in lib/motion.ts, which likely holds shared animation variants/configuration, and hooks/useLenis.ts, which suggests smooth scrolling behavior via Lenis. This means scrolling/animation behavior is intentionally abstracted away from page content.
8. The layout/chrome is separated into components/layout/Navbar.tsx and components/layout/Footer.tsx. These frame the page and likely provide section navigation and site identity, while the main content remains inside the section components.
9. components/ui/SkillTicker.tsx is a specialized presentation component used by the skills area. It indicates that the skills section is not just static text; it includes an animated or continuously scrolling visual element.
10. The Contact section includes form primitives from components/ui/input.tsx and textarea.tsx, but there is no API route or server action visible in the tree. Architecturally, that means contact handling is either purely client-side, uses an external service, or is incomplete in this repo snapshot.
11. Static/SEO assets are in public/manifest.json, robots.txt, and sitemap.xml. That indicates the site is configured for discoverability and possibly PWA/browser metadata, which is important when diagramming the deployment surface.
12. Tooling and runtime boundaries are standard Next.js/TypeScript:
- TypeScript config in tsconfig.json
- linting via eslint.config.mjs
- styling via postcss.config.mjs
- build/runtime via Next.js in the Node/Vercel ecosystem
The README also references next/font, so font loading is handled by the framework rather than custom CSS assets.
13. Deployment automation exists in .github/workflows/deploy.yml, so there is a CI/CD path independent of local development. The README points to Vercel as the primary deployment target, so the likely production flow is GitHub push → workflow/build → Vercel-hosted site.
14. Overall, the architecture is best drawn as: a thin Next.js application shell, a single-page composition layer, shared content/constants, reusable UI primitives, and a separate animation/smooth-scroll subsystem. There is no visible database, server API, or external data ingestion layer, so the system is mostly static/presentation-focused.
Main entry points: page.tsx Home page · data.ts Content data · AnimatedSection.tsx Animations · layout.tsx Root layout
Components 21
App shell
Next.js App Router entry points and global styling.
- Root layout · Defines the global shell, metadata, and shared styling for the app.
app/layout.tsx - Home page · Assembles the single-page experience from shared sections.
app/page.tsx - Global styles · Global reset and site-wide styling layer.
app/globals.css
Page content
Single-page sections that make up the portfolio experience.
- Navbar · Top-level navigation and site identity chrome.
components/layout/Navbar.tsx - Footer · Bottom page chrome and closing site information.
components/layout/Footer.tsx - Hero · Opening section and primary visual introduction.
components/sections/Hero.tsx - About · Personal background and summary content block.
components/sections/About.tsx - Skills · Capabilities showcase with animated skill presentation.
components/sections/Skills.tsx - Experience · Work history and timeline-style content.
components/sections/Experience.tsx - Projects · Portfolio/project showcase content.
components/sections/Projects.tsx - Testimonials · Quotes and social proof content.
components/sections/Testimonials.tsx - Contact · Contact form and outreach call-to-action.
components/sections/Contact.tsx
Shared UI
Reusable presentation primitives and data-driven UI pieces.
- Content data · Central content source consumed by multiple sections.
constants/data.ts - Skill ticker · Specialized skills presentation component.
components/ui/SkillTicker.tsx - UI primitives · Reusable shadcn-style inputs, buttons, cards, badges, separators, and textarea.
components/ui/button.tsx - Icons · Centralized iconography used across the site.
components/icons.tsx
Motion layer
Animation wrappers and scroll/motion utilities.
- Animations · Reusable animation wrappers and interaction effects.
components/animations/AnimatedSection.tsx - Motion config · Shared animation variants and motion helpers.
lib/motion.ts - Smooth scroll · Lenis-based smooth scrolling behavior.
hooks/useLenis.ts
Support
Metadata, icons, and deployment/tooling boundaries.
- Web manifest · Public manifest and site discovery metadata.
public/manifest.json - Deploy workflow · GitHub Actions deployment automation.
.github/workflows/deploy.yml
Connections 31
- Root layout → Global styles: loads · Root layout applies the global stylesheet.
- Root layout → Home page: wraps · Layout provides the shell around the home route.
- Home page → Navbar: includes · Home page composes the navigation chrome.
- Home page → Hero: includes · Hero is the first major section on the page.
- Home page → About: includes · About section is part of the single-page flow.
- Home page → Skills: includes · Skills section is part of the single-page flow.
- Home page → Experience: includes · Experience section is part of the single-page flow.
- Home page → Projects: includes · Projects section is part of the single-page flow.
- Home page → Testimonials: includes · Testimonials section is part of the single-page flow.
- Home page → Contact: includes · Contact section closes the page content.
- Home page → Footer: includes · Footer anchors the bottom of the page.
- Hero → Content data: reads · Hero content is sourced from shared constants.
- About → Content data: reads · About section uses centralized copy/data.
- Skills → Content data: reads · Skills section uses shared skill and profile data.
- Skills → Skill ticker: uses · Skills section uses the ticker presentation component.
- Experience → Content data: reads · Experience section is driven by shared content.
- Projects → Content data: reads · Projects section is driven by shared content.
- Testimonials → Content data: reads · Testimonials section is driven by shared content.
- Contact → UI primitives: uses · Contact form uses shared input and textarea primitives.
- Contact → Content data: reads · Contact section may use shared contact details or copy.
- Navbar → Animations: uses · Navigation likely uses shared motion wrappers or effects.
- Hero → Animations: uses · Hero uses motion wrappers for entrance and emphasis.
- Skills → Animations: uses · Skills section uses motion-enhanced UI elements.
- Projects → Animations: uses · Projects section uses motion wrappers for reveal effects.
- Contact → Animations: uses · Contact section uses animated interactions where needed.
- Animations → Motion config: relies on · Animation components use shared motion config.
- Smooth scroll → Motion config: coordinates · Smooth scroll behavior is part of the motion layer.
- Home page → Smooth scroll: enables · Page experience is expected to use smooth scrolling.
- Root layout → Web manifest: publishes · App shell contributes to public metadata and manifest surface.
- Root layout → Icons: shares · Layout-level presentation may use centralized icons.
- Deploy workflow → Home page: builds · Deployment workflow builds and ships the Next.js app.