Nested grouping of details

- Group incidents by year
- Group incidents themselves, only keeping the most current / recent one expanded by default
- Added a section on how to add a new incident to the status page in the README.md

Author: hansmannj

README.md

@@ -80,3 +80,33 @@ To add a release note, follow these steps:
    ```
 
 2. Save the file and commit your changes.
+
+## How to add a new incident details section
+
+1. Edit the file [`status-page.md`](./page/status-page.md)
+1. If there already is a section of the current year, such as e.g. `:::: details 2025 {open}`, add the incident on top of that section, leaving one blank line after the `:::: details 2025 {open}`
+1. If it is the first incident of the current year, create a new section for the new year, e.g. `:::: details 2026 {open}` and already the closing `::::`, so basically like this:
+
+   ```markdown
+   :::: details 2026 {open}
+
+   ::::
+   ```
+
+1. When you started a new year, please remove the `{open}` from the last year. This way, the old year is collapsed by default.
+1. Also, please remove the `{open}` from the last incident's details, this way, only the recent incident's details are expanded.
+1. Add the new incident either in the section of the new year or in the already existing section of the current year like this:
+
+   ```markdown
+   :::: details 2026 {open}
+
+   ::: details MONTH, DAY - short heading {open}
+
+   ### MONTH, DAY - longer heading
+
+   DETAILS go here
+   :::
+   ::::
+   ```
+
+1. Remember to close the details section of the incident with three `:`, and in case you created a new year section, remember to close that one with four `:`.

page/status-page.md

@@ -44,26 +44,14 @@ This page provides the latest status updates for all \*.geo.admin.ch web service
 
 ## Incident History
 
-<!-- Once we are in 2026, we should do the following:
-1. add a new details section for 2026:
-   ::: details 2026 {open}
-    [add any new incidents here]
-    ### [2026-mm-dd] Incident XYZ
-    #### [2026-mm-dd] Iformation related to incident XYZ
-    bla bla bla
-   :::
-
-2. remove the {open} from the 2025 section, so that it is collapsed by default
-
-This will group all incidents by year, and only the current year is expanded, all older incidents
-are collapsed. Improves overview a bit, in case we have too many incidents in one single year ;-)
+<!-- Please check the README.md for details on how to add new incidents or start a new year, thanks!
 -->
 
-::: details 2025 {open}
+:::: details 2025 {open}
 
-### [2025-11-12] Issues with search service
+::: details Nov 12 - Issues with search service {open}
 
-#### [2025-11-14] Information on recent problems when changing address data from RBD to the official directory of building addresses
+### Nov 14 - Information on recent problems when changing address data from RBD to the official directory of building addresses
 
 On Wednesday, November 12, 2025, the Search Service was switched from the register of buildings and dwellings (RBD) to the new default data source of the official directory of building addresses.
 
@@ -86,10 +74,10 @@ For your information, there are three ways to perform an address search:
 1. FeatureSearch in the layer ch.bfs.gebaeude_wohnungs_register; if desired, the feature ID can be transferred to the feature endpoint of the specialist layer ch.bfs.gebaeude_wohnungs_register.
 
 Specific documentation for this topic: [Search | \*.geo.admin.ch](https://docs.geo.admin.ch/access-data/search.html#request-details)
+:::
+::: details Nov 12 - Incident with Service Stac
 
-### [2025-11-12] Incident with Service Stac
-
-#### [2025-11-12 19:15] Disruption of Service Stac - Resolved
+### Nov 12, 19:15 - Disruption of Service Stac - Resolved
 
 The root cause that led to the outage of STAC API could be identified and resolved. The problem was a
 misconfigration of database logging that was done earlier today
@@ -98,13 +86,13 @@ space has been increased and the logging configuration change rolled back.
 
 STAC API is functioning normal again.
 
-#### [2025-11-12 19:15] Disruption of Service Stac
+### Nov 12, 19:15 - Disruption of Service Stac
 
 The STAC API on data.geo.admin.ch is currently unavailable. We're investigating the cause and will give an update later tonight.
+:::
+::: details July 2nd - Incident with Printing
 
-### [2025-07-02] Incident with Printing
-
-#### [2025-07-03 10:00] Incident Resolved
+### July 3, 10:00 - Incident Resolved
 
 An update to map.geo.admin.ch made on July 2, 2025 caused a temporarily disruption to the system's printing service.
 This resulted in a problem with the browser cache storing the information.
@@ -140,14 +128,14 @@ SAFARI
 - In Safari, go to "Settings" > "Advanced" and enable "Show Develop menu in menu bar."
 - Click on ‘Develop’ in the menu and then on "Empty Cache."
 
-#### [2025-07-02 16:00] Incident Detected
+### July 2, 16:00 - Incident Detected
 
 The printing functionality of map.geo.admin.ch is currently unavailable.
 We are analysing the problem and keep you updated on this page.
+:::
+::: details April 30 - Incident with WMS/WMTS
 
-### [2025-04-30] Incident with WMS/WMTS
-
-#### [2025-05-06] Root Cause Analysis
+### May 6 - Root Cause Analysis
 
 On the 30th of April and 1st of May, the WMS service and WMTS service provided by geo.admin.ch were restricted or unavailable, which also affected the print function in the map viewer.
 
@@ -160,15 +148,15 @@ We apologise for any inconvenience caused.
 
 Thank you for your understanding and patience.
 
-#### [2025-05-01, 16:00] Incident Resolved
+### May 1, 16:00 - Incident Resolved
 
 The disruption has been resolved.
 
 All services on \*geo.admin.ch are now available as usual.
 
 We thank you for your understanding and patience.
 
-#### [2025-05-01, 12:00] Update
+### May 1, 12:00 - Update
 
 No change since the update at 9:25 a.m.
 We are continuing to work intensively to resolve the problem.
@@ -177,7 +165,7 @@ The next update will be provided today at around 4 p.m. or as soon as the disrup
 
 We apologise for any inconvenience caused and thank you in advance for your patience.
 
-#### [2025-05-01, 09:25] Update
+### May 1, 09:25 Update
 
 The extent of the disruption has been reduced in the meantime.
 Certain WMS layers and the printing service are still affected.
@@ -187,7 +175,7 @@ The next update will be provided today at around 12 noon or as soon as the disru
 
 We apologise for any inconvenience caused and thank you in advance for your patience.
 
-#### [2025-04-30, 16:00] Update
+### April 30, 16:00 Update
 
 The disruption to the WMS, WMTS and print services is still ongoing.
 No other services provided by \*geo.admin.ch are affected.
@@ -197,7 +185,7 @@ The next update will be provided tomorrow, 1 May, at 9 a.m. or as soon as the di
 
 We apologise for any inconvenience caused and thank you in advance for your patience.
 
-#### [2025-04-30, 12:00] Update
+### April 30, 12:00 Update
 
 The disruption to WMS and WMTS services is still ongoing.
 We are continuing to work hard to resolve the issue.
@@ -206,7 +194,7 @@ The next update will be provided today at around 4 p.m. or as soon as the disrup
 
 We apologise for any inconvenience caused and thank you in advance for your patience.
 
-#### [2025-04-30, 10:00] Incident Detected
+### April 30, 10:00 Incident Detected
 
 We are currently experiencing some problems with our WMS and WMTS services, which we are analysing and will resolve as quickly as possible.
 The duration of the disruption is still unknown.
@@ -216,3 +204,4 @@ The next update will be provided today at around 12 noon or as soon as the disru
 
 We apologise for any inconvenience caused and thank you in advance for your patience.
 :::
+::::