Developer Documentation

Build with Timepath

Integrate Timepath at the level that fits your stack — embed complete interactive experiences, render Timepath natively in your site, use our frontend components, or build your own frontend on top of the Timepath headless CMS.

Start embeddingGo headless with Liveblog

More managedMore control

  1. iFrameFully hosted. Maximum isolation.
  2. ScriptNative rendering. Managed by Timepath.
  3. ComponentsYour codebase. Your design system.
  4. HeadlessYour frontend, end to end.

Integration levels

Choose your integration level

Start with a simple embed or take full control of the frontend. Timepath stays at the centre of the editorial workflow.

Available

Embed

The fastest way to publish with Timepath.

Create the experience in Timepath and add it to your website or CMS. Timepath manages the content, the frontend and the hosting.

Timepath CMS + Timepath UI

  • Works with virtually any CMS or website
  • Two methods: an isolated iframe, or native rendering in your page
  • Minimal engineering — the editor writes the snippet for you
View embedding docs
Coming soon

Timepath Components

Built for shadcn

Own the frontend. Keep Timepath as your CMS.

Install Timepath components into your codebase and adapt them to your design system. Your newsroom keeps creating in Timepath while your developers control how that content is rendered.

Timepath CMS + your component code

  • Components live in your repository, not behind an iframe
  • Full control over styling and presentation
  • Designed for modern React and Next.js stacks
What we are building
Available for Liveblog

Headless CMS

Maximum frontend control.

Use Timepath as the editorial CMS, read structured content from the data API, and render the entire experience yourself.

Timepath CMS + your UI

  • Your own frontend, architecture and design system
  • Structured content, documented field by field
  • Journalists keep the Timepath workflow they already have
View Liveblog Headless docs

Embed

Two ways to embed

Both keep Timepath as the CMS and the frontend. The difference is whether the story renders in its own browsing context or inside your page.

iFrame

All plans · every embeddable format

Fully hosted. Maximum isolation.

Timepath hosts and renders the complete experience; your page gives it a slot. Styles cannot leak in either direction, and the documented resize helper keeps the height honest as content changes.

  • Fastest implementation
  • Complete style and script isolation
  • Responsive height handling
Add a published story to any page
<iframe
  src="https://embed.timepath.co/timeline/YOUR_ID"
  width="100%"
  height="700px"
  title="Interactive Timeline"
  loading="lazy"
></iframe>

The editor's Share dialog gives you this snippet with the id, a sensible height and the full attribute set already filled in.

View live embed examplesRead embedding docs

Script

Enterprise · Timeline, Liveblog, Collection, Quiz, Poll, GeoStory

Native rendering. Managed by Timepath.

The Timepath renderer mounts the format into your own DOM — no iframe, no fixed height, and the story flows with your layout. Timepath still supplies and maintains the frontend, and the content still comes from the Timepath CMS.

  • Renders inside your page, not beside it
  • Layout flows with your grid — no height to guess
  • Far less work than building the frontend yourself
Mount a format inside your own markup
<div class="tp-quiz" data-timepath-quiz-id="YOUR_ID"></div>

<!-- then load the renderer for that format -->
<script
  src="https://quiz-script.timepath.co/timepath-quiz.umd.js"
></script>

The documented loader also handles a script that is already on the page and mounts every container at once. The embedding guide has it in full.

View live embed examplesRead Script documentation

Timepath Components

Coming soon

Timepath Components are coming

Interactive publishing components, built for your stack.

We’re bringing Timepath’s interactive formats directly into developer codebases through a shadcn-compatible component registry. Journalists continue working in Timepath. Developers own the presentation layer.

Your code
The components become part of your own frontend codebase — reviewed, versioned and deployed with everything else you ship.
Your design system
Typography, colour, spacing and interaction conventions are yours. A Timepath story stops looking like a Timepath story and starts looking like your title.
Timepath content
Editors and journalists carry on working in Timepath. Nothing about the newsroom workflow changes because the rendering moved.
Headless by design
The components consume structured content from Timepath rather than requiring the hosted Timepath frontend.

The registry, the package and the component list will be published here when they are final. Until then, the Script embed renders Timepath natively in your page and the Liveblog data API already gives you the content.

Your applicationyour routes · your layout

Timepath componentsin your repository

Installed into your codebase, styled with your tokens, reviewed and deployed like everything else you ship.

structured content

Timepath CMSunchanged

Journalists keep building timelines, liveblogs, quizzes and maps in the editor they already use.

Architecture

One newsroom workflow. Multiple frontend options.

Timepath provides the editorial infrastructure. You choose the presentation layer — and the newsroom never has to know which one you picked.

  • Managed by Timepath
  • Managed by you

  1. iFrame

    1. Journalist
    2. Timepath CMS
    3. Timepath hosted frontend
    4. Publisher website

  2. Script

    1. Journalist
    2. Timepath CMS
    3. Timepath JavaScript renderer
    4. Publisher website

  3. Components

    1. Journalist
    2. Timepath CMS
    3. Timepath components, in your repo
    4. Publisher application

  4. Headless

    1. Journalist
    2. Timepath CMS
    3. Timepath structured data
    4. Publisher frontend

Compare

Which level fits your team?

The content layer is the same in every row. What changes is who builds and maintains the frontend.

Timepath integration methods compared by frontend, content source, who maintains the UI and engineering effort
IntegrationFrontendContentWho maintains the UIEngineering effort
iFrameTimepath hostedTimepath CMSTimepathLowest
ScriptTimepath managedTimepath CMSTimepathLow
ComponentsComing soonPublisher codebaseTimepath CMSPublisherMedium
HeadlessLiveblog todayPublisher builtTimepath CMSPublisherHighest

Documentation

Start integrating Timepath today

Everything listed here is live and maintained, and written against what is shipping right now.

Roadmap

Developer platform roadmap

What we are building next for technical teams. Nothing here is available yet, and nothing here has a date.

  • Coming soon

    REST API

    Programmatically create and manage Timepath content.

  • Coming soon

    Webhooks

    Receive events and content updates from Timepath.

  • Coming soon

    Authentication

    Enterprise authentication and secure programmatic access — SSO, SAML and token-based access.

  • Coming soon

    Component Registry

    Install Timepath frontend components directly into your application.

Looking for editor documentation?

Step-by-step guides for journalists and editors — building, styling, publishing and embedding each format — are in the Timepath Support Centre.

Visit the Support CentreTalk to our team

Subscribe for updates

Product news, newsroom stories and new formats — occasionally, never spam.