Publishing
From CMS to waveform: a sane publishing pipeline
Audio publishing breaks when it lives outside your CMS. Here is a lightweight pipeline that keeps editors in familiar tools.
From CMS to waveform: a sane publishing pipeline. Demo — illustrative only.
Single source of truth
Your article body should remain canonical. Audio, transcript, and summary should be derived artifacts with explicit versions—especially when legal or corrections are involved.
Most teams start with a simple rule: no audio publish until copy is approved. The nuance is what happens on update—regenerate, diff the transcript, and re-approve only what changed.
If corrections require a developer, your pipeline is still too fragile.
Structured embeds beat pasted scripts
Use components that accept player configuration as data. That keeps spacing predictable in templates and makes accessibility fixes global instead of per-article.