ideas
ideas copied to clipboard
Content approval flow with Revisions
In my experience, it is fairly common for clients to want an "approval" flow for content:
- content created/edited
- Approver is notified
- Approver approves content and publishes.
I have done this in v2 w/ listeners and controllers to check state/change state etc. Can definitely do this the same way in v3, but revisions seem like the perfect way to handle this. A few missing things:
- notifications of changes/updates
- revision events
Seems like "revision events" exist: https://github.com/statamic/cms/pull/4587