How nicomelendez/portfolio works
Project type and purpose
• This is a static, content-driven portfolio website built with the Astro framework.
• It uses TypeScript, Tailwind CSS for styling, and is configured for deployment on Vercel.
• There is no backend or database—content is assembled at build time into static HTML, CSS, and JS.
File structure
Top-level:
• astro.config.mjs, tsconfig.json, tailwind.config.mjs, vercel.json → build & deployment settings
• package.json, pnpm-lock.yaml → dependencies, scripts, and package management
• public → static assets (images, favicon, etc.)
• src/
– pages/ → route definitions (.astro files)
– layouts/ → page wrappers (Layout.astro)
– lib/ → shared utilities and types
– env.d.ts → environment typing
Elements
• Clear labels for each component (e.g., “Astro Build”, “Tailwind Processor”, “Vercel CDN”)
– Rectangles for code & config
– Hexagons for processes (build, deploy)
– Clouds for external services (Vercel, CDN)
• Top layer: Developer workspace → GitHub repo
• Mid layer: Source breakdown
• src/pages (routes)
• src/layouts (page shell)
• src/components (UI atoms & molecules)
• src/lib (helpers & types)
• Output layer: dist/ (static site)
• Delivery layer: Vercel CDN → End user