Replies: 2 comments 5 replies
-
Hello @mo-anon, I can see several issues with versioning a single file:
Given the "ambiguity" of this approach, I think this needs a very subjective/opinionated solution. |
Beta Was this translation helpful? Give feedback.
-
Every other month I think about it, and I miss it a lot, indeed. For technical docs that have subcomponents (like an embedded app or API or dependency), this would be a very nice feature. |
Beta Was this translation helpful? Give feedback.
-
Currently, MkDocs (with plugins like mike) supports versioning at the site-wide level, meaning that versioning affects the entire documentation set. However, in many cases, versioning is only needed for specific documents or sections, while the rest of the content remains unaffected.
For example, let's say there is a single document, like a technical specification or an API reference, that needs versioning. Other parts of the site (like introduction pages, general guides, etc.) may not require multiple versions. Versioning the entire site for a single file creates unnecessary complexity and overhead, both for maintaining the documentation and for users navigating through it.
Is there a way to achieve versioning for a single site?
Beta Was this translation helpful? Give feedback.
All reactions