Before supporting multiple product versions creates a doc sprawl.
Design a versioning strategy for [product] docs. Specify: how to version, what to do with old versions, how to show what changed, and when to deprecate. Consider maintenance cost.
Anything in square brackets is meant to be replaced. The builder turns those into fields you can type into.
Tired of re-pasting the same context into every new chat? That is what the Unimatrix MCP server is for.