Between written and live
Workflows give a project an ordered set of stages, and approvals decide who moves work between them. One stage is the publish gate, and a setting decides whether that gate binds at all.
Your stack. Your rules. Everyone moves faster.
What workflows give you
-
Two separate axes
Status is the system lifecycle on every project. Stage is your own process, and you name the stages.
-
A gate you can turn off
One stage of the four is the publish gate. A team with no approval step can publish from anywhere.
-
Board and list
Columns are your stages plus a Published column. The same entries, read two different ways.
-
Three ways to move a card
Drag it, use the Move menu, or use the keyboard. The keyboard path announces every move as you go.
-
Filters that count
All, Assigned to me and Overdue, each with a count. A running summary reads N of M entries.
-
Only if the project has no stage set as the publish gate. When a stage is the gate, publishing stays blocked until that stage is cleared.
-
The stages are a project setting. You give the project an ordered set of stages and decide which roles may move work between them.
-
It returns to the draft stage. Nothing is lost and nothing was published, because the published page never changed.
-
Yes. Scheduled is a status on the entry, so a dated page sits in your stages like any other until the gate is cleared.