Five people write here, and each one holds a beat rather than a byline.

Short answer: a beat is a subject area somebody keeps writing about, so the post you are reading about migration was written by the person who writes about migration every time. We do not invent an author per article and we do not publish under a generic editorial account. Five beats cover the whole subject area, which is why ten guides needed no sixth writer.

Marta Oyelaran

Beat: DAM fundamentals, governance, taxonomy and metadata standards.

Marta works on the unglamorous half of asset management, the part where somebody has to agree what a field means before anyone can search on it. Taxonomy design, controlled vocabularies, and the rules that decide what a team is allowed to publish.

Her recurring argument is that most asset libraries fail on description rather than on storage.

Every post by Marta Oyelaran · start with metadata is the whole product

Tobias Lindqvist

Beat: systems architecture and the boundaries between DAM, CMS and PIM.

Tobias spends his time on the seams between content systems. He draws the lines for teams who have accidentally built all three inside one tool, and writes about integration, ownership, and what happens when two systems both believe they hold the source of truth.

Every post by Tobias Lindqvist · start with DAM, CMS and PIM

Priya Raghunathan

Beat: developer experience, APIs, headless DAM and agent tooling.

Priya writes about asset management from the API side: upload endpoints, search queries, transformation URLs and the agent tooling that now sits in front of all of them. Her interest is in what a system exposes to the thing calling it, whether that caller is a build script, a front end, or a coding agent that will never open the admin interface.

Every post by Priya Raghunathan · start with headless DAM

Hana Sorensen

Beat: cost, procurement and vendor evaluation.

Hana covers the buying side: what platforms cost, what the line items hide, and how to tell whether a team has an actual asset problem or a filing habit. She is more interested in helping people avoid a purchase they do not need than in helping vendors close one.

Every post by Hana Sorensen · start with do you need a DAM yet

Ewan Doherty

Beat: migration, rollout, operations and adoption.

Ewan runs DAM rollouts. He writes about the part of the project where twenty years of folder structure has to become something searchable without anyone losing the file they need on Tuesday. His recurring theme is adoption: a library nobody uses is a more expensive failure than no library at all.

Every post by Ewan Doherty · start with migrating off shared drives

How we assign posts

A post goes to the beat that covers it. If no beat covers it, we ask whether the topic belongs here before considering a sixth writer. Within a batch, bylines rotate so no two consecutive posts share an author, and totals stay roughly even.

How we source, verify and correct is on editorial standards.