GitToTheHub commented on PR #1447: URL: https://github.com/apache/cordova-docs/pull/1447#issuecomment-3660620150
> Wouldn't make much sense in practice with how the docs are built where it includes all the platforms, so a particular build isn't behind a particular platform. > > Currently the docs is "tied" to the CLI version because once upon a time, platforms was tied to a particular CLI version, there was a coupled dependency. But as the CLI matured, we found that we could go many platform releases without releasing a CLI version. So we started allowing wider range of CLI versions to be used across different platform versions. > > Today the CLI is completely decoupled from the platforms, and we just always assume that if you install a platform you want the latest version unless if there is a hint in the project somewhere that suggest otherwise. That's kind of the history of how we got where we are today with the docs. > > The discussion over [here](https://lists.apache.org/thread/yjnhx3s71plspc8jdz0f32sb85whtp69) I think suggests some really good paths including removing the snapshot logic altogether. The docs becomes more of a live document that just simply gets updated rather than having versions. Documented features will simply be annotated for platform support. > > I think we will still have archives, which is effectively a snapshot in a particular moment of time, which we will likely use before we do any kind of documentation cleanup (such as deleting information for old deprecated APIs that has been removed from the framework for some time). But these archives will not be something of focus, it will probably be a link to an archive index perhaps in the footer. All of this is not set in stone, just kind of brainstorming. Thank you for your reply and clairification. I think the discussion mail from @erisu is very good and simplifies everything -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
