I appreciate the introduction of the content versioning feature in Strapi, and it is by all means a valuable addition. Unfortunately, it is only available in the Enterprise edition, costing $99 per month per seat, with a minimum of 3 seats. This pricing, totaling nearly $300 per month, is not feasible for small businesses or independent developers at all.

In our opinion, version control is an essential feature for any CMS. It helps mitigate errors by allowing users to revert unintended changes and ensures content integrity over time. These are fundamental needs for all users, not just enterprises. Including this feature in the Community edition would, in our opinion, better serve Strapi's diverse user base and align with the platform's open-source principles and success. I hope you can reevaluate this decision.

A safe method would be to use git functionality, embedded and hidden inside a UI suitable for normal human consumption.

Hello everyone 👋

We are currently designing the Content History feature! We have created a Maze prototype for you to try out.

Feel free to share any feedback!

Here is the link: https://t.maze.co/205754797

This is so important for content audits and reverting content if needed. We really need this to help manage different versions of content over time.

This is a very important feature, it would allow tracking of the changes on some content, who made the changes, and when they were made.

It could be interesting to have a solution for reverting the content to an older version, too.

Refer to this card for having multiple versions of the same content at the same time: https://feedback.strapi.io/customization/p/content-versioning-1