How krimsonjosh/portfolio works
Project type and purpose
• This is a static-site portfolio built with Astro (an SSG framework).
• Purpose: compile .astro components, Markdown content and CSS into a static website for deployment.
File structure
• Top-level:
• astro.config.mjs, package.json, tsconfig.json → build/configuration files
• public/ → static assets (images, logos, favicon)
• src/
– components/ → reusable UI pieces (Header, Footer, Hero, etc.)
– layouts/ → page wrappers (BaseLayout, MarkdownPostLayout)
– pages/ → file-based routes (.astro pages and Markdown posts)
– scripts/ → client-side JS (menu toggling)
– styles/ → global CSS
• Patterns: component-based design, file-based routing, Markdown-as-content.
README
• Confirms basic Astro template, commands for dev, build and preview.
• No runtime server; everything is prebuilt into /dist/.
Detail
• Every top-level directory as a source input to the build process.
• Both static assets and generated assets.
• That the final output is entirely static, eliminating runtime servers.
• If using CI/CD, show build triggers on push/merge.