Practical guide · MachinA

Save versus publish: a safer workflow for website changes

Why checking a draft before making it public reduces mistakes.

Last reviewed: 8 October 2026Based on the current public product

Before you begin

Editing a website is different from publishing it. In MachinA, the management system distinguishes saving changes from publishing them.

That separation lets a website owner prepare text and review it before visitors see the final version.

Prepare a small batch of edits

Fix the business description, services or hours with the actual source information at hand.

Save without assuming it is live

Review the draft view or management state. Do not tell customers a correction is public until you have checked.

Publish the intended changes

Use the designated publish action only after reviewing the affected sections.

Verify as a visitor

Open the public link in a separate browser view and check the content, navigation and contact paths.

A practical example

You update the price description on a business website. Save the change, check the intended wording in the admin, publish it and verify the public URL using a separate browser session. That last check matters because an editor confirmation and a live visitor view are different things.

What to check before you finish

  • Use accurate source material for opening hours and addresses.
  • Keep a record of important business changes outside the website.
  • If a change fails to appear, diagnose the publish state before repeating actions.
Scope of this guide

This article is practical product documentation, not legal, medical, financial or employment advice. Always verify consequential details with the responsible organization or person.

Use the actual tool

For the current feature set, visit the MachinA product reference, then open its official website. Do not rely on an old screenshot or instructions if the live interface has changed.

Explore the other practical guides or return to the four featured products.