Skip to content
NewSee how this site publishes in seconds
Halftone

ProductLaunch

Version history, rebuilt from scratch

Built for the person with five minutes between meetings. What it does, who it is for, and how to try it today.

Bo Lindqvist / Lu Brandt
Published 2 min read

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

#Rolling it out

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.

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

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.

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

#The constraint

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.

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.

“Good defaults are invisible until they are missing.”
Fen Alvarez

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

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

text
# p95 before / after
build      41.2s -> 6.8s
deploy     18.0s -> 4.4s
end-to-end 11m   -> 1m 52s

#What's next

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.

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.

ts
export async function publish(post: Post) {
  const problems = validate(post);
  if (problems.length) return { ok: false, problems };
  await commit(post);
  return { ok: true, url: `/blog/${post.slug}/` };
}
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