
SimplifyUX Console
One place to create, watch, change and roll back every website I run, and to swap a site's whole design without touching its words. Part of the SimplifyUX suite, the software I'm building for my own company.
SimplifyUX Console is where the websites in the SimplifyUX suite are made, watched and changed. It is the third product in the suite I’m building for my own company, SimplifyUX. The suite’s other products are the design tool, the notes and the task board that plans the work. The AI agents design and build; this is where their work becomes a running website. It also holds the suite’s set of interchangeable site designs. The screens here show invented sites on reserved example addresses, so none of them is real.
What was broken
Every website I ran lived somewhere different, and every job on it meant a terminal, a password and a checklist I kept in my head. Creating a site was a page of steps. Rolling one back meant remembering which parts of it a rollback would touch.
Then AI agents started building the sites, and they built them faster than I could look after them by hand. The risk moved. It was no longer that work was slow; it was that a fast change could break something nobody was watching. I needed one screen where any job in a site’s life could be done safely, by me or by an agent. Every change would be recorded, and every risky one explained before it happened.
How I worked it out
I listed the jobs first. A website’s life has eight of them, and the console does all eight from the browser: watch, create, edit, copy, delete, read logs, redeploy and roll back. For each job I wrote down what it may touch, and the screen says so before you act.
| Job | What it can touch |
|---|---|
| Watch | Nothing. It only reads, and finds sites that drift from the record. |
| Create | A new site, its code history, its pipeline and its address, in one request. |
| Edit and copy | The console’s record, or a new site made from an existing one. |
| Delete | The running site. Never its code history. |
| Read logs | Nothing else. It runs as a separate identity that can only read. |
| Redeploy | The same release, started again. |
| Roll back | Which release is live. It never touches the data and never deletes a release. |
Two rules carry most of the safety. Every change that needs administrator rights asks me for the password, uses it once and wipes it, so no standing permission is left lying around. And a change that can be undone asks for less ceremony than one that cannot. Changing a design needs one clear button, because changing back undoes it. Deleting a site still asks me to type its name.
The design work had a second job. The suite’s sites all wear one of ten designs: eight custom and two standardised. The console previews any of them at a true screen width and swaps a live site from one to another. That swap follows four steps, and stops at the first that fails:
- 01CheckThe site's own pipeline must have passed, or the change is refused.
- 02SwapOnly the files the design owns are replaced. The words are not touched.
- 03RecordThe swap lands as one recorded change, so it can be undone.
- 04Read backThe console reads the live site and confirms the words are byte for byte the same.
What I designed
The console is quiet on purpose. One typeface throughout, machine values in a monospace face, ruled rows instead of cards, square corners and no shadows. Status is the only colour that shouts, and it always comes with a word as well, never colour alone.
The dashboard answers one question at a glance: is anything wrong? Hosts and the certificate sit in one strip, four small charts sit under it, and every site follows in a ruled table. A site’s own page leads with one huge word, Up, Degraded, Down or Unknown, followed by the reason. Each tab opens with a line saying what it can touch. The Overview says it only reads; the Releases tab says it can change what is live.
The rollback warning is the piece I’m proudest of. Rolling back code is easy; knowing whether the data rolls back with it is what people get wrong. The console says it in plain words before the button: the data does not roll back, and here is what that means for this site.
The design pages are where the suite’s visual side lives. The preview shows a design at 390, 820, 1280 or 1920 pixels wide, or any exact width from 320 to 3840, in light or dark. It renders from its own sealed-off address, so a design can never reach into the console. The Create form shows all ten designs as the same homepage, so the only thing that changes between them is the design.
Making the console wear the suite’s shared design engine turned up a fault no screen would have shown. The shared pack’s status colours looked fine and failed the contrast that text needs. I recalibrated all four, and a test now holds each one above the pass mark of 4.5 to 1 against both light backgrounds:
| Status | Before | After |
|---|---|---|
| Up | 4.31 to 1 | 5.17 to 1 |
| Degraded | 3.75 to 1 | 5.17 to 1 |
| Down | 4.42 to 1 | 5.16 to 1 |
| Unknown | 3.82 to 1 | 5.15 to 1 |
What changed
The first working versions, one to watch and one to create, shipped on 6 June 2026, four weeks after the first commit. Since 14 June the console has deployed itself: a push builds it, and it restarts only if the build passes. On 1 October 2026 a test site changed design and back again, both times through its own pipeline. Its words came through byte for byte the same each way.
The numbers are measured, not estimated. 866 of 866 unit tests pass in 57 files, measured on 18 October 2026. Every page is scanned for accessibility in both themes, at desktop and phone widths, in two browser engines, with zero violations allowed. Adopting the shared design engine moved 315 colour uses across 20 files onto one set of tokens. The console and every site it creates now share a single design language.
Commits by month
What I learned
The redesign started with my own mistake. On 1 October I set a site’s design seven times in a form that only changed the console’s record, never the site. Nothing on the screen told me so. I called the page what it was and started again. The new design was approved the next day, and its first rule came straight from that afternoon: every tab says what it can touch.
Safety is a design problem before it is a technical one. The password wiped after one use and the separate identity for logs matter. But the line that says ‘the data does not roll back’ prevents more mistakes than either of them, because it speaks at the moment the decision is made.
And a set of designs is only useful if they are genuinely different. On 28 September I opened a project for new designs that look nothing like the existing ones or each other. A choice between two things that look alike is not a choice.









