Replies: 2 comments 1 reply
-
|
We are planning to add a Content Releases feature in Craft 5.0 which sounds like it would solve this. It will enable authors to stage multiple edits to a Release, and publish them all at one time. You could then create a webhook that triggers a deployment whenever a Release is published. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Thanks for the update @brandonkelly. That sounds like the perfect solution for this challenge in CMS headless configurations. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
We are using Craft CMS more and more as a CMS for Next.js Frontend web projects. We also use Strapi. There is only one feature in Strapi that I really miss in Craft CMS and that is the "Publish (My Changes)" button. Please see the screenshot below:
Basically, the user makes all of their changes and then clicks this Publish (My Changes) button, which triggers the deployment to the frontend Next.js app. Currently, in Craft CMS we are using webhooks, which trigger a deployment whenever an entry is saved, which potentially leads to lots of deployments being triggered. It would be great to have a "Publish (My Changes)" button that would trigger a deployment when the user is ready to do so.
Beta Was this translation helpful? Give feedback.
All reactions