For most projects we deploy a static web documentation site. The content of this site is generated under change control by a select few publishers / editors.

For most projects we deploy a static web documentation site. The content of this site is generated under change control by a select few publishers / editors. Our reasoning is that documentation should be a "read mostly" resource. We prefer to vet and manage the updates with some manual processes. Might be sub-optimal, but the quality is high and erroneous / misleading changes can be easily rolled-back and then the re-edited versions re-released. However, most errors are caught in pre-release review stage.