The pipeline page

When you publish a post, a few things happen in the background: the markdown becomes the HTML readers actually see, audio is synthesised if you asked for it, and — if the audio is included in the podcast — the feed is updated. The pipeline page collects all of this in one view so you can see what finished, what’s still running, and what failed.

Open it from any post: there’s a Pipelinetab alongside the editor. You don’t need to babysit it — jobs run on their own — but it’s the place to check if something looks off.

The live post page on the blog also updates in real time as each job finishes — see Your post goes live right away for what readers see while the pipeline runs.

The render card tracks the conversion from your markdown into the HTML that’s served to readers. This includes optimising images, generating syntax highlighting for any code blocks, and processing math notation. It runs every time you publish (or republish after changes).

If the render job fails, the post stays in its previous rendered state and you can click Retry on the card. The card also shows how long the job has been running and how long it usually takes for a post of this size.

The audio card is the full picture of the text-to-speech flow covered briefly on the Audio synthesis page. The two stages are synthesis (the voice generation) and alignment (the word-by-word timing data that powers the highlighter in the player), each shown with a checkmark when complete, a spinner when running, and a red marker if it failed.

When the job is done, the card surfaces a play button so you can preview the audio, and a download link for the alignment file (the data that powers word-by-word highlighting in the player). For editors and admins, this card is also where the approval buttons live.

The podcast card only appears on posts that have audio and the Include in podcast feed flag enabled. It shows the current status of the post in the feed and the mode used for synthesis. If something needs to be re-pushed to the feed, the card surfaces that too.

Each card shows the job’s timeline as a row of stages:

• Checkmark — this stage finished cleanly.
• Spinner — this stage is running right now.
• Red marker — this stage failed. An error message appears below with the details, and a retry button if a retry makes sense.

While a job is running, the card shows an estimate of how long it usually takes. Once complete, it shows the actual elapsed time so you have a sense of how long to expect next time.