Platform admin

Changelog

The Glozr changelog is both a public-facing release-notes page and a content surface authored inside the admin. It's how customers learn what shipped, and how the team makes sure those messages actually reach people.

Where it lives

Public: /changelog — visible to anyone with a workspace login.
Authoring: /admin/changelog — restricted to super-admins.

Format standards

Entries follow the Keep a Changelog convention and use semantic versioning (e.g. v1.4.0). Each entry supports:

Markdown with standard sections: Added, Changed, Fixed, Removed, Security.
Headings, bullet lists, bold text and inline code spans.
Unsupported formatting falls back to plain text rendering.

Status lifecycle

Status	Behavior
draft	Default state. Invisible to customers; filtered from the public `/changelog` page.
published	Visible to customers. Version number becomes immutable to preserve historical linkbacks.
archived	Hidden from the public listing but preserved for legacy URL references.

Note. Once published, you cannot renumber a version. To correct a mistake, archive the bad entry and publish a new one.

Distribution channels

JSON feed. The /changelog.json endpoint returns the most recent 100 published entries as machine-readable JSON — handy for dashboards, Slack bots, or no-code platforms like Make and Zapier.

In-app banner. Authenticated workspace members see a notification banner when there's a published entry newer than their last_changelog_seen_at timestamp. Dismissing the banner updates that timestamp via POST /changelog/seen.

Creation & management

You can author entries through the admin UI or via the command line. The CLI is idempotent on version numbers, so it's safe to bake into a release script:

php artisan changelog:add --version=v1.5.0 --title="..." --released_at=2026-05-15

Entries persist as JSON at storage/app/private/changelog-entries.json — same rationale as the Kanban board: development DB resets don't wipe release notes. The system auto-seeds from markdown source files in database/changelog-entries/v*.md on first read, so you can ship release notes from git when you prefer.

Source markdown format

Each markdown source file requires frontmatter:

---
version: v1.5.0
title: Short release title
released_at: 2026-05-15
status: published
---

### Added
- ...

### Fixed
- ...

The body is standard markdown and renders automatically on the public changelog. Place the file in database/changelog-entries/ and it gets picked up on the next read.

Note. Released entries for Glozr are coming soon. The first published entry will be v1.0.0 — Initial release; subsequent versions will follow the format above.