Releases and release history

Every time a site is published, DocSpade creates a release. A release is a saved copy of the site exactly as it was published: its articles, navigation, home pages, look, shared content and images. The live site is always one release.

Releases are what make publishing safe. A new release is built in the background and replaces the live one only when it is ready, so readers never see a half-finished site.

What a release shows

Each release records:

Detail	What it tells you
Status	Where the release is, from queued to live
How it started	Manual when a person published, or Scheduled when it was published automatically
Timeline	When it was requested, when building started and finished, and when it went live
Articles	How many articles it contains
Failure reason	If it failed, a plain-language explanation of what went wrong
Warnings	Problems that did not stop publishing

Release statuses

Status	Meaning
Queued	Waiting to be built
Building	Being built now
Ready	Built successfully, but not live
Active	Live. This is the version your readers see.
Failed	Could not be built. The previous live version stays live.

A release normally moves from queued to building to ready, and becomes active on its own when it is ready. Only one release is active for a knowledge base at a time.

If a build finishes after a newer release has already gone live, it is kept as ready but does not replace the newer one.

Warnings

A warning points out a problem that did not stop the site from publishing, so you can fix it for next time. Each warning names the article or shared content it comes from. Examples are an image that could not be found and a link that leads nowhere.

When a release fails

A failed release does not affect your live site. DocSpade shows a plain-language reason, for example which article caused the problem, so you can fix it and publish again. If the same problem keeps happening and the reason does not help, contact support and mention the release.

Release history

Release history is the permanent record of who published, when, and how many articles each release contained. It covers every release that went live.

The history is separate from the releases themselves. DocSpade keeps only a limited number of earlier releases, and how many depends on your plan. When an old release is removed to stay within that number, only the saved copy of the site is removed. Your articles, images and settings are not touched, and the release stays in the history with who published it, when, and how many articles it had.

Releases that never went live, and releases that failed, are not removed this way.

Who can see it

Release history is available to publishers, and to owners and admins.

How releases relate to limits

Each release counts towards the number of times a knowledge base can be published in 24 hours, including releases that have since been removed. Failed releases do not count.