Workflow

A change doesn't begin with design, and it doesn't end when the code is merged. Someone requests it, someone designs it, someone approves it, someone implements it, and someone checks that the finished result is actually correct. Most teams spread those steps across different tools.

Workflow keeps them attached to the page itself. A request lives on the section it refers to, the designer makes the change in place, reviewers approve it, developers implement it, and the status moves forward with the work instead of being copied into another system.

The final step is the one that's easiest to miss. A task isn't finished just because the code shipped. The person who requested the change still needs to confirm that the live page matches what was approved. Closing that loop on the page itself means everyone sees the same status, from the first request to the final sign-off.