My Website

My personal site — built to replace a Wordpress install I never wanted in the first place.

Tech Stack

AstroAstroWindTailwind CSSTypeScriptGitHub ActionsNetlifyMarkdown/MDX

Astro because I love it for static sites. AstroWind as the design starting point. Netlify for zero-config deploys.

I dumped my WordPress website to have something I actually built myself. This is now built with Astro and has space for information about me, my projects, and blog posts.

The chances are fairly high that you’re reading this text on my website right now. Unless I copied it somewhere else.

So if you’re on my website — just have a look around, that’s probably the best way to explain the whole thing. And if you’re not on my website, I wonder where you found this text. But feel free to visit ricoklimpel.de.

How it gets deployed

Write

Astro · MDX · Tailwind

Posts and pages as plain files. No CMS, no database.

Verify

GitHub Actions

Types, lint, build — on every push, across Node 18 / 20 / 22.

Build & Deploy

Netlify

Builds independently from CI. Generates fully static output in dist/.

Live

ricoklimpel.de

100% static. No server. Assets cached for 1 year — content-hashed, no stale risk.

Push to main, GitHub Actions verifies the build passes on Node 18, 20, and 22 — plus runs astro check and ESLint. Netlify picks up the same push independently, builds the static output, and deploys it. The /_astro/* assets get a one-year immutable cache header — Astro’s content-hashed filenames mean there’s no stale cache risk.

Back to Projects