group incidents by year

[hansmannj]

Suggestion:
How about grouping incidents by year and only expanding the current year by default, to improve readability?
Esp. useful in years with many incidents

Test link

[hansmannj]

Might even be worthwile to use nested ::: details, so that detail information of any single incident is collapsable, too. And only the most recent / currently ongoing one is expanded by default

[asteiner-swisstopo]

I like the idea of grouping by year.

How about collapsing all years by default?

This way, the reader sees immediately only the most relevant section: The current status. Also, the instructions on how to archive incidents would get simpler.

[hansmannj]

Good idea @asteiner-swisstopo .
Had to remove the ###since they would have been listed automatically in the TOC on the right side.
Introduced a 3rd level of containers to achieve this.
Resulting page looks nice IMHO.

[hansmannj]

P.S.: for the test link to reflect the most recent changes, it helps to add a dummy query param to bypass cache: https://sys-docs.dev.bgdi.ch/preview/feat_group_incidents_by_year/page/status-page.html?_=dummyvalue

[asteiner-swisstopo]

Cool thanks, looks as expected.

Seeing it now, maybe it would be even cleaner to extract it to a separate subpage without collapsible blocks. I don't really see the advantage of having to click every section in order to be able to read it.

So we would have two pages:

• Status page: As before, but only the current status
• Incident history: Archive with past incidents

But no strong opinion, I let you decide.

What you should fix for sure: The numbering in the README, currently each steps starts with "1.".

[hansmannj]

Having subpages might be an option.

How about the new commit: The incidents, grouped by year, are still on the same page.
But by default, if you expand a year, all incident details of that year are expandes, too.
So the user only needs to expand the year of interest to see all incidents with one click.