Editorial systems, video pipelines, and websites

Editorial Systems Architecture

Most organisations are rich in knowledge (research, archival records, metadata, ongoing projects) but poor in how that knowledge is structured and shared. I design the pipelines that extract, stabilise, and shape that material into repeatable formats.

This means content modelling, CMS integration, publishing workflows with well-placed checkpoints for human input, and the data structures that let editorial teams stay in control while the system handles the grunt work. I define what gets published, in what form, and across which channels.

At the Eye Filmmuseum I worked with curators and developers to create a shared model that matched both institutional language and digital requirements: a single, coherent platform representing a complex identity without flattening it. I've done similar work for publishers, cultural institutes, and research teams.

The architecture determines how your work evolves publicly. You own it. You're not locked into a platform or dependent on a vendor.

Video Pipelines

I build programmatic video pipelines using Remotion and React. Instead of editing each video by hand, I design systems where data drives the output: structured content goes in, rendered video comes out.

This approach works for short-form social content, data visualisations, and any scenario where you need many variations from a single template. The Kunstlijn walking tour videos are a good example: location data, artwork metadata, and narration combined into a series of short films, each generated from the same pipeline. The RGB glitch work pushes the format in a more experimental direction: generative visuals driven by code rather than a timeline.

If your team produces repeatable visual content (product explainers, social clips, event recaps) a video pipeline removes the bottleneck. You update the data, and the system produces the next batch.

Websites

I build custom websites and web applications using React, Next.js, and modern tooling. Fast, flexible, and maintainable. Built around your content, your goals, and your team.

A template is a space, not a solution. I start with the fundamentals: what the site needs to express, who it's for, and how identity, content, and structure support that purpose. From editorial systems to user profiles, I identify key data sources and figure out how they shape the experience. Structure comes first.

Design systems, structured content, analytics, performance: I handle the technology so you can focus on the work. For teams who simply need a new site, I design and ship that quickly. For teams who want more, the same foundation extends into a broader publishing system over time.

Every site I build is designed to grow with your practice, not against it.