Search blocks by description or jump to a page.
A two column incident retro pairing the story, root cause, and follow up changes with a static minute by minute timeline panel.
The source for every Portfolio block is included with Pro and Team. Start a plan to copy the code.
Already on a plan? Log in
Incident Postmortem is a two-column retro split. The left column carries the write up: the incident title with a date and severity chip, a what happened paragraph, a root cause paragraph, and a checked list of the three changes that followed. The right column is a static timeline panel that logs the incident minute by minute from first page to resolution, each row pairing a mono timestamp with a status dot and a short event line.
timeline and changes are typed arrays, so the log and the follow up list both grow from data rather than markup. A dotClasses helper maps each entry tone to a theme token, which marks the alert and resolved moments without color noise. The panel is a blueprint only, with no portal and no animation, so it renders cleanly inside the preview frame.
Reach for this block when a developer portfolio needs to show judgment under pressure rather than a happy path. It suits engineers who own on call work and want to prove they treat failure as a system to improve, not a thing to hide. The installer replaces the timeline entries, the root cause, and the three changes with their own incident.
A natural flow around it on a Portfolio Pro page:
Before
After
One strong use is the poison message that backed up the job queue. Other retro layouts:
Tip: keep the timeline honest and specific; rounded timestamps and vague events read as a story invented after the fact, not a log kept during one.