How jairc137/portafolio works
Project type and purpose
• From the README and file tree, this is a front-end web application built with Next.js (using the new “app” directory), TypeScript, React and Tailwind CSS.
• It’s essentially a personal portfolio/resume website that uses static generation (SSG) or server-side rendering (SSR) for pages, serves static assets from public/, and is intended to be deployed on Vercel (or any CDN).
File structure
• Top-level config files:
• next.config.ts, tsconfig.json – Next.js and TypeScript configuration
• tailwind.config.js, postcss.config.mjs, eslint.config.mjs – Styling and linting
• package.json/package-lock.json – deps and scripts
• public/ – static assets (PDFs, images, served directly by the CDN)
• src/app/ – Next.js 13+ App Router pages and layouts; contains global layout, error/not-found, and nested about page
• src/components/ – shared React components (Hero, Navbar, ProjectsSection, etc.) imported into pages
• No backend/API folder detected → purely front-end / static.
README insights
• No special backend services or external APIs documented.
• Uses next/font to optimize a cloud-hosted font (Geist) at build time.
• Intended for local dev via npm run dev and deployment on Vercel.
Detail
• Call out the routing flow from src/app/page.tsx → page components → layout.tsx.
• Where Tailwind config is applied and where global CSS lives.
• Build step (next build) and the serve step (next start or Vercel serverless).