Publish and sync — Hub sync and static ZIP

Sync to Dekimu Hub so your Hub site links your documents, or download a static ZIP to publish on your own site.

Once you have a saved draft, you have two ways to put the document where users can find it: sync to Dekimu Hub so your Hub site can link to your documents, or download a ZIP of your drafts to publish on your own site.

miniterms never hosts your documents as the canonical location. Your own site is always where the live URL lives.

Sync to Dekimu Hub

Hub sync records the current version of every document as your published baseline. Your Hub site's footer links to the document URLs in miniterms' publish record, which Hub reads when you publish your Hub site. You record those URLs through the API (PUT /api/v1/publish).

  1. Open Publish in the sidebar.
  2. Click Sync to Hub.
  3. miniterms records the current versions and timestamps the publish record. Publish your Hub site again to pick up the links.

If you regenerate documents after a previous sync, the Documents page shows Out of sync — sync again to push the latest versions. Syncing is idempotent; syncing the same version twice overwrites with the same value.

Download ZIP

The static export gives you your latest saved Privacy Policy, Terms, Cookie Policy and DPA drafts as Markdown files in a single archive, ready to publish on your own site.

  1. Open Publish in the sidebar.
  2. Click Download ZIP.
  3. The archive downloads to your browser. Extract it and publish each draft on your site, in your CMS or converted to your site's format.

Each draft that carries a provenance receipt begins with a provenance comment:

<!-- Dekimu-APR: <claimId> · verify https://verify.dekimu.com/v/<claimId> -->

Its Agent Provenance Receipt shows this exact text was saved in miniterms at that time. Keep it in the file — it is harmless to end users and links the published text back to its receipt.

Canonical location rule

When a document URL changes (you move to a new domain, restructure your site), record the new URL through the API (PUT /api/v1/publish), re-sync to Hub and publish your Hub site again. The URL you record is what your Hub site's footer links to. If the URL goes dead, users clicking your footer link will hit a 404.