deployerphp-docs-policy

To maintain a master index for DeployerPHP documentation, you must update the docs/documentation.md file whenever new files are added to the docs/ directory. This policy ensures the index stays synchronized and prevents navigation drift.

The required table of contents format for DeployerPHP docs mandates a TOC in all documentation files. This enforcement standardizes navigation and ensures consistent structure across the entire markdown documentation directory.

You enforce a consistent formatting workflow by applying documentation rules after editing markdown files in the docs/ directory. This process keeps formatting clean, restricts hidden CLI option docs, and guides prose-focused steps.

No, the DeployerPHP documentation policy restricts documenting specific CLI options. It instead guides authors to use prose-focused prompts and steps to prevent inconsistent or hidden command-line references in the markdown files.

Documentation updates cause master index drift when you add new markdown files without updating docs/documentation.md. Enforcing the documentation policy resolves this by requiring master index maintenance alongside every new file addition.

Yes, you can use standard markdown, but DeployerPHP docs updates must follow specific policy constraints. You must enforce a table of contents, maintain the master index, and adhere to a formatting workflow to ensure prose-focused consistency.