When I decided to rebuild my personal website, my first intention was as direct as possible: open the editor and build it with pure, classic HTML. No weird dependencies, no complex configurations, just plain code to have something functional on the internet.
However, in the world of development, curiosity always wins.
Browsing on YouTube, I started running into several videos talking about Astro. The philosophy they proposed caught my attention: a framework designed from scratch for performance, which by default does not send kilos of unnecessary JavaScript to the browser and allows you to structure everything using clean, reusable components.
I said: “Well, why not? Instead of staying comfortable, I’m going to genuinely learn Astro by building my own website on it”.
The pleasant surprise: a website that flies instantly
Learning a new tool while applying it to a real project is the best way to internalize it. And with Astro, the experience was great from day one:
- Immediate speed: Pages load instantly, without dead time or white screens waiting for a giant JavaScript bundle to finish hydrating.
- Comfortable structure: Being able to write modular components with familiar syntax, separate logic from view, and handle content collections (like the articles in this logbook) in a completely typed way.
- Zero bloat: Only what is strictly necessary is sent to the client.
Seeing how the browser responds instantly when navigating between sections confirmed that the change had been 100% worth it.
The deployment workflow: From Git to Cloudflare in seconds
Having the site ready locally was the first step, but deployment had to be just as agile.
I connected the Git repository directly with Cloudflare. Now the workflow is wonderful:
- I make my adjustments or write a new article locally.
- I do a
git pushto my repository. - Cloudflare detects changes, builds the site automatically, and in a matter of seconds the new version is live across its global network.
Zero dealing with manual servers, complicated Apache or Nginx configurations, or expiring SSL certificates. Everything runs on Cloudflare’s perimeter infrastructure with maximum security and minimum response times.
Discovering the power of Cloudflare beyond hosting
The interesting thing about this process is that I did not stop at using Cloudflare merely as static hosting. Curiosity struck and I started exploring what else they offered.
I have been learning and experimenting with their tools for personal projects:
- Cloudflare Workers: To execute lightweight logic and ultra-fast APIs at the edge of the network (Edge computing) without needing to spin up a traditional server.
- Integrated database: To manage fast data persistence close to users.
- File storage (Storage R2): To store images and media files with complete flexibility.
What has impressed me most is their free tier: it is extremely generous and allows you to prototype, experiment, and stand up real architectures without spending from day one. For any programmer who enjoys tinkering and validating ideas, it is a blessing.
What is in the pipeline
I am still learning and exploring every corner of this ecosystem; I feel I am barely scratching the surface of its full potential.
In fact, I am already working on a new personal idea where I want to involve all these pieces in a single system: Astro on the frontend, Workers for distributed logic, database at the edge, and file storage.
As soon as I have the prototype mature and tested, I will share it here in the logbook with the wins, the stumbling blocks, and the lessons learned along the way.
Sometimes the best reason to start a personal project is not just to have a pretty page, but the perfect excuse to learn something new and take it to production.
