From 42dea03bf4eea040e3fefdba696525d2a23e9f8f Mon Sep 17 00:00:00 2001 From: Madraka <8898640+Madraka@users.noreply.github.com> Date: Fri, 23 Oct 2026 16:40:17 +0300 Subject: [PATCH] docs(demo-newsroom): release notes for 0.3 to 0.6 Four posts the editor agent publishes through MCP: the public launch and our own site (0.3), first-class collections (0.4), typed fields (0.5), and listings, expiry and structured data (0.6). Co-Authored-By: Claude Opus 5.5 Signed-off-by: Madraka <8898640+Madraka@users.noreply.github.com> --- .../content/posts/collections-you-can-see.md | 23 +++++++++++++++++++ .../posts/listings-and-structured-data.md | 23 +++++++++++++++++++ .../content/posts/open-source-on-npm.md | 21 +++++++++++++++++ .../content/posts/typed-fields.md | 23 +++++++++++++++++++ 4 files changed, 90 insertions(+) create mode 100644 apps/demo-newsroom/content/posts/collections-you-can-see.md create mode 100644 apps/demo-newsroom/content/posts/listings-and-structured-data.md create mode 100644 apps/demo-newsroom/content/posts/open-source-on-npm.md create mode 100644 apps/demo-newsroom/content/posts/typed-fields.md diff --git a/apps/demo-newsroom/content/posts/collections-you-can-see.md b/apps/demo-newsroom/content/posts/collections-you-can-see.md new file mode 100644 index 00000000..ea22144b --- /dev/null +++ b/apps/demo-newsroom/content/posts/collections-you-can-see.md @@ -0,0 +1,23 @@ +--- +slug: collections-you-can-see +title: "0.4: collections people can see and manage" +summary: Events, team members or jobs are no longer strings on an entry. Collections have names, icons, URLs and settings, and agents create them only with a person's approval. +tags: release, content +--- +An agent could always put an entry into any collection it named, and Studio only ever showed posts. Collections are now first-class. + +## A registry without a migration + +A site's collections live in its settings: a name in every language, an icon, whether they appear in feeds and the sitemap, and how their lists are sorted. Collections that already had entries count as declared from the first read, so existing sites keep working without rewriting anything. + +## URLs that cannot collide + +Each collection has its own address, such as `/blog/{slug}` instead of `/posts/{slug}`. Changing it moves the entries and leaves permanent redirects behind. The first entry of a new collection is checked against every other collection, archive and reserved path, so two collections can never answer the same URL. + +## People decide on new collections + +Agents read the registry before they write. Creating or changing a collection waits for a person who may change site settings, in every mode. An entry in a collection nobody declared is refused. + +## In Studio + +Every collection appears in the sidebar with its own list, editor and settings: names, URL, categories and tags, comments, and how it is listed. diff --git a/apps/demo-newsroom/content/posts/listings-and-structured-data.md b/apps/demo-newsroom/content/posts/listings-and-structured-data.md new file mode 100644 index 00000000..47b22fe6 --- /dev/null +++ b/apps/demo-newsroom/content/posts/listings-and-structured-data.md @@ -0,0 +1,23 @@ +--- +slug: listings-and-structured-data +title: "0.6: listings by field, expiry and structured data" +summary: Lists can be filtered and sorted by a field, ended events leave them on their own, and entries can describe themselves to search engines. +tags: release, seo +--- +Typed fields now do work on the public site. + +## Structured data from fields + +A collection can map its fields to an Event, a job posting, a product or a recipe. The site then publishes the matching schema.org data instead of a generic article. A mapping is checked when it is saved, and an entry missing a required value publishes none rather than incomplete data. Studio previews the result for any entry. + +## Expiry without a background job + +A collection can end its entries at a date field: an event after it ends, a job when applications close. Ended entries leave lists, feeds, the sitemap and search, or disappear entirely. Nothing is rewritten and no scheduler runs; the renderer works it out on each request, and the edge cache expires at the right moment. + +## Lists by field + +Pages can list a collection by its fields, such as upcoming events, soonest first. Themes, Studio, the API and agents share one evaluator, so they always agree on what a list contains. A listing page for a collection is one click in Studio. + +## A feed per collection + +Every collection with its own address now has a feed at `
/rss.xml`, including on sites whose themes were copied before this release. diff --git a/apps/demo-newsroom/content/posts/open-source-on-npm.md b/apps/demo-newsroom/content/posts/open-source-on-npm.md new file mode 100644 index 00000000..e72d6c26 --- /dev/null +++ b/apps/demo-newsroom/content/posts/open-source-on-npm.md @@ -0,0 +1,21 @@ +--- +slug: open-source-on-npm +title: "0.3: open source, on npm, running our own site" +summary: The repositories are public, every package installs from npm, and cloudhal.com itself is a Cloudhal site that updates the way any other site does. +tags: release, launch +--- +Cloudhal is now public. The source is open, the packages are on npm, and `npm create cloudhal` sets up a site in an empty folder. + +## Our own site, our own releases + +cloudhal.com runs on Cloudhal. A new release reaches it the way it reaches anyone: a dependency update opens a pull request, the site and Studio are bundled as a check, and merging deploys through Workers Builds. If the site or Studio stops answering after a deploy, a post-deploy check rolls it back. + +Running our own site found problems that tests did not. A redirect from `www` looped because the edge cache was keyed by path rather than host, so every response now varies by host. A theme copied by an older version broke when a helper changed its signature, so the old signature came back as a deprecated overload, and a frozen copy of the old theme now builds in CI on every change. + +## A playground anyone can open + +try.cloudhal.com gives every visitor a private site for an hour, in its own Durable Object, with Studio and the public pages. Nothing needs an account. + +## Fast first paint + +Pages preload their fonts with Early Hints, and the fallback fonts are measured to match the web fonts, so text does not jump when they load. A render check flags fonts without a matched fallback. diff --git a/apps/demo-newsroom/content/posts/typed-fields.md b/apps/demo-newsroom/content/posts/typed-fields.md new file mode 100644 index 00000000..d24af8e2 --- /dev/null +++ b/apps/demo-newsroom/content/posts/typed-fields.md @@ -0,0 +1,23 @@ +--- +slug: typed-fields +title: "0.5: typed fields for every collection" +summary: A collection can define its own fields, from dates to images, and agents, Studio and themes all read the same definitions. +tags: release, content +--- +An event needs a start time and a venue, a job a salary and a deadline. Collections can now define typed fields: text, rich text, number, yes or no, date, date and time, link, image and choice. + +## One checker for everyone + +The same checker validates values in the store, the API and the MCP server. It also produces the JSON Schema agents receive, so an agent's output is checked before a person is asked to approve it. Fields can be required before publishing while drafts save freely. + +## Languages decided per field + +Each field says whether it is translated. A price is shared and read from the original, a description is written per language. Changing only a shared value no longer marks translations as out of date. + +## Changes that never lose data + +Renaming a field, changing its type or its language setting, and removing it are explicit operations. Each shows what it will change, takes a snapshot first, waits for approval and can be reverted. A plain edit of the definitions is refused if it would drop a value. + +## Forms and themes + +Studio builds the entry form from the definitions and has a builder for them. Themes get resolved, formatted values and a component that lists them, so new sites show fields without custom code.