Community Forum
Is there a recommended way to handle version updates in Ohyay documentation?
last month by Victor Reeves
Hi everyone, I’m currently maintaining a set of docs on Ohyay for a project that gets fairly frequent updates. One challenge I’m running into is how to handle changes between versions without confusing readers who might still be using older releases.
Is there a recommended approach in Ohyay for managing versioned documentation? For example, should older versions of guides be duplicated and archived, or is it better to update the same page and add notes about what changed? I’m trying to keep the documentation clean while still making sure users can find instructions that match the version they’re using.
If anyone here has experience maintaining docs for evolving projects in Ohyay, I’d love to hear how you handle this. Thanks in advance!