Every organisation approves content differently. Visor lets you draw that process as a workflow and attach it to the content it governs, so every page and entry shows where it stands.
Draw the steps
A workflow definition lists the states content moves through, such as Draft, Review, Approved, and Published, and the actions between them, such as Submit, Approve, and Reject. Drag states and actions onto the canvas and Visor writes the JSON definition. A sample workflow ships to start from.
Assign it where it applies
An assignment links a definition to a collection and activates its states for every entry. One definition can govern several collections, and each site can have its own. A filter rule sends a subset, such as one category, down a different path, so product disclosures can go to legal while news items go to an editor.
What editors see
Every page and entry shows its current state, and its status control offers only the transitions the definition allows. Drafts under review are versioned. A published entry is read-only, and editing it opens a new version that goes live when it is published again.
What gets recorded
Publishing queues the change and triggers a static build. Visor keeps three read-only records of that process:
- The publishing delta: content queued for, or included in, the next build
- Publishing executions: each build trigger, created automatically on publish
- Frontend build history: every completed or in-progress build
When the process changes, change the definition. No code is involved.
