Why I Chose SvelteKit and Supabase for My First Portfolio

I mentioned in my first post that it was time to learn something new. For me, the best way to learn is to build. So I built my first-ever portfolio.

Even though I currently focus and engineering management - guiding people, collaborating with customers, and making sure delivery stays aligned with goals, I keep an eye on the UI side of a developer’s life like beautiful designs, thoughtful interactions, and the craft of building for the browser. It also brings back memories of writing TypeScript for our company’s Angular web app.

After watching a few talks and chatting with people in tech, I kept hearing the same thing more than once: Svelte is cool. It felt like a “now or never” moment: I started my journey, my first Svelte driven Website.

I chose Svelte as the frontend framework, and then stepped up to SvelteKit with SSR. The reason was simple: I wanted to write posts, capture experiences, and list projects directly within my site, everything behind a login, with a minimal CMS-like flow that I control. SvelteKit’s file-based routing, server-side rendering, and simplicity seemed like the right fit.

For storage, I went with Supabase. Why Supabase? Honestly, because I’d never used it before, and I wanted to try something new. The Postgres core, row-level security, and straightforward auth made it a strong choice for a small, personal project that could still grow.

TL;DR This setup gives me:

• A fast, modern frontend with SvelteKit (SSR for performance and SEO).
• Auth-protected authoring so I can draft and publish directly on my site.
• A managed Postgres via Supabase, with simple APIs and policies.
• A stack that’s fun to work with and one that nudges me to keep learning.

I have some ideas what I could write next, let’s see where this is going. Stay Tuned!

And again: Shoutout to ChatGPT for the humble proofreading assist!