Public changelog page
The app exposes a public /changelog page that renders the CHANGELOG.md markdown for logged-out prospects and current operators.
Open: https://flatsbratislava.com/changelog
Who sees it
- Logged-out visitors — prospects evaluating the platform see what's been shipped and how often.
- Logged-in operators — quick reference for "did we ship that fix yet?" without bouncing to GitHub.
What it shows
The page renders CHANGELOG.md from the repo root as a vertical timeline. Each entry has:
- Date
- A short label (Feature / Fix / Polish / Security)
- One-paragraph description in operator language
- A backlink to the GitHub issue(s)
Entries are written for operators, not developers — no commit SHAs, no "refactored X into Y", no Zod schema talk.
Updating
The page auto-renders from CHANGELOG.md on the next deploy. Edit the file, push, the public page updates.
If you want a richer per-feature walkthrough — screenshots, before/after — that goes in the User manual instead. The public changelog is a one-line summary; the user manual is the full reference.
vs the user manual's changelog
| Surface | Audience | What |
|---|---|---|
| Public /changelog | Logged-out + logged-in | One-line ship notes per change |
| User manual changelog | Logged-in operators | Per-batch summary with backlinks into the manual pages affected |
They serve different purposes — the public one is marketing-and-reference; the user manual one is the doc-side index of what was added/updated to which page.
Implements: gh#305 (public /changelog page).