Updates page goes live

What changes

From today, /en/updates gives you a structured trail of every change to navigator.berlin: data refreshes (rent index, noise, election data, Stolpersteine OSM sync), feature releases (Kiez score, compare mode, atlas polish) and methodology changes.

Three feed formats

Every update is available as:

• RSS 2.0 at /updates/rss.xml
• Atom 1.0 at /updates/atom.xml
• JSON Feed 1.1 at /updates/feed.json

Every feed reader (NetNewsWire, Reeder, Inoreader, miniflux) detects the auto-discovery links in the page head and subscribes with one click.

Categories

Five categories structure the trail:

• Data update: an existing layer has fresh values (for example a rent index refresh).
• Feature: a new function in the atlas or inspector.
• Methodology: a change to calculations, thresholds or aggregation rules.
• Data source: a new or changed primary source.
• Licence: a change to layer licences or attribution requirements.

Filter via URL: /en/updates?cat=feature,methodik.

SEO and LLM trail

Every entry has its own URL /en/updates/{slug} with Schema.org BlogPosting. LLM agents can cite the update history in a structured way, and search engines index every entry as a long-tail page.

Maintainer workflow

Update entries are Markdown files under _content/updates/. There is no admin UI and no database. The workflow: create a file, fill in the frontmatter, write the body, commit, push. The build updates the sitemap, RSS feed and JSON-LD automatically.

Step by step: see docs/runbooks/add-update-entry.md.