Roadmap and release history

This is the one place in the External Docs that retains project chronology — every other document describes only the system as it currently is.

• What's planned or known-broken lives as GitHub Issues on the project's repository — github.com/hoejriis/hoejriis-dk/issues. That list is the live backlog: proposed features, bug reports, and known limitations in what's already shipped, each kept current where the work is actually tracked rather than copied into a document that would immediately start drifting. Issues are grouped by status: Ready for Development (specified in enough detail to build), Needs Design (needs a design pass first), and Backlog (a known idea, not yet scheduled).
• What's actually shipped is recorded as GitHub Releases — one Release per deployed batch of work, in plain language, with concrete steps to confirm each change on the live site. The admin sidebar's Documentation tree's Release notes section (see Administrator quick start) shows the site's deploy history sourced directly from these — each entry its version/tag, date, and notes. A repository with no Releases yet simply shows an empty list here, not fabricated history.

Every other document in /_docs/ describes only what's actually shipped — if a doc and the site disagree, the doc is out of date, not the site. Nothing proposed, in progress, or deferred is described as available anywhere outside this page.