Clean up release pages #patch#129
Merged
asteiner-swisstopo merged 1 commit intomasterfrom Mar 23, 2026
Merged
Conversation
This is a follow-up of [a PR comment](#128 (comment)). I have noticed that all release pages follow this structure: ```txt \# Release title \### API & applications \### API - Bug fixes - Announcements: - Announcement 1 - Announcement 2 - [Full changelog][https://link] \### Geodata ``` I see three issues with that: 1. Inconsistent formatting: The heading levels jump from h1 (#) directly to h3 (###). Proper markdown does not skip heading levels. 2. "API & applications": Empty on all pages, not clear what is its purpose. 3. "Bug fixes": It's empty for all pages except 20250514. Removing it along with the "Announcements" reduces the list nesting. To focus on the content, I propose to simplify the structure to this: ```txt \# Release title \## API - Announcement 1 - Announcement 2 - [Full changelog][https://link] \## Geodata ``` The change in heading levels also requires changing the script for the "All releases" page.
ltclm
approved these changes
Mar 20, 2026
asteiner-swisstopo
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a follow-up of a PR comment regarding a change by @ltshb.
I have noticed that all release pages follow this structure:
In an example:
I see three issues with that:
To focus on the content, I propose to simplify the structure to this:
The change in heading levels also requires changing the script for the "All releases" page.
Test link