Duggie CMS 0.9.0: A continuity commitment in the Terms, a rebuilt About page, and archive/restore that keeps your keys.

A continuity commitment in the Terms, a rebuilt About page, and archive/restore that keeps your keys.

Added

• A 90-day shutdown notice is now a term of the Terms of Service, and the "No lock-in" page explains what happens to your content in every scenario, including if we shut down.

• The changelog you are reading is served from a Duggie JSON asset, upserted from git on every release.

• The demo now seeds two sites, Riverside Studio, which you own, and Fieldstone Bakery, where you are an Editor, so both roles can be tried in one session.

• A ten-step demo tour runs from the Projects page through editing copy and seeing it on the live site, and a reload resumes where you were.

• Most of a demo project's settings are open to change; only the demo's own keys and webhook delivery stay as they are, with the reason shown in place.

• Editors: The project overview shows an Editor how much storage the project has left for uploads and the largest file it takes.

• Developers: An llms.txt at the site root describes Duggie CMS and where the documentation lives, for AI assistants that read it.

Changed

• Editors: The About page tells the origin story in first person and names every piece of the stack.

• Signup buttons say "Join the waitlist" while registration is closed, instead of promising a signup that opens a waitlist.

• Legal pages checked line by line against the code; the Terms, Privacy and No lock-in pages now describe exactly what the app does.

• The traffic charts on the Projects page and the project overview read day by day: hover or drag across them, or use the arrow keys, to see each day's request count.

• The card shown when a link to the site is shared carries the page's headline alone, large enough to read on a phone, since every app prints the description beside it anyway.

• An account left over its project slots past the notice's deadline, with no billing change pending, is now brought within its slots once a day: the extra project moves to free limits or is archived, as the notice said, and the owner is emailed.

• On the Projects page a project someone else owns has a dashed border, and its Free badge says whose free slot it is on.

• Project cards count the assets awaiting review, put requests beside their trend line, and show no traffic figure while a project is still on its setup checklist.

• The asset list opens as a table until you pick a view in your settings.

Fixed

• Developers: Unarchiving a project restores the same API keys it had, so nothing needs reconnecting. Archiving still stops serving.

• Developers: Batch upsert validates JSON assets against the project's field rules, the same as the editor does.

• Open Graph and Twitter share tags on the public pages.

• Dialogs ignore repeat clicks while a request is in flight.

• The project overview's daily trend labeled each day as the one before for anyone west of UTC; the chart now reads the day the server counted.

• When a complimentary slot ended with no free slot to fall back to, the project was not archived but the email said it was, every day; the archive now lands, and the email names only what actually moved.

• Withdrawing an invitation from the Members page is recorded in the project's activity as a withdrawal by the person who did it, where it used to read as a decline.

• The activity page's user filter no longer names the support person behind a row shown as Support; it lists Support instead.

• The subscription page no longer offers to release a complimentary slot as if it were paid, and a paid slot can be released while a complimentary one is holding a project.

• An archive or unarchive in the activity feed reads "2 API keys revoked" rather than a raw field name.

• Editors: The Action needed rows on the Projects page no longer send an Editor or Viewer to a settings page they cannot open; they say an owner or admin has to generate the keys or enable the project.

• Uploads by a project member were measured against the member's own storage rather than the project owner's; they now count against the owner's account, which is the one the project belongs to.

Security

• Linking a Google account to your Duggie account is now bound to the session that started it by a signed, short-lived token, and a link that does not carry it is refused.

Full changelog: https://duggiecms.com/changelog#v0.9.0