From b1088248cafa6eb70be6608293ae973823e3aea2 Mon Sep 17 00:00:00 2001 From: Maximilian Kaske Date: Sun, 11 Oct 2026 21:05:27 +0200 Subject: [PATCH] content(web): mention the quieter sidebar in the incident timeline post --- .../pages/blog/four-iterations-of-an-incident-timeline.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/apps/web/src/content/pages/blog/four-iterations-of-an-incident-timeline.mdx b/apps/web/src/content/pages/blog/four-iterations-of-an-incident-timeline.mdx index e2b16874f..7635902e9 100644 --- a/apps/web/src/content/pages/blog/four-iterations-of-an-incident-timeline.mdx +++ b/apps/web/src/content/pages/blog/four-iterations-of-an-incident-timeline.mdx @@ -59,6 +59,8 @@ Then one observation at a time: We were emphasizing every event the same way. Notes and status changes became cards written as sentences: Thibault marked Resolved. System events collapsed into one-liners: linked status report #3473. Slack got a badge on the avatar. +The sidebar got the same treatment. The linked status report sat in its own card with a primary "Post public update" button, which pulled the eye away from the timeline. It is now one row under Communication, the actions behind a menu. The timeline is the page; the aside is reference. + Iteration 4: notes and status changes as cards, system events as one-liners The timeline is less tall and less loud because it has levels. The important stuff reads like a story. The plumbing stays out of the way. -- 2.51.2