Article

Why you should check a staging version before you publish

You should check a staging version before you publish because it shows your change exactly as visitors will see it, on real devices and at a link you can share, without touching the live site. It catches the mistakes a preview on your own screen misses, and it gives clients a safe place to say yes.

By Lumiave · · 2 min read

In short

A staging version is a private, published copy of your site at its own link. Checking it before you publish lets you see the change as visitors will, on any device, and share it for approval, while the live site stays untouched. It catches broken layouts on phones, missing images, wrong links and wording a client would have changed.

What staging is

Most changes to a website go through three places:

  1. Your editor or preview: the site on your own computer while you work.
  2. Staging: a private copy, published to its own link.
  3. Production: the live site at its real address.

The preview is great for making changes. Staging is for checking them. The difference matters because a preview runs on your machine, in your browser, with your files, which is exactly where problems hide.

What staging catches that a preview doesn’t

  • Real phones. Open the staging link on an actual phone. Menus, tap targets and long words behave differently from a narrow browser window.
  • Missing files. An image that exists on your computer but wasn’t included in the publish shows up as broken on staging, not in your preview.
  • Links and forms. Click through the navigation and try the contact form on the published copy.
  • Fresh eyes. Someone who didn’t make the change notices the typo you’ve read past five times.
  • Approval. A client can look at the real thing and say yes, without anything being live.

When to use staging

Use it when the change:

  • is visible to customers, such as prices, opening hours or a new page,
  • needs someone else’s approval,
  • touches navigation, forms or anything people rely on to contact or pay you,
  • is large, or touches many pages at once.

When you can skip it

Staging is a habit, not a rule. Publishing straight to production is reasonable when you’re fixing a typo on a site only you look after, or reverting something you just broke. The point is that skipping it should be a decision, not the default.

A quick staging checklist

  • Open the staging link on your phone and on a computer.
  • Look at the page you changed, and the pages around it.
  • Click the main links and buttons.
  • Check images loaded.
  • Read the changed words out loud once.
  • If someone else needs to approve it, send them the link and wait for the yes.

How Devdwell does it

In Devdwell, staging and production are two checkboxes in the same publish panel. Tick Staging to get a private preview link (the live site doesn’t change), tick Production to go live, or tick both. The panel warns you when a site has been edited since its last publish and shows when each address was last published. The steps are in how to publish a website, and the difference is laid out in staging vs production.

Bring all your sites home.

Devdwell is in early access for Mac and Windows, with the web app for everywhere else. Tell us a little about how you build and we’ll be in touch.