Skip to content
NewSee how fast an edit goes live on this site
Halftone

ProductLaunch

Now available: scheduled publishing

Less waiting between done and live, for every team.

Fen Alvarez
Published 2 min read

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

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.

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.

  • Keep the previous version one click away
  • Skip what has not changed
  • Cache what never changes

#Trade-offs

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.

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
  • Run independent steps in parallel
  • Skip what has not changed

#The constraint

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.

“The safe path has to be the easy path.”
Fen Alvarez

#What's next

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

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.

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.

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

#What we would do differently

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.

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.

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

#Rolling it out

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.

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

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
  • Skip what has not changed
Nowavailable:usagedashboardsHALFTONE / JOURNAL

Product6 min

Now available: usage dashboards

Built for the person with five minutes between meetings.

Lu Brandt
Introducingthe commandbarHALFTONE / JOURNAL

Product10 min

Introducing the command bar

The thinking behind the release and what comes next.

Ivo Santos
Introducingrole-basedaccessHALFTONE / JOURNAL

Product5 min

Introducing role-based access

Less waiting between done and live, for every team.

Eli Tanaka