Something we've noticed is that traditional CMS systems have long relied on a draft/published model for content updates within a single database. For many use cases this is fine, but many of our users want to create multiple environments to stage updates for review, preview the changes, then push the changes to production. There wasn't an easy way to merge content changes between environments in review stages (such as Development, Staging, Production). This is especially true when you want to make large bulk edits to lots of content.
For this reason, we built Merge Requests. Much like software teams use Git to work in branches, make pull requests, and so on, this lets our users work in isolated content environments to add/update content, safely isolated from production. When ready, a merge request is submitted to review content changes. Reviewers can be added to review and approve updated content. Preview links are available to preview bulk edits in the user-facing application or website. After approvals, a merge is performed. If needed, restoring to a previous version can be done in a few clicks.
The feature is free to anyone with an account, but if you want to see how it works without signing up (we know you, HN!), check out the screenshot videos on the blog announcement (linked at the top). To go deeper, sign up for a free account (https://www.cosmicjs.com/). You can also install the Next Merge Starter (https://github.com/cosmicjs/next-merge) which includes merge request preview capabilities. Read the docs to get more information on how to implement the merge request preview for your applications currently available via the REST API and NPM module (https://docs.cosmicjs.com/rest-api/objects.html#get-objects-...).
This is work in progress and we would greatly appreciate any feedback that you may have in the comments below!