diff --git a/.github/release-notes.md b/.github/release-notes.md
index 912358c6..2f276fd7 100644
--- a/.github/release-notes.md
+++ b/.github/release-notes.md
@@ -1,11 +1,16 @@
 ---
-version: 0.5.0
+version: 1.0.0
 ---
 
-# Forgejo GitHub Theme 0.5.0 - [Short subtitle]
+# Forgejo GitHub Theme 1.0.0 - Forgejo 17, page by page
 
-[1-2 sentence summary of the release.]
+The theme now targets Forgejo 17, and most pages Forgejo has were compared against GitHub and brought in line: Actions,
+project boards, settings, commits, branches, labels and milestones, notifications, the create pages and more. GitHub's
+layouts are rendered by the templates instead of being patched in the browser, so pages no longer shift after they load.
 
 # Compatibility
 
 This release targets Forgejo `17`. It was tested against Forgejo `17.0.0`, including the bundled template overrides.
+
+The templates are bound to Forgejo 17's template data. On Forgejo 16 keep using 0.4.0; install this release together
+with the upgrade to Forgejo 17, stylesheets and templates at the same time.
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 1632685a..32818c65 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -55,7 +55,7 @@ is written for the people who install the theme, so the title and the label deci
 
 Areas: `Actions`, `Auth`, `Branches`, `Code`, `Commits`, `Dashboard`, `Editor`, `Explore`, `Forks`, `Forms`, `Insights`,
 `Issues`, `Labels`, `Milestones`, `Navbar`, `Notifications`, `Organizations`, `Packages`, `Profile`, `Projects`,
-`Pull requests`, `Releases`, `Repository`, `Settings`, `Teams`, `Themes`.
+`Pull requests`, `Releases`, `Repository`, `Settings`, `Teams`, `Templates`, `Themes`.
 
 Reuse an existing area whenever one fits; add a new area only for a page people recognise by that name, and add it to
 this list in the same pull request. Never use file, component or style names as an area.