My domain was basically bricked. Cloudflare errors every time someone tried to visit it, and not in a “once in a while” way, but like 10+ times a day. At some point you stop debugging and start rebuilding.
So I did exactly that.
I decided to spin up a SvelteKit-based portfolio website, mostly because:
- I needed something stable online
- I wanted full control
- I’d never properly used Svelte before, which felt like a skill issue worth fixing
The Idea
Instead of hardcoding everything and calling it a day, I built the site around a custom admin page. The whole portfolio is configurable from there: content, structure, whatever. No redeploys just to tweak text. That alone already felt like a win.
The goal wasn’t overengineering. Just clean, flexible, and mine.
Learning Svelte (on purpose, accidentally)
I went into this knowing basically nothing about Svelte beyond “people on the internet won’t shut up about it.” And it urns out that they were onto something.
SvelteKit forced me to think differently compared to React/Vue:
- Less boilerplate
- More “just write the thing”
- Reactive logic that actually feels intuitive once it clicks
I didn’t spend weeks on it either. The project came together pretty fast, and the learning curve was surprisingly chill.
The Result
Now I have:
- A working, stable portfolio
- Zero Cloudflare rage
- A new framework in my toolbox
- A site that I can customize without touching the code every time
Honestly, this was one of those projects that starts out as a fix and ends up being a straight upgrade.
Cloudflare broke my site, but SvelteKit fixed my skill issue.