Skip to content
NewSee how this site publishes in seconds
Halftone

ProductLaunch

Now available: the command bar, part 2

The thinking behind the release and what comes next. Built for the person with five minutes between meetings. Less waiting between done and live, for every team.

Hana Pike
Published 2 min read

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. This post covers what we changed, why, and what it means for you.

#Results

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.

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.

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

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

#Where we started

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.

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.

  • Cache what never changes
  • Run independent steps in parallel
  • Report problems in plain language
  • Keep the previous version one click away

#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.

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.

StepBeforeAfter
Install94s12s
Build41s7s
Deploy18s4s

#The constraint

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.

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.

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

#What's next

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.

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.
Nowavailable:usagedashboardsHALFTONE / JOURNAL

Product6 min

Now available: usage dashboards

Less waiting between done and live, for every team. Built for the person with five minutes between meetings. The thinking behind the release and what comes next.

Hana Pike
Introducingthe commandbarHALFTONE / JOURNAL

Product10 min

Introducing the command bar

The thinking behind the release and what comes next. What it does, who it is for, and how to try it today. Less waiting between done and live, for every team.

Eli Tanaka
Introducingrole-basedaccessHALFTONE / JOURNAL

Product5 min

Introducing role-based access

Less waiting between done and live, for every team. Built for the person with five minutes between meetings. The thinking behind the release and what comes next.

Gus Heller / Ivo Santos