v2026.08.4

Released 2026-08-20.

Features

• CMS content is served from a domain of its own. Published JSON and the images your client uploads now come from minionusercontent.com instead of sharing a domain with the app. How you read them does not change — the Delivery tab shows the URLs, and they are still plain files fetched at build time. What changes is the blast radius: a client site under load cannot affect Minion, and nothing a client uploads can affect Minion’s mail deliverability or reputation. Delivery runs on Cloudflare R2, so traffic to the sites you build stays free however popular they get.
• One page that tells you everything about connecting a front end. The new CMS integration guide carries the URL patterns, the exact JSON each field type produces, complete Astro, Next.js and Nuxt examples you can copy as they are, and the mistakes that look reasonable and are not — rendering pages from the read API, swallowing a failed fetch, re-sorting a list that is already ordered. It is written to be handed over on its own, without following links. For coding assistants, the documentation is also published as plain text at /llms.txt, /llms-full.txt and /llms-cms.txt.

Improvements

• The docs now state who can read published CMS files. Anyone with the URL: published content carries no authentication, and cannot, because that is what keeps your client’s visitors from ever reaching us. The API key protects drafts and writes only. Worth reading before publishing something ahead of time and linking to it later — use a scheduled publish instead.
• Documentation links in the app point at docs.minionworkspace.com.

Fixes

• Avatars, workspace icons and product images are visible again. URLs saved before the storage domain moved pointed at a host that no longer answers, so the images did not come back on a reload.
• Republishing a whole CMS site no longer lists entries whose own files are not written yet. For a moment during a republish, the index could name entries whose individual JSON had not been written — long enough for a build started by that publish to produce a site with missing detail pages.