ZADA - The Freamework for This Site

The "renaissance of serverless"

Why this approach (my constraints)

This website is deliberately optimized for a very specific use case: a single software engineer, low traffic, and almost no “dynamic product requirements” such as a blog, guestbook, webshop, login, or contact forms.

In that context, the best architecture is the one with the smallest maintenance footprint:

• fast to develop
• fast to load
• robust in production
• transparent enough that I can understand every moving part.

What I wanted to avoid

• Operational overhead (servers, databases, deployments, monitoring)
• Update pressure (CMS/plugin ecosystems that require constant patching)
• Opaque behavior (too many layers of abstraction, “magic” configuration)
• Fragile add-ons (features that break the page if a single script fails)

What I wanted instead

• Static-first delivery: HTML/CSS/JS served directly from a static host/CDN
• Minimal runtime: just enough JavaScript for navigation and small UI enhancements
• SEO-ready output: real, indexable pages generated from the same content
• Optional features: isolated “widgets” that only run when the page includes their containers

I previously ran this site on a classic CMS (WordPress). While it offers features out of the box, it also introduces ongoing maintenance, performance overhead, and a lack of transparency. ZADA is the opposite: a small, readable codebase with predictable behavior.

AI Assistant

I started this project to learn more about serverless architectures and to experiment with them.

as there were some problems to solve that were a little bit tricky, and I did not want to spend too much time On it, I decided to realize it as a peer programming project with AI assistant within JetBrains Webstorm API.

The index page basically consists of four "div" elements for navigator, main content, sidebar and footer

Further, a small script is loading content into navbar, sidebar and footer

Und das Meta-Update hier: