Skip to content
HalftoneJournal
← All articles

Product

Introducing the command bar

The thinking behind the release and what comes next.

Ivo Santos

Admins can scope access by project, so guest contributors see only what they are working on. Nothing about the experience changes for everyone else. This post covers what we changed, why, and what it means for you.

The details

We designed for the person who has five minutes between meetings. The common path takes two clicks, and everything else stays out of the way until you ask for it.

Version history keeps every change, who made it, and why. Restoring an older version is a single action, and it never deletes the newer ones.

Every change now shows its status in plain language. You see when it is saving, when it is publishing, and the moment it is live, with a link to check for yourself.

StepBeforeAfter
Install94s12s
Build41s7s
Deploy18s4s

Rolling it out

This is available today on every plan. We will keep shipping small improvements every week, and we read every piece of feedback that comes in.

Teams told us the same thing in different words: the work was done, but getting it live took longer than doing it. This release is about closing that gap.

Preview links work for anyone you send them to, even people without an account. They expire on their own, so nobody has to remember to clean them up.

  • Run independent steps in parallel
  • Keep the previous version one click away
  • Skip what has not changed
  • Report problems in plain language

Results

Admins can scope access by project, so guest contributors see only what they are working on. Nothing about the experience changes for everyone else.

We designed for the person who has five minutes between meetings. The common path takes two clicks, and everything else stays out of the way until you ask for it.

Version history keeps every change, who made it, and why. Restoring an older version is a single action, and it never deletes the newer ones.

“Good defaults are invisible until they are missing.”
Fen Alvarez

Trade-offs

Every change now shows its status in plain language. You see when it is saving, when it is publishing, and the moment it is live, with a link to check for yourself.

This is available today on every plan. We will keep shipping small improvements every week, and we read every piece of feedback that comes in.

What changed

Teams told us the same thing in different words: the work was done, but getting it live took longer than doing it. This release is about closing that gap.

Preview links work for anyone you send them to, even people without an account. They expire on their own, so nobody has to remember to clean them up.

Diagram of the request path before and after the change
Figure: the request path, before and after.

What we would do differently

Admins can scope access by project, so guest contributors see only what they are working on. Nothing about the experience changes for everyone else.

We designed for the person who has five minutes between meetings. The common path takes two clicks, and everything else stays out of the way until you ask for it.

  • Cache what never changes
  • Report problems in plain language
  • Skip what has not changed
  • Keep the previous version one click away