Generated from
folio-assistant-core/processes/content/folio-review-publish.bpmnbygen-processes-viz.ts— do not edit here. All processes · folio-assistant-core processes
Review and publish a folio
Process_FolioReviewPublish · advisory · 3 step(s)
Review a rendered folio and publish it, or send it back with changes. Shared by every authoring process: authoring-a-document (this layer) and authoring-a-paper (folio-assistant-sci) call it after they validate and render, so review, publish and committee feedback are drawn once. What differs by folio kind stays with the caller: its writing loop, its own check (the content profile for a document, the Lean build for a paper), and its renderer. It ends one of three ways. Published: the caller closes its bean. Changes asked and Feedback in: changes asked: the caller goes back to its writing loop.
How it connects
- Called by: Authoring a document, Authoring a paper
- Calls: Contributor feedback on a working draft
- Presented on: no docs page section shows this diagram
- Running instances: none recorded
Lanes — who acts
| lane | role | what it does here |
|---|---|---|
| Build pipeline | build-pipeline | Publishes once the reviewer approves. Release authorisation is not relaxable. |
| Reviewer | reviewer | Owns the one gate that decides publish or iterate, and is deliberately unspecialised: whichever reviewer the folio binds. |
| Authoring Committee | authoring-committee | The people writing the document with the editor. While it is a working draft they give feedback through the Contributor Feedback sheet, one change set per row, and each row runs Process_ContributorFeedback. |
Steps
Every one of the 3 step(s) is documented.
| step | lane | skill / sub-process | what it does |
|---|---|---|---|
Review and record feedbackTask_Review | Reviewer | content-reviewstaging-review | The reviewer this folio binds. authoring-document relaxes the base SME step precisely because no single lane fits every document. Review the rendered folio, not a description of it, and record the feedback. The outcome is iterate — back to authoring — or approved for the publication path. |
PublishTask_Publish | Build pipeline | content-publish | See draft-to-publication.bpmn for the review and release path this expands into. Release authorisation is not relaxable. |
Contributor feedbackCall_ContributorFeedback | Authoring Committee | calls Contributor feedback on a working draftreview-sheet-script | Process_ContributorFeedback: while the document is a working draft, the Authoring Committee gives feedback through the Contributor Feedback sheet, and each change set is edited and merged in its own pull request. When its changes are merged, the document is validated and rendered again. |
Decisions
Every one of the 1 decision(s) is documented.
| decision | what decides it | branches |
|---|---|---|
Ready to publish?Gateway_ReviewOutcome | The reviewer’s call after the review. approved goes to publish. iterate ends this process with changes asked, and the caller returns to its own writing loop with the feedback. Authoring Committee feedback sends a working draft to the committee through the Contributor Feedback sheet; what comes back is also changes asked. | iterate → Changes asked approved → Publish Authoring Committee feedback → Contributor feedback |