How eliascoca85/tegrity works
Project type and purpose
• This is a Next.js–based frontend application (a static/SSR “portfolio” or marketing site).
• It was bootstrapped with create-next-app and consists of a single monolithic codebase serving React pages and components.
File structure
• Top level:
• Configuration files (package.json, next.config.mjs, ESLint, PostCSS, jsconfig.json)
• public/ (static assets: images, favicon, etc.)
• src/app/: Next.js “app” directory containing layout.js, page.js, globals.css
• src/app/components/: reusable UI modules (Particles, header, footer, herosection, servicios, proyectos, tecnologias, contactos) each with its JS and CSS
• No separate “api” or “backend” directory—app logic is purely presentation, with optional Next.js SSG/SSR.
Key insights from README
• Uses Next.js App Router and next/font for optimized font loading (Geist).
• Deployed on Vercel (CDN + Edge Functions).
• Development via npm/yarn/pnpm/bun dev.
Main components
a. Client (Browser)
b. CDN/Edge layer (Vercel)
c. Next.js Server (SSR/SSG pipeline)
d. React Component Tree (layout → header, herosection, servicios, proyectos, tecnologias, contactos, footer, Particles)
e. Static Assets (public folder, optimized fonts)
f. CI/CD pipeline (GitHub/Vercel integration)
Relationships & interactions
• Browser → (HTTP request) → CDN/Edge
• CDN/Edge → Next.js Server or serve cached static HTML
• Next.js Server → renders React component tree (SSG at build time or SSR at request time)
• Next.js → fetches static assets from public/ and optimized fonts via next/font
• Build pipeline (Git push → Vercel CI → SSG/SSR build → deploy to Edge CDN)
Architectural patterns & design principles
• Component-based UI (each folder under src/app/components)
• SSR/SSG hybrid (App Router)
• Separation of concerns: global CSS vs per-component CSS modules
• CDN caching for static content
Technologies & frameworks
• Next.js (App Router, SSR/SSG, next/font)
• React
• Vercel (hosting + CDN)
• PostCSS, ESLint, JavaScript/JSX