There are situations where the Docs as Code approach is unarguably the best. The primary example is when engineers maintain an OpenAPI spec that becomes HTML documentation. In that case, it works because when engineers create a new property in the code, nobody else knows what the property is for, and the most sensible and efficient approach is for the engineer to write the description, followed by some kind of review by a technical writer. It follows naturally to provide editing tools that are familiar and comfortable for the engineers.
When docs as code is a big success, this is why
When docs as code is a big success, this is…
When docs as code is a big success, this is why
There are situations where the Docs as Code approach is unarguably the best. The primary example is when engineers maintain an OpenAPI spec that becomes HTML documentation. In that case, it works because when engineers create a new property in the code, nobody else knows what the property is for, and the most sensible and efficient approach is for the engineer to write the description, followed by some kind of review by a technical writer. It follows naturally to provide editing tools that are familiar and comfortable for the engineers.