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

Product

Introducing offline mode

The thinking behind the release and what comes next.

Lu Brandt
Published 2 min read

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

#The constraint

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.

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.

“The safe path has to be the easy path.”
Bo Lindqvist

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

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.

#What we measured

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

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 is available today on every plan. We will keep shipping small improvements every week, and we read every piece of feedback that comes in.

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

#Where we started

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.

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.

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.

“A cache key must include everything that can change the output, and nothing that cannot.”
Cam Okafor
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