Media & Marketing
A content pipeline fails quietly: a feed that stops updating, a translation that reads wrong, and it can run for days before a reader catches it.
Pulse is an editorial experiment I run. Content is aggregated and published in more than one language, and nothing should reach a reader without a review step. Some older sitemap URLs 404; I would rather say that than point at a broken archive as proof.
What the domain demands
A stale feed or a mistranslated headline can run for days before a reader points it out. The system has to catch what an editor would catch, before publish, not after a complaint. And a page that exists in three languages is not the same as a page that reads correctly in three languages.
What changes about how I build
Aggregation and translation pipelines run behind a review step rather than publishing straight through, and each piece is traceable back to its source. Where a locale has no value for a field, the fallback is explicit and counted, so a site that looks complete in every language cannot quietly be serving one of them in the wrong one.
- Built against
- Multi-source aggregation / Reviewed AI-assisted translation / Editorial review before publish / Per-locale fallback tracking / Multi-language delivery
Other domains
Different pressure, the same way of building.
Building in Media & Marketing?
Tell me the constraints. I will come back with how I would build against them.