@sandeep-krishnamurthy thanks for the feedback. I add clarifications to the description above in a Stats section and a Details on Each Change section.
> Change is confusing for readers trying to find docs in other version: With > this change, I am unable to see any other doc page for other than master > version. Everything gets redirected to master. It is confusing for users, say > I click v1.0.0 and Tutorials => gets redirected to landing page of v1.0.0 Basically users are only allowed to browse versions on the API pages. For tutorials I think each one should be tested back through versions and then labelled to what their minimum version is. But since we don't test the old versions now, I think it is better that we don't display them. For your UX flow here, which I think would be quite rare, but we could send them to a page where they get the option to continue to the old broken info, or go to the new stuff. > Versions are now applicable only for APIs. So why don't we just show versions > under API? Currently, it is not clear versioning is only for API docs. Yes! But apparently it wasn't that easy last time when Krishnan tried. I'd like to tackle that next. But at least with this, people aren't going to bad/incorrect/non-working info or tutorials! > I go to a API page (say scala) then change version, it goes to landing page. > Should we go to that current page in older version? It's always done that. Really annoying. That should be fixed too though (or moot if we get the versions just working right within the API section. Next PR? [ Full content available at: https://github.com/apache/incubator-mxnet/pull/12540 ] This message was relayed via gitbox.apache.org for [email protected]
