K
← Back to blog
· 3 min read

Hello world

Notes on why I rewrote my personal site in Astro 5 + Cloudflare after years of vanilla HTML, and what I plan to publish here.

#meta #astro #cloudflare

My personal site lived in vanilla HTML + CSS + JS for years. It worked — but I was accepting a silent friction every time I wanted to publish something new, translate a section, or test a component. This is the first note of the rebuild.

Why Astro 5

I’m a lifelong PHP developer and I build enterprise management systems at Suite HUB. But for my personal site I don’t need a server: I need speed, good SEO, and the ability to publish in Markdown without fighting a CMS. Astro 5 with its Islands Architecture gives me exactly that: static HTML by default, selective hydration where it matters, and native MDX for articles like this one.

Why Cloudflare

The final stack ended up being 100% Cloudflare:

  • Pages for static hosting with automatic builds.
  • Workers for serverless endpoints (contact form, future APIs).
  • D1 and KV for data that doesn’t fit in MDX.
  • Access for the private admin area — zero auth code.
  • MailChannels for free, unlimited email sending from Workers.

This matters because I already have PROOQ infrastructure on other providers, and I didn’t want to mix more dependencies. Cloudflare solves nearly everything with a single vendor.

What I plan to publish here

  • Technical decisions with their why, not just how.
  • Field notes from Suite HUB and the projects I deliver.
  • Learnings from operating between Panama and the US.
  • Every once in a while, something on drones, networking, or electronic security.

Nothing planned in an editorial calendar — I publish when I have something worth saying. If you read, I ask one favor: if something resonates or feels wrong, let me know. The comments block at the end is open.

Comments

Comments via GitHub Discussions — requires GitHub login.

Comments pending configuration (Giscus).