Skip to content
NewSee how this site publishes in seconds
Halftone

ProductLaunch

A closer look at the API

Less waiting between done and live, for every team. What it does, who it is for, and how to try it today. Built for the person with five minutes between meetings.

Ada Rivers
Published Updated 3 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

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.

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.

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

#What we measured

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.

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 changed

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.

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.

  • Skip what has not changed
  • Run independent steps in parallel
  • Cache what never changes

#Rolling it out

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.

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

#Results

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.

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.

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

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.

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

  • Skip what has not changed
  • Run independent steps in parallel
  • Keep the previous version one click away
  • Cache what never changes
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