From Zero to Astro: A Minimalist Tech Stack for IT Nerds

As a dedicated IT nerd, you hold your own digital footprint to the highest standards: maximum control, uncompromising portability, an open-source foundation, and zero unnecessary overhead.

When I set out to rebuild the digital presence for gecko knowledge, the requirements were clear: no bloated monolithic CMS, no WordPress baggage, and no proprietary cloud lock-ins. Instead, I opted for a rigorous “keep it simple” approach leveraging modern web technologies.

Here is a look under the hood at how an OSS stack, Astro, and edge-hosting come together in practice.

1. The Tech Stack: Modern, Open Source, Zero-Bloat

At the center is Astro—currently one of the most pragmatic concepts in the frontend ecosystem. Instead of shipping tons of JavaScript to the client like a traditional Single Page Application, Astro defaults to pure, static HTML.

  • Open-Source Principles: The entire ecosystem relies on free standards, MDX for content-driven documentation, and Tailwind CSS for utility-first styling.
  • No Framework Overload: Interactivity is only injected where strictly necessary via an Islands Architecture. The rest is pure, unadulterated performance.

2. Architecture & Portability: Independence as a Design Goal

For any tech enthusiast, vendor lock-in is a massive red flag. The entire setup was designed from day one to remain maximally portable:

  • Content as Code: Content lives entirely as Markdown and MDX files directly inside the Git repository. No proprietary database, no hidden SQL queries. If you have the code, you have the website.
  • Hosting Agnosticism: Currently deployed via high-performance edge networks (Cloudflare Pages), the site could be moved to any S3 bucket, Nginx server, or alternate CDN within seconds thanks to the pure static build output (dist/). No server maintenance, no patch-day stress.

3. Engineering Details: Bot Protection & Automation

Even on a smaller scale, clean engineering pays off. Two examples from the current setup:

  • Client-Side Email Obfuscation: Instead of exposing raw mailto: links to scrapers or running a bloated PHP contact form backend, the email address (hello@geckoknowledge.ch) is dynamically assembled using vanilla TypeScript directly in the client’s browser. It keeps scrapers at bay without annoying the user.
  • Automated Sitemap Generation: Manual XML sitemaps are error-prone and ripe for automation. Thanks to the @astrojs/sitemap package, the sitemap-index.xml is compiled directly from the routing tree during every CI/CD build, verified cleanly at the edge via standard HTTP requests.

4. DevOps, GitOps & Infrastructure as Code

Even though this is “just” a static website, the workflow strictly mirrors enterprise paradigms:

  • GitOps (Git as the Single Source of Truth): Every change—whether it’s a blog post, a configuration update in astro.config.mjs, or a new contact page—is declared as code in the repository. The state of the repo is the exact state of the website. Rollbacks are as trivial as a git revert.
  • Configuration as Code: No clicking through hosting GUI panels or manual server tinkering. Routing is determined deterministically by the file structure in src/pages/, and integrations are declared cleanly in code.
  • Automated CI/CD Pipeline to the Edge: The deployment path consists of three steps: git add -> git push -> done. A push triggers an isolated build pipeline on Cloudflare Pages, handling dependency resolution, static compilation, sitemap generation, and global edge distribution automatically.

Conclusion

At the end of the day, it proves an old IT truth: The best codebase is the one you never have to maintain.

With this setup, the platform is blazing fast, completely maintenance-free, and future-proof—leaving the focus right where it belongs: tinkering with cool tech and building clean solutions.

(Crafted via vibecoding with ❤️ & Gemini)