Interactive storytelling your stack can live with

Embeds that carry their own weight

An embed is one div and one script tag. It fetches its own stylesheet from our CDN and mounts client-side into the element you place, so nothing lands in your global CSS and nothing depends on your framework version. If the embed fails to load, the article around it is untouched. Step-by-step guides for WordPress, Ghost and Webflow live in the integration docs.

Loaded only where it is used

The reader bundle is fetched per embed, on demand. An article with no Timepath embed loads none of it. Because the interactive mounts after your own content has rendered, your page stays static and cacheable and the embed never blocks the story.

CMS-agnostic on purpose

A script tag and a document ID is the whole contract. That is why it behaves the same in a bespoke editorial CMS as it does in WordPress: there is no plugin to maintain against your upgrade cycle and nothing to deploy server-side. Journalists paste an embed code; you review one script origin.

Who may edit, publish and approve

Workspaces and roles map onto how a newsroom already works: who drafts, who publishes, who signs off. It is the same permission model across all ten editors rather than a per-product bolt-on, so onboarding a desk does not mean learning it again.