Hi Aaron, Thanks for your work on this! Few points I noticed
1. Looks like something is wrong with the pip instructions. I see instructions for pre-reqs but not the actual pip install. 2. Most of the language bindings seem to be redirects to install page for that OS, regardless of CPU/GPU, but we still show that selector. 3. Can we remove the 'Validate MXNet..' wording when instructions are on a different page. The combination Linux, Scala, CPU for example. 4. I don't see much advantage of Pytorch or Caffe style installation webpages. Like you mentioned we have couple of more selectors. But it's pretty clear and not enough to overwhelm the user. If the problem is the maintenance of backend instructions, could we address that by having different files / folders for different scenarios and including them from one file? Not sure if that's feasible. +1 for hyperlinks to specific instructions. Regards, Rahul On Tue, May 22, 2018 at 11:53 AM, Naveen Swamy <[email protected]> wrote: > MXNet UI definitely needs more love. > > +1 - pytorch style > +0.5 - caffe2 > > > On Tue, May 22, 2018 at 11:48 AM, Markham, Aaron <[email protected]> > wrote: > > > Hi everyone, > > In addition to the options on the wiki (pros & cons), there's this > preview. > > It uses a dropdown next to the install options to make it clearer what > > versions you can install… then updates the pip commands… > > > > http://54.210.6.225/install/index.html# > > > > Thoughts? > > > > > > On 5/16/18, 9:31 AM, "Aaron Markham" <[email protected]> wrote: > > > > Hi, > > I've written some notes on the wiki about issues with the > installation > > page > > along with some suggestions. I'd appreciate your feedback here or on > > the > > wiki. > > > > https://cwiki.apache.org/confluence/display/MXNET/ > Installation+page+UX > > > > Cheers, > > Aaron > > > > > > > -- Rahul Huilgol
