- Client
- GrN.dk (this site) and nowa.dk
- Sector
- AI content automation
- Period
- April 2026 — ongoing
At a glance
The articles on this site are written by a pipeline: every morning it scouts what changed in the web-development and AI world, picks one topic worth a practitioner's attention, writes the piece, draws a sketch-style infographic for it, and publishes — 138 articles since mid-April 2026, one per day, without a stock photo or an image-API key anywhere in the chain. A second, deliberately slower instance runs on nowa.dk: one guarded article a week, with a kill switch.
The challenge
Automated publishing usually fails in one of two directions: content mush (generic posts nobody would sign), or a runaway robot (something embarrassing goes live at 3 a.m. and nobody notices until a customer does). The interesting problem is not "can an AI write an article" — it is building the editorial machinery around it: topic selection that tracks what actually changed this week, images that carry the argument instead of decorating it, and enough guard rails that the system can be trusted to run unattended.
The solution
A nightly pipeline on this site's server: a scout stage gathers candidate topics and ranks them (with a plan bank held in reserve for nights the scout comes home empty), a writing stage produces the article against an editorial prompt, and an illustration stage generates the whiteboard-sketch infographic that leads each piece — drawn by the model itself, so it depicts the article's actual argument. The result lands in Drupal as a normal reviewed-format article.
nowa.dk runs the cautious variant of the same machinery, tuned for a commercial site: a hard cap of one article per week (an explicit owner decision, not a technical limit), plus a kill switch and an auto-pause that stops publication if its checks fail rather than shipping something doubtful.
The results
138 articles live on grn.dk since 18 April 2026 — a daily cadence no freelancer's blog keeps by hand — each with its own infographic, and the weekly guarded feed on nowa.dk running alongside. The pipelines are boring to operate, which is the achievement: failures alert, gaps are visible, and nothing publishes around the guard rails.
This case is deliberately meta: the machinery described here is the same kind sold to clients — AI content automation with editorial control designed in, not bolted on.