Guides
Practical articles on versioning, approval, HTML/JSON/PDF delivery and live drift checks of already-published legal texts.
What is Legal Content Operations?
Legal content distributed across CMS pages, Word documents, and copied snippets makes versioning and live drift detection harder. This guide outlines typical risks.
How structured management, clear reviews, and controlled publishing simplify the management of legally relevant website content.
Multi-site and multi-locale setups place specific demands on variant maintenance and publishing control.
Three artifact forms of the Public Delivery API compared — when HTML fits, when JSON fits and when PDF fits.
How Transactional Legal Text Delivery works: HTML in the email footer, JSON in your own template or PDF as an attachment for order, contract and sign-up confirmations.
How workspaces, brands, and site profiles cleanly model separate clients and brands.
Legal content drift happens when the version visible in production no longer matches the approved version — on websites, in apps, in languages or in transactional emails.
Sequential reviews, threshold approvals, and a ban on self-review as building blocks of auditable processes.
Immutable snapshots, restoration as a new draft, and traceable version histories.
Which legally relevant documents SaaS products typically maintain, and where errors creep in.
Base document, targeted overrides, and avoiding duplicated full texts for clean variant maintenance.
How to attach the approved terms version as a PDF artifact from the Public Delivery API to transactional order confirmations — versioned and traceable.
HTML in the email footer or PDF as attachment: how the approved withdrawal notice reaches transactional confirmations in a versioned way.
Version pinning, effective_at delivery and audit trail: how to establish the link between a transaction and the published version that applied at that time.
Drift originates at publishing time, not when you go looking: one source instead of copied full texts, risk moments like relaunch and caching, plus continuous live reconciliation.
A central base version plus targeted variants for multiple domains, brands and languages — without duplicating full texts, with approval and publishing per site.
TermShelf as a central source and delivery layer for shop systems: HTML, JSON and PDF via the Public Delivery API instead of scattered maintenance in the shop backend.
How Shopware storefronts and order-confirmation emails pull terms, the withdrawal notice and privacy information as a versioned HTML, JSON or PDF artifact from TermShelf — instead of maintaining full texts across sales channels and Twig mail templates.
How transactional Shopify emails pull terms and withdrawal artifacts from an external delivery source: PDF as attachment, HTML fragment in the template or JSON in your own middleware — versioned and traceable to the order timestamp.
How WooCommerce order emails pull the approved terms or withdrawal version as a PDF attachment, HTML fragment or JSON from TermShelf — instead of maintaining legal texts in the theme or mail template that gets overwritten on the next update.
