ScreenSteps automatically saves all changes made to an article as you work. However, capturing a specific version of your article for future reference involves additional actions beyond these automatic saves. Understanding how versions are managed helps ensure you can track and review changes over time.

• Automatic saves do not create distinct versions for review.
• Specific actions are required to formally save a version.

Key Terms

Publish: Making the article and its latest changes available to others.
Update: Applying and publishing new changes to an already published article.
Revision: A saved snapshot of the article at a particular point in time, which can be reviewed or compared later.

• Publishing and updating both create new versions of the article.
• Saving a revision allows you to capture a version without publishing changes.

Background

In ScreenSteps, while your edits are saved automatically, these are not considered formal versions. To create a version you can return to or compare, you must either publish, update, or manually save a revision. This system allows you to track the evolution of your content and review previous states when needed.

• Formal versions are created by publishing, updating, or saving a revision.
• Revision history enables you to review and compare different versions.

Why Versioning Matters

Versioning is important for maintaining a record of changes, collaborating with others, and ensuring you can revert to or review previous content if necessary. It provides accountability and flexibility in managing documentation.

• Versioning helps track the history of changes.
• It supports collaboration and quality control.
• Allows recovery of previous content if needed.