How pauaua/portafolio works
1. Repository shape
- This is a Next.js App Router portfolio site, not a multi-service application.
- The architecture is mostly static content + client-side interaction, with one small server-side contact endpoint.
2. Application boundary
- The main user-facing routes are:
- app/page.tsx for the landing page
- app/contact/page.tsx for the contact page
- app/api/contact/route.ts for form submission handling
- app/layout.tsx wraps the whole site with shared shell concerns like global styles and persistent UI.
3. Content/data layer
- lib/data.ts appears to be the single source of truth for portfolio content: projects, experience, education, skills, and other structured sections.
- This keeps the page composition thin and makes the sections render from centralized data rather than hardcoding content in multiple places.
4. Internationalization layer
- lib/translations.ts plus components/ui/LanguageProvider.tsx implement ES / EN / FR language switching.
- Language-dependent copy is likely consumed by the section components and UI chrome without a full page reload.
- components/ui/LanguageBanner.tsx is part of that user-facing language selection experience.
5. Page composition
- The landing page is built from reusable section components in components/sections/:
- Hero, About, Skills, Projects, Experience, Education, HowIWork, ContactCTA, ContactForm
- This indicates a section-based single-page portfolio rather than a deeply nested app.
6. Shell and navigation
- components/layout/Navbar.tsx and components/layout/Footer.tsx provide the persistent site chrome.
- components/ui/SideNav.tsx adds desktop-oriented section navigation, which suggests the landing page is long-form and anchored by sections.
7. Interactive portfolio features
- components/ui/ProjectModal.tsx is the main interaction for project details, likely opening richer project metadata from lib/data.ts.
- components/ui/EasterEgg.tsx adds the “hire me” hidden interaction mentioned in the README.
- components/ui/CustomCursor.tsx and components/ui/BackgroundSparkles.tsx are decorative motion layers that sit above the content, not part of the data model.
8. Theme and presentation
- components/ui/ThemeToggle.tsx indicates a dark/light mode system with persisted preference.
- app/globals.css and components/ui/button.tsx suggest Tailwind-driven styling with shared primitives.
- The visual system is enhanced with Framer Motion for animated transitions and hover/scroll interactions.
9. Contact submission flow
- The contact form in components/sections/ContactForm.tsx is the user entry point.
- Submission goes to app/api/contact/route.ts, which acts as the backend boundary.
- The README states this route uses Resend to deliver email, so the app has a real external integration rather than a mock form.
10. Static assets and SEO
- public/CVREALPAPCV.pdf is a downloadable static asset.
- The README mentions a custom favicon/icon and SEO-oriented metadata, which fits Next.js App Router conventions.
- This repo is optimized as a personal brand / recruitment portfolio, so discoverability and polished presentation are first-class concerns.
11. Runtime boundaries
- Most components are likely client components where interaction is needed: theme, language switching, cursor, modals, form, and Easter egg.
- Pure content sections can stay mostly presentational, while the API route is the only clearly server-executed part.
12. Deployment shape
- The architecture is designed for Vercel deployment, with no separate backend or database layer visible in the tree.
- That means the system is essentially: Next.js frontend + serverless contact endpoint + external email service.
Main entry points: page.tsx Home page · layout.tsx Root layout · data.ts Portfolio data · translations.ts Translations
Components 29
App Router
Route handlers and shared application shell
- Root layout · Wraps the site with global styles and persistent providers/chrome
app/layout.tsx - Home page · Main landing page that assembles the portfolio experience
app/page.tsx - Contact page · Dedicated contact route separate from the landing page
app/contact/page.tsx - Contact API · Backend boundary for contact form submissions and email delivery
app/api/contact/route.ts - Global styles · Site-wide styling foundation
app/globals.css
Page Sections
Landing page content blocks
- Hero · Top-of-page introduction and primary branding
components/sections/Hero.tsx - About · Personal background and summary content
components/sections/About.tsx - Skills · Capability overview rendered from structured data
components/sections/Skills.tsx - Projects · Project showcase with richer item metadata
components/sections/Projects.tsx - Experience · Career history and roles timeline
components/sections/Experience.tsx - Education · Academic background section
components/sections/Education.tsx - How I work · Process and working-style narrative
components/sections/HowIWork.tsx - Contact CTA · Call-to-action block leading users toward the contact flow
components/sections/ContactCTA.tsx - Contact form · User-facing form that submits to the contact API
components/sections/ContactForm.tsx
UI Layer
Interactive chrome, motion, and shared UI components
- Navbar · Persistent top navigation for the portfolio site
components/layout/Navbar.tsx - Footer · Persistent bottom site chrome and closing links
components/layout/Footer.tsx - Theme toggle · Dark/light mode preference switch
components/ui/ThemeToggle.tsx - Language provider · Shared language state for ES EN FR switching
components/ui/LanguageProvider.tsx - Project modal · Expanded project detail view sourced from portfolio data
components/ui/ProjectModal.tsx - Side nav · Section navigation for the long-form landing page
components/ui/SideNav.tsx - Language banner · Visible language selection and status affordance
components/ui/LanguageBanner.tsx - Easter egg · Hidden playful interaction layer
components/ui/EasterEgg.tsx - Custom cursor · Decorative pointer treatment layered above content
components/ui/CustomCursor.tsx - Sparkles · Animated background decoration
components/ui/BackgroundSparkles.tsx - Social icons · Reusable social link cluster
components/ui/SocialIcons.tsx - Button · Shared UI primitive used across the portfolio
components/ui/button.tsx
Content Layer
Centralized portfolio data and translations
- Portfolio data · Central source of truth for projects experience education skills and other content
lib/data.ts - Translations · Localized copy for the language switcher
lib/translations.ts
Static Assets
Files served directly from public
- CV PDF · Downloadable resume document
public/CVREALPAPCV.pdf
Connections 40
- Root layout → Global styles: loads · Applies global styling to the whole site
- Root layout → Language provider: wraps · Provides shared language state across routes
- Root layout → Navbar: includes · Persistent header chrome
- Root layout → Footer: includes · Persistent footer chrome
- Root layout → Theme toggle: exposes · Theme preference control in the shell
- Root layout → Custom cursor: enables · Global decorative interaction layer
- Root layout → Sparkles: enables · Global background motion layer
- Root layout → Language banner: surfaces · Language selection affordance
- Home page → Hero: assembles · Landing page is built from sections
- Home page → About: assembles · Landing page is built from sections
- Home page → Skills: assembles · Landing page is built from sections
- Home page → Projects: assembles · Landing page is built from sections
- Home page → Experience: assembles · Landing page is built from sections
- Home page → Education: assembles · Landing page is built from sections
- Home page → How I work: assembles · Landing page is built from sections
- Home page → Contact CTA: assembles · Landing page is built from sections
- Home page → Social icons: uses · Shares social link presentation
- Home page → Side nav: uses · Desktop section navigation for the long page
- Contact page → Contact form: contains · Dedicated contact page centers the form flow
- Contact CTA → Contact form: routes to · Call-to-action leads into the contact form
- Contact form → Contact API: submits to · Form posts to the serverless contact endpoint
- Contact API → Portfolio data: uses · May reference portfolio details for message context
- Hero → Portfolio data: reads · Intro content is populated from centralized portfolio data
- About → Portfolio data: reads · About content comes from shared data
- Skills → Portfolio data: reads · Skills section is data-driven
- Projects → Portfolio data: reads · Project cards and metadata come from shared data
- Experience → Portfolio data: reads · Experience timeline is data-driven
- Education → Portfolio data: reads · Education entries come from shared data
- How I work → Portfolio data: reads · Working-style copy is centralized
- Projects → Project modal: opens · Project items expand into a modal detail view
- Language provider → Translations: provides · Supplies localized strings to UI and sections
- Language banner → Translations: reads · Uses localized labels for language selection
- Navbar → Translations: reads · Navigation labels adapt to selected language
- Footer → Translations: reads · Footer copy can be localized
- Side nav → Translations: reads · Section navigation labels adapt to selected language
- Contact form → Translations: reads · Form copy and validation text are localized
- Theme toggle → Global styles: affects · Theme state is expressed through shared styles
- Button → Contact form: used by · Shared primitive used in form and call-to-action UI
- Button → Contact CTA: used by · Shared primitive used in call-to-action UI
- CV PDF → Footer: linked from · Resume download is surfaced from site chrome or sections