Templates / Human in the loop / content-review
Editorial Content Review
Runs automated checks on a draft, then puts it in front of an editor with a Camunda form that records the verdict — publish, revise or reject — and a comment. The verdict routes the draft to the CMS, back to its author with the comment, or to the archive.
Scenarios · 2
- The editor publishes the draft automated-checks → editorial-review → publish → published
- The editor asks for a revision editorial-review → return-to-author → returned
Job types · 4
-
author-notifyReturn to author -
cms-archiveArchive draft -
cms-publishPublish to CMS -
content-lintRun automated checks
Files · 3
- content-review.bpmn Process model
- content-review.bpmn.tests.json Test scenarios (runScenario format)
- editorial-review.form Camunda form
Every scenario passes on @bpmnkit/engine's runScenario in the
package's tests. casen template use content-review [dir] writes the files above
into your project — see the templates guide for running
the scenarios and deploying.