It looks like my previous email did not go through. Re-sending: Hi Aaron,
The website looks cool. Thanks for pushing this to production. A few questions: - I was looking for the API doc for mx.sym.dot, but I find that most operators under mx.sym.* are missing. Is this expected? - I was also checking the search functionality, searching the keyword "ndarray" only returns one result "mxnet.ndarray.NDArray", which doesn't seem right. There animation keeps going (Searching. -> Searching.. -> Searching ...) and gives me an impression that the search is never completely done(?). Best, Haibin On Fri, Sep 20, 2019 at 4:50 PM Chaitanya Bapat <chai.ba...@gmail.com> wrote: > Thanks Aaron and the team for launching new website! > > 1. There's no search button anywhere on the landing page. > 2. I wasn't able to find FAQ (and without search button I dont have option > but to go manually on each menu). Only when I go to Docs&Tutorials -> FAQ > -> Extend and Cotribute (that I got what I wanted). > > Suggestions > Might want to make this searchable and pop FAQ on the main page (or > somewhere prominent) > > Thanks, > Chai > > > On Fri, 20 Sep 2019 at 14:58, Przemysław Trędak <ptre...@apache.org> > wrote: > > > There seems to be a problem with (at least Python, did not check others) > > APIs. For example this page: > > > > > https://mxnet.incubator.apache.org/api/python/docs/api/symbol/_autogen/mxnet.symbol.Symbol.argmax.html > > > > says that it is a convenience method for argmax (with a link), but > > clicking that link just points to the same website (and so user has no > way > > of getting to the docs of the actual operator). > > > > When I tried to manually remove Symbol from the URL to get to > > mxnet.symbol.argmax.html, I got a "Not found" webpage which I guess also > > should not happen (ignoring the fact that this should exist, going to > > random URL under the website should redirect to the main page I think). > > > > Przemek > > > > On 2019/09/20 16:41:28, Lin Yuan <apefor...@gmail.com> wrote: > > > Looks very neat. Thank you Aaron and many others for launching this! > > > > > > On Fri, Sep 20, 2019 at 7:31 AM Carin Meier <carinme...@gmail.com> > > wrote: > > > > > > > Nice!!! Congrats everyone! > > > > > > > > On Fri, Sep 20, 2019 at 10:28 AM Aaron Markham < > > aaron.s.mark...@gmail.com> > > > > wrote: > > > > > > > > > Alrighty! The new site is launched. You might need to clear your > > cache. > > > > > > > > > > Cheers, > > > > > Aaron > > > > > > > > > > On Thu, Sep 19, 2019 at 3:33 PM Aaron Markham < > > aaron.s.mark...@gmail.com > > > > > > > > > > wrote: > > > > > > > > > > > > Thanks everyone. The PRs passed CI, but please continue holding > > off on > > > > > > docs and CI edits. Unless there are any objections, I'd like to > > launch > > > > > > the new website today. > > > > > > > > > > > > On Wed, Sep 18, 2019 at 7:46 AM Aaron Markham < > > > > aaron.s.mark...@gmail.com> > > > > > wrote: > > > > > > > > > > > > > > Hi everyone, > > > > > > > The last two PRs [1][2] for the new website and docs have > passed > > CI > > > > > > > (finally). Please do not make changes to /docs or /ci until we > > get > > > > > > > these approved and merged. Every time there's a merge conflict > > it has > > > > > > > set us back a day or two while shepherding the PRs through CI > > again. > > > > > > > Unless there are catastrophic issues discovered in a review, I > > > > > > > recommend that we hold any patches or updates to the PRs to > > follow-up > > > > > > > PRs. > > > > > > > > > > > > > > There are four steps to launch: > > > > > > > 1. Once the PRs are approved, the plan is to merge 15885 to > > delete > > > > the > > > > > > > old content first. > > > > > > > 2. Then immediately merge 15883 to add in the new CI flows and > > > > updates > > > > > > > to the content Thomas and I have already had merged in 15884 > [3]. > > > > > > > 3. I will change the website validation Jenkins pipeline to > > point to > > > > > > > the new pipeline. > > > > > > > 4. I will change the website publishing Jenkins pipeline to > > point to > > > > > > > its new pipeline as well. Once triggered, the old site will be > > > > > > > replaced with the new one. > > > > > > > > > > > > > > Post launch we'll need to update the DNS for beta.mxnet.io to > > point > > > > to > > > > > > > production, and there will likely be some redirect/.htaccess > > updates > > > > > > > needed next week to assist with any deep linking and 404 issues > > that > > > > > > > pop up. > > > > > > > > > > > > > > Cheers, > > > > > > > Aaron > > > > > > > > > > > > > > [1] https://github.com/apache/incubator-mxnet/pull/15885 > > > > > > > [2] https://github.com/apache/incubator-mxnet/pull/15883 > > > > > > > [3] https://github.com/apache/incubator-mxnet/pull/15884 > > > > > > > > > > > > > > > > > -- > *Chaitanya Prakash Bapat* > *+1 (973) 953-6299* > > [image: https://www.linkedin.com//in/chaibapat25] > <https://github.com/ChaiBapchya>[image: https://www.facebook.com/chaibapat > ] > <https://www.facebook.com/chaibapchya>[image: > https://twitter.com/ChaiBapchya] <https://twitter.com/ChaiBapchya>[image: > https://www.linkedin.com//in/chaibapat25] > <https://www.linkedin.com//in/chaibapchya/> >
