Wrote the campaign plan and strategy, ran the weekly execution rhythm, kept the planning document current, and translated direction into concrete work for the team.
GroenLinks-PvdA De Wolden
One merged local list, one public line, and one working platform under election deadlines.
Campaign work
GroenLinks-PvdA De Wolden
Digital campaign lead and tech lead. Municipal election campaign, 2026.
In De Wolden, this was the first time GroenLinks and PvdA had to operate as one local list. The job was to make that workable in public, not just on paper.
I led the digital campaign platform and much of the working system around it: site build, hosting, docs, chat, assistant tooling, automation, media production, publishing, analytics, and the cadence that kept the team moving.
From 19 January 2026 onward, the work settled into a weekly cadence: candidate pages, print runs, QR actions, assistant sessions, press work, and a Monday/Thursday publishing rhythm under election deadlines.
I rebuilt the national GroenLinks-PvdA campaign language in Ghost, then adapted, hosted, and operated it for De Wolden as a usable local platform.
Scope
Turn a merged local list into a working campaign system.
A joined local list does not become coherent by itself. It needed a plan, a platform, and a publishing rhythm that volunteers and candidates could actually use once the timetable became real.
Internally, I kept planning, strategy, tooling, and reporting structured instead of letting them disappear into chats and email. Publicly, the campaign site and assistant work remained visible enough to inspect from the outside.
Rebuilt the national GroenLinks-PvdA language in Ghost, adapted it for the local campaign, and hosted the public site plus the supporting stack on infrastructure I operated myself.
Edited photos, designed posters and sandwich boards, shot campaign videos, and handled green screen, grading, subtitling, compression, and final exports.
Built campaign-specific assistant and automation flows for article drafting, press workflows, social scheduling, internal support, and a public question-and-answer layer around the programme.
Systems
Build the campaign system around the public site.
The website was only the visible surface. Underneath it I built a working stack for planning, documentation, assistant flows, press handling, and social distribution.
Platform and workflow
Take the national language and make it locally usable.
I rebuilt the national GroenLinks-PvdA campaign language in Ghost, adapted it for the local list, and hosted the site on infrastructure I operated myself. That gave the combined campaign a strong public face from day one.
I also had to make it publish quickly, survive load, support people pages, policy pages, news, and calls to action, and stay consistent enough that the campaign looked like one organisation instead of a fragile merger.
Ghost theme clone, local hosting, campaign site, structured content, public publishing.
Execution and automation
Use assistant tooling as campaign infrastructure.
I built the assistant layer around the programme and the site, used it for both public and internal support, and connected it to the wider publishing flow rather than treating it as a novelty.
Around that, I also wired Ghost tags into Ocoya and Zammad flows, AI-generated channel copy, article preplanning, ticketing, and campaign reports that kept communication and execution tied together.
Assistant API, Outline, Ocoya, Zammad, article drafting, press automation, and structured campaign reporting.
Public record
Public references from the campaign.
Most campaign work disappears into private chats, last-minute edits, and tired volunteers. This one left a public trail: a live site, a bylined assistant article, and local press on the chatbot.
Primary reference
The assistant became public enough to be covered locally.
The campaign site carried the original article under my byline. It explained a programme that could be read, listened to, and discussed through a chatbot built around the programme.
When local press picked that up as a primeur for GroenLinks-PvdA in De Wolden, the assistant stopped being a private experiment and became visible campaign infrastructure.
Read the local coverage →Campaign site
Public campaign platform
The public site carried the local list, people pages, news, programme material, and calls to action in one coherent campaign front end.
Open the campaign site →Bylined article
AI accessibility article
I published the original article under my own byline, explaining how the programme could be read, heard, and discussed through a chatbot built around the campaign programme.
Read the assistant article →Next
Elsewhere on this site.
Campaign execution under deadline. Oegema is the current role.