Content Requirements Documentation

Schema changes are written down before they are made. A change is a set of markdown requirements pages, one per artefact, grouped by a changeset. The user approves the changeset; only then is it applied, and only after reading the result back is it marked applied.

Write the requirements doc, stop for approval, apply, verify. Never create or change schema on a site from a requirements doc whose status is still proposed.

The rules for what to put in a requirements doc (names, folders, tabs, sorts) live in the sibling skill umbraco-content-model-conventions. It must be installed alongside this one. If that link cannot be read, stop and say so; do not work from memory.

Steps

The six steps every schema change follows, with what is shared between skills written once, are in change-workflow.md. Each step's detail: