Feature Request Summary: 

I would like to be able to review and save changes to published articles, without updating the article that is visible to the audience.  I want to be able to choose when to publish those changes.

Description/Use Cases: 

When I add new features to our main articles and/or navigation changes – it necessitates numerous small changes with screenshots and so on, in addition to new sections, updating content pages and so on. These changes require reviewing, prior to being published and invariably a delay until the feature/product changes have gone into production.  There is no easy way to do this.

Currently, I must copy all the content into a new article (or word document)- make the changes and review it - then either:

• manually track any updates and then retrofit the changes into the original article – increasing the likelihood of mistakes being made,
• delete the content in the original article and copy and paste from the new version, meaning I then must reimport and insert all the images; or
• entirely replace the original article, find and mend any other links and upload/ insert all the images that were copied and retained from the original article.

I then have the joy of repeating the exercise for our other brands.

Business impact of limitation or missing feature:

The time to work around the lack of functionality is significant, I estimate that it doubles my time and introduces new opportunities for errors. 

Other necessary information or resources:

I understand that there is additional functionality in the Enterprise plan which would double our costs and give us a huge amount of features that we do not need. We are currently a small organisation and the additional expense of paying for the Enterprise solution doesn’t represent good value for money. Our main priority is to build customer usage with the help of good documentation – so our primary interest is the KB tools rather than the heavy weight ticketing tools for large number of support agents. It strikes me in 2022 that the ability to save and review, but not immediately publish updates, is a fundamental requirement of a decent knowledge base.