How javiergoodall99/javiergoodall-portfolio works
Project type and purpose
• This is a full-stack (mostly frontend) portfolio website built with Next.js App Router.
• It renders static pages (SSG) and server-rendered pages (SSR) for dynamic project routes.
• It uses Tailwind CSS for styling, a custom UI component library under src/components/ui, and static data files under src/data.
File structure
• Top-level config: next.config.ts, tailwind.config.js, tsconfig.json, ESLint & PostCSS configs.
• src/app/: App Router layout (layout.tsx), global CSS, entry point (page.tsx), dynamic route under projects/[projectId].
• src/components/: feature sections (hero, about-me, projects, etc.), theme provider, and atomic UI primitives (ui/).
• src/data/: navigation and project metadata as TypeScript modules.
• src/lib/utils.ts: shared utilities.
README insights
• Bootstrapped with create-next-app, deployed on Vercel.
• Uses next/font to optimize the Geist font.
• No external database or API—data is loaded from local modules at build time or on server fetch.
Main components & relationships
a. Client / Browser
b. Next.js application (hosted on Vercel)
• Edge / Serverless Functions: handles SSR/SSG routes
• App Router:
• layout.tsx (shared layout + theme context)
• page.tsx (home)
• projects/[projectId]/page.tsx (dynamic project details)
• Components: UI primitives & feature sections
• Static data imports (src/data/*.ts)
c. CDN: caches static assets from public/ and built pages
d. Vercel Platform: CI/CD pipeline, build & deploy
Architectural patterns & design principles
• Component-based UI (React Server/Client Components)
• SSG for homepage and dynamic routes at build time, SSR/Fallback for new routes
• Theming via context provider (theme-provider.tsx)
• Atomic design for UI primitives (ui/ folder)