Skip to content
NewSee how this site publishes in seconds
Halftone

ProductLaunch

Introducing version history, part 2

The thinking behind the release and what comes next. What it does, who it is for, and how to try it today. Built for the person with five minutes between meetings.

Gus Heller
Published 3 min read

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

#What we measured

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.

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

“The safe path has to be the easy path.”
Dee Marsh

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

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.

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

#The details

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.

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
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}/` };
}

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

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}/` };
}

#What we would do differently

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.

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.

“Good defaults are invisible until they are missing.”
Ada Rivers

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

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.

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