How ezequiel-dev93/portafolio works
Project type and purpose
• This is a static, content‐focused personal portfolio site built with Astro (a static site generator).
• The README and file tree show it’s the “Astro Starter Kit: Basics” scaffold, customized with sections for profile, experience, projects, skills, and contact.
File structure
• Top‐level files:
• astro.config.mjs, tsconfig.json – Astro and TypeScript/JS tooling configs
• package.json, pnpm-lock.yaml – dependency management
• env.d.ts – ambient typings
• Directories:
• src/pages – route definitions (.astro pages translate directly to URLs)
• src/layouts – top‐level layout templates
• src/styles – global and component SCSS files
• public – static assets (images, favicon)
• dist – the build output (HTML, optimized assets ready for deployment)
README for additional insights
• The README confirms typical Astro commands (dev, build, preview) and no back-end services by default.
• No external databases or server APIs are part of this starter kit—purely a static front-end.
Main components and interactions
a. Developer workstation
– Source code (src/, public/, config files) in Git repo
– npm/pnpm toolchain + Astro CLI
b. Build system
– Astro build process (astro.config.mjs)
– SCSS compiler, PostCSS/Tailwind (if used), image optimizers
– Outputs to dist/ directory
c. Deployment platform
– Static hosting (Netlify, Vercel, GitHub Pages, or any CDN)
– Continuous Integration (optional): GitHub Actions or similar
d. End-user browser
– Fetches HTML/CSS/JS from CDN
– Executes client-side JS for interactivity (Dark Mode toggle, form validation)
e. (Optional) External integrations
– Contact form submission service (e.g., Netlify Forms, Formspree, custom API)
– Analytics, social media embeds, etc.