Vibe Coding in Practice: How This Website Is Built

There is a lot of talk about AI that can write code, but it stays abstract quickly. So instead of another general explanation, I would rather show what it actually means, using a concrete example: the website you are reading right now.

What vibe coding is

Vibe coding is building software by describing what you want in plain language to an AI coding assistant, instead of writing every line of code yourself. You set direction and check the result, instead of being the one typing syntax. See the Vibe Coding dictionary entry for the short version.

It is not the same as letting the AI run unsupervised. Someone still needs to know what a good result looks like, be able to read the code that comes out, and catch what is wrong. Without that, it quickly becomes something that looks right on the surface but is not under the hood.

How michaelkirkegaard.com is actually built

This website, both the Danish version at michaelkirkegaard.dk and this English version, is built and continuously maintained with Claude Code as the coding assistant. This is not a one-off demo. It is the actual workflow every time something needs to happen on the site:

• New landing pages and articles. I describe what the page needs to contain and why, and the structure is built in the same code and design language the rest of the site already uses.
• Dictionary entries like the one you are reading now. New terms, definitions, and deeper explanations are added directly into the site’s content structure, not in a separate system.
• Fixes and polish. When something looks wrong, an arrow is misplaced, or a page does not look consistent on mobile versus desktop, it gets fixed the same way: described, built, checked.
• Images and alt text. Even the illustrations on articles, like the one at the top of this page, are generated and inserted through the same process, with alt text and file names set correctly from the start.

Before anything goes live, it is built locally and checked to make sure it actually works, both technically and visually. It is the same quality control a developer would apply, just with a different split of who writes the code.

Why I am showing this instead of just mentioning it

It is easy to say you “work with AI.” It is another thing to have a site where that can actually be verified. This article, the dictionary entry, the image at the top of this page, and the structure itself, all of it is a product of the exact process just described. That is why I think it is worth writing about, rather than mentioning it in passing somewhere.

Why it matters for marketing

This hits the marketing side of a business directly. The classic bottleneck has always been that a new landing page, a technical SEO fix, or a new article has to wait on developer resources, often for weeks. When the person who understands the marketing and the strategy can also ship the change directly, that wait disappears. Content, structure, and technical fixes can go from idea to live markedly faster.

It is also part of how I already work on SEO, where Claude is already part of the tech stack for research and briefs. Vibe coding is the next layer of that: not just using AI to prepare the work, but for the actual build.

An honest limit

Vibe coding is not a shortcut to skipping quality. It still requires someone who understands what good looks like, why a structure makes sense for SEO, and when a result is not good enough yet. The tool has changed. The responsibility for the result has not.