Building a repeatable publishing workflow for content teams

Content teams ship constantly — and the document plumbing is usually copy-pasted from last week. A reusable workflow fixes that.

What a publishing pipeline actually needs - Image normalization so every asset starts as a PDF page. - A merge step that bundles drafts and assets in the right order. - A compression step so the final file fits an email or CMS.

A starter pipeline Try the [Publishing bundle](/workflows/publishing-bundle) workflow — it chains JPG → PDF, [Merge PDF](/merge-pdf), and [Compress PDF](/compress-pdf) end-to-end. Run it on a weekly recurrence and the next newsletter ships without setup.

Where teams get stuck - Mixing PNGs and JPGs without normalizing first — fix with PNG → JPG up front. - Compressing twice and degrading images. Compress once at the end. - Forgetting the recurrence — saved workflows can run on a weekly cadence so the pipeline is always primed.

Explore more publishing workflows.