Skip to content
HalftoneJournal
← All articles

ProductLaunch

Now available: usage dashboards

Built for the person with five minutes between meetings.

Lu Brandt

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

What we would do differently

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.

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.

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.

“Measure the time from done to live, and treat every minute of it as a bug.”
Dee Marsh

What changed

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.

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.

The constraint

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

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.

Results

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.

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.

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.

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.

ts
const key = `${route}:${hash(content)}:${hash(template)}`;
const hit = await cache.match(key);
if (hit) return hit;

Where we started

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.

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

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.

  • Run independent steps in parallel
  • Skip what has not changed
  • Report problems in plain language