◆ KI und WordPress WP Meetup Hamburg #140
Deutsch

Chapter 9

Static or generated

Two ways a page comes into existence — and the difference decides how reliably an AI can work on it.

  • Static: the HTML already exists. It is the result.
  • Generated: the HTML appears on request, out of database, theme, plugins, filters and hooks.
  • In the second case you do not write the result. You write the thing that produces it.
  • For an AI that means: in one case it can check what it wrote. In the other it cannot.
  • Same model, very different reliability. Not because of the AI, but because of the distance to the output.

What you cannot look at before it exists, you cannot check either.

What each side costs

Neither camp wins. Both charge you, just in different places — and you decide per project which bill you would rather pay.

  • Static — in favour

    Nothing runs, so nothing can crash. No PHP at the front, no database on the network, no weekend updates. What you see is what shipped — you can read it, check it, version it. And it is absurdly cheap to host.

  • Static — against

    Every change needs somebody with access to the files. No roles, no approvals, no editor. And it scales badly: see the staircase on the next slide.

  • Generated — in favour

    Roles, permissions, approvals, search, forms, translations — all there, without anyone building them. The client changes things whenever they like. This is what a CMS was invented for, and at that it is unbeatable.

  • Generated — against

    You never write the result, you write the machine behind it. One update, one plugin, one filter, and the output changes without you touching anything. More surface, more maintenance, more that can break.

The staircase

It always starts the same way: one page, static, done. And then the client comes back with the next wish.

  1. One page. Perfectly fine. Static is exactly right.
  2. Add a contact page. Now you need a form.
  3. A form. Now you need a service that sends mail.
  4. A mail service. Now you need a webhook you do not entirely understand.
  5. Embed a video. Now you need consent handling.
  6. Consent handling. Now you need a cookie banner.

Five steps from "static is enough" to a CMS you built yourself — only worse.