A Lunch Conversation Changed My Website | Ammar NajjarOn this pageCuriosity Has a Way of Growing<br>Settling the Infrastructure<br>More Than a Framework<br>A Lunch Conversation Changed My Website<br>Ammar Najjar · Posted on July 19, 2026 — astromigrationfrontendarchitecturestorytelling<br>Some of the most enjoyable projects I’ve worked on have started in surprisingly ordinary moments. A conversation introduces a new idea, someone shares an experience from their own work, or I come across a different way of approaching a familiar problem. The conversation eventually ends, everyone returns to their daily work, yet one small idea continues to occupy my thoughts. Over the following days that idea slowly grows into documentation, notes, experiments and, occasionally, an entirely new project. Looking back, I can trace many of my favorite learning experiences to moments exactly like these, and rebuilding my personal website became another one of those unexpected journeys.

The story began during a lunch break with one of my fellow Chapter Leads while we were talking about frontend technologies and exchanging experiences from our teams. As often happens when engineers sit together, the discussion wandered naturally between projects, frameworks and the different decisions we make in our day-to-day work. At one point he mentioned that his team had built their frontend with Astro. I recognized the name immediately, yet I realized that my knowledge ended there. He spoke about the framework with genuine enthusiasm, describing how well it suited their use case and how much they appreciated its performance. We continued our conversation, talked about several other topics and eventually returned to work, but Astro quietly remained with me throughout the afternoon.

I’ve always enjoyed exploring technologies that are unfamiliar to me because every mature framework represents years of engineering experience, countless design decisions and a particular way of thinking about software. Reading documentation has never felt like collecting new APIs or memorizing syntax. I enjoy understanding why a technology was designed the way it was, which problems it was created to solve and how its authors approached the trade-offs that every engineering decision inevitably brings. Every exploration broadens my own perspective, and that alone makes the time worthwhile.

That afternoon I opened Astro’s documentation with exactly that sense of curiosity. Within the first few pages I found myself becoming increasingly interested in the philosophy behind the framework. Astro begins with static HTML and gradually introduces JavaScript wherever interactivity contributes to the experience. The simplicity of that idea immediately resonated with me because it reflects a very deliberate way of thinking about websites. Every piece of JavaScript has a purpose, every interactive component earns its place, and the content itself remains at the center of the experience. As I continued reading, I found myself reflecting on my own website and the role I wanted it to play over the coming years.

My website had gradually evolved beyond its original purpose. It still contained technical articles and documentation, yet over time it had become a place where I collected projects, documented architectural decisions, shared experiments and explored ideas that interested me. More recently, photography had become an increasingly important hobby, and I had already started imagining a future where larger images, richer galleries and visual storytelling would naturally become part of the website as well. Those thoughts made me look at my website from a different perspective. Instead of seeing a collection of pages, I began thinking about the experience I wanted readers to have and the kind of foundation that experience deserved.

As those ideas came together, another question quietly emerged. If I were building this website today, with everything I have learned over the past few years, which technologies would I choose? I wasn’t searching for a quick answer because the question itself felt far more interesting than any particular framework. It invited me to revisit assumptions that had settled over time, to look again at decisions I had once considered complete and to approach the entire website with fresh eyes. Questions like these have a remarkable way of expanding beyond their original scope, and I could already sense that I was about to begin something much larger than reading the documentation of a framework I had never used before.

That evening marked the beginning of an engineering exercise that would eventually reshape far more than the frontend framework. It became an opportunity to revisit the architecture of the website, the publishing workflow, the technologies behind it and, perhaps most importantly, the purpose of the website itself. At that point I still had no idea where the journey would lead, yet I was already enjoying the process because curiosity has a wonderful...