shadcn.io is not affiliated with official shadcn/ui
System Administrator Runbook Profile Block for React Aria
A system administrator profile as a runbook drill: a menu of three runbooks, five numbered steps each with a copyable command in a scrolling mono block and a Done box, the steps and minutes to go worked out from the ticks, and the admin's figures in a start cell.
Installation
Overview
Rehearse an incident before it happens, with this system administrator profile for React with React Aria. A compact header names the console, and the frame under it opens on a start cell with the admin (initials, name, role and place) and three figures: runbooks owned, the last drill as a fixed date and on-call weeks. In the main cell a Select picks one of three runbooks: rotate a certificate, fail over the database or clear a full disk. Its five steps are numbered, each with the minutes it takes, the command in a mono block that scrolls sideways, a Copy Button that really copies it and a Checkbox to mark it done. A bar and one line, such as 1 of 5 steps, about 6 min to go, are worked out from the ticks, and each runbook keeps its own. Reset drill clears them all. It's built from Select, Checkbox, Copy Button, Progress, Avatar, Button and Guides, with a CSS entrance only. It is a drill: nothing is executed. The hosts, paths and commands are invented. For an ops console, an on-call page or a runbook library.
FAQ
How do I add my own runbook?
Add an entry to RUNBOOKS: an id, a name and its steps. A step has an id, a title, the command and the minutes it takes. Keep each runbook to the same number of steps if you want the panel to keep one height when you switch. The count, the minutes to go and the bar are worked out from which step ids are ticked.
Does Copy really copy?
Yes. It writes the command for that step to the clipboard, and the status line says which step was copied; if the browser refuses it says so instead. Nothing runs the command: it is text. Each button names its step, so it is clear when you move down the list.
Is anything executed or saved?
No. Ticking a step, switching runbooks and resetting only change what the page shows, and the ticks are lost on reload. The commands are written for invented hosts, and the line under the list says A drill: nothing is executed here. To wire it for real, post each tick to your runbook store and show who did the step and when.
What about a long command?
The command stays on one line and its box scrolls sideways. The box is a labelled region that you can reach with the keyboard and scroll with the arrow keys, and the command is always left to right, also in a right-to-left layout.
Is it accessible?
The steps are an ordered list, every Done box is named for its step, the runbook menu is named, and the progress line is a polite live region present from the start. A finished step is struck through and also stays readable. On React Aria the menu is a Select with the same three items, and the bar takes its name from its label.
Related
- Runbook Status DashboardIncidents and uptime
- On-Call Handoff ChangelogIncidents and uptime
- AI Engineer Latency Budget ProfileResearch and learning
- Technical Writer Documentation Types ProfileWriting and words
- Scrum Master Impediment Log ProfileTeam dashboards
- Accountant Filing Deadlines ProfileTeam dashboards