You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The governance documentation can be (and is) different between the different versions of docs (i.e. CMS3 vs CMS4 docs). This leads to conflicting information depending on where you look. This will continue to be a problem even if we removed documentation for EOL versions, because we're unlikely to update governance docs on any branch other than the most recent stable.
Options
Create a "governance docs" repository to hold the source for governance docs (contributing, maintenance guidelines, processes, etc)
We can then use the new repository for governance docs and the dev docs for everything else - this would be similar to how the userhelp docs pull from multiple repos.
Keep "governance docs" where they are, but only show the current stable version on docs.silverstripe.org
Host the governance docs entirely separately from docs.silverstripe.org
Notes
With both options 1 and 2 above, we'll need some UX advice for how to indicate that this documentation isn't tied to CMS versions the same way the developer docs are (or if such an indication is even necessary).
It may be as simple as not displaying the version note at the top of the page, possibly in combination with hiding the version picker.
The text was updated successfully, but these errors were encountered:
The governance documentation can be (and is) different between the different versions of docs (i.e. CMS3 vs CMS4 docs). This leads to conflicting information depending on where you look. This will continue to be a problem even if we removed documentation for EOL versions, because we're unlikely to update governance docs on any branch other than the most recent stable.
Options
Notes
The text was updated successfully, but these errors were encountered: