How sonnymonroe/mike_abramo_dev_portfolio works
Project type and purpose
• This is a single-page, static portfolio site built with SvelteKit.
• It uses file-based routing for pages, TailwindCSS for styling, Vite as a bundler, and is deployed to Vercel as a static site.
File structure
• Top level:
• package.json, vite.config.js, svelte.config.js, tailwind.config.js (configuration & build)
• src/ – application source code
– app.html, app.css (global static files used by SvelteKit)
– components/ – reusable Svelte components (Header, Footer, Main, Step, Table, VideoCards)
– lib/ – shared utilities or JS modules
– routes/ – file-based routes (+layout.svelte, +page.svelte)
– images/ – locally served images
• No backend code—entirely client-rendered or prerendered.
README insights
• Tech stack: SvelteKit + Tailwind + Vite + Vercel
• Deployment target: Vercel, so the build produces static files served via CDN/Edge.
Main components
a. Browser (User)
b. Vercel Edge/CDN
c. SvelteKit application (SSR/SSG layer)
d. Vite build pipeline
e. Source code structure: Routes, Components, Static Assets
f. External services: FontAwesome CDN, particles.js JSON, email link (mailto)
Relationships and data flow
• Developer → GitHub → Vercel (CI/CD)
• Vercel CI: npm install → npm run build (Vite + SvelteKit prerender) → deploy static assets
• File-based routing: clicking nav links loads generated HTML/JS for each route
Architectural patterns & design principles
• File-based routing (SvelteKit)
• Component-based UI (Svelte components in src/components)
• Static site generation (SSG) on Vercel for performance & SEO
• Utility-first CSS (Tailwind)
• Build abstraction via Vite
Sample component grouping
• Routes layer: +layout.svelte, +page.svelte
• Components layer: Header, Footer, Main, Table, etc.
• Config/build layer: svelte.config.js, vite.config.js, tailwind.config.js
Detail
• Directory’s role in the flow
• How environment variables flow from Vercel UI → build → code (import.meta.env)
• That all routing is client-side after initial load or prerendered at build time