You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mxnet.apache.org by Aaron Markham <aa...@gmail.com> on 2018/06/12 00:11:22 UTC
landing pages for the website
Hi dev@,
We've had a lot of great expansions to MXNet's functionality and family of
tools in recent months. I would like to gauge the temp on what would be
good to highlight, and what would be good as navigation items with actual
landing pages.
For example, when ONNX was added, being in a contrib package, it was going
to totally buried, so it has a navigation item under Docs and a landing
page with some usage details. This page could certainly be enhanced, or
there could also be a landing page for it in the docs folder.
https://mxnet.incubator.apache.org/api/python/contrib/onnx.html
Gluon needs a new landing page, and could probably be folded into the Docs
navigation. Why landing pages? We shouldn't have navigation items that take
you off of the site without warning. Github would be an exception. But for
books and tutorials suites that are off-deck, I think it would be a good
habit to describe what it is and indicate where it goes. The tutorials page
has this notion with little icons now.
The new Scala infer package will be buried once it rolls off of the new
highlights section of the home page. Maybe we should have navigation items
for things like model serving and inference along with landing pages for
each?
Then we have a couple of projects outside MXNet, but directly add value,
and could be highlighted with a landing page to describe what it does, how
to install it, plus links to the projects and some examples:
* MXNet Model Server
* Keras-MXNet
I'm sure there's more. Let's discuss and promote all these good things.
Cheers,
Aaron
Re: landing pages for the website
Posted by Aaron Markham <aa...@gmail.com>.
I've created a PR for an ecosystem page. Please let me know your feedback.
https://github.com/apache/incubator-mxnet/pull/11528
On Sat, Jun 23, 2018 at 2:50 AM, Ivan Serdyuk <lo...@gmail.com>
wrote:
> I wonder if there would be a page for a list of startups, which use your
> project (integration)? With details of type of cloud/inter-cloud (private;
> hybrid; big commercail ones)
>
> On Fri, Jun 22, 2018 at 9:44 PM, Steffen Rochel <st...@gmail.com>
> wrote:
>
> > Hi Aaron - support Mu's suggestion to add an ecosystems page to add links
> > to MXNet related projects (gluon toolkits, mxnet model server, keras,
> onnx,
> > sockeye etc) to promote the solutions in the MXNet ecosystem. What do you
> > suggest as next steps?
> > Steffen
> >
> > On Mon, Jun 11, 2018 at 5:19 PM Mu Li <mu...@gmail.com> wrote:
> >
> > > Thanks for the proposal, Aaron. The landing page idea is great. I feel
> we
> > > should group MXNet topics into landing pages, such as Gluon you
> > mentioned,
> > > also performance, and deployment. But I'm less sure if we want to add
> too
> > > many contents from 3rd party projects into MXNet, otherwise, it may
> make
> > > the MXnet docs have too many dependencies and hard to maintain. We may
> > just
> > > create an "ecosystem" page to add links to all high-quality 3rd party
> > > libraries.
> > >
> > > On Mon, Jun 11, 2018 at 5:11 PM, Aaron Markham <
> > aaron.s.markham@gmail.com>
> > > wrote:
> > >
> > > > Hi dev@,
> > > > We've had a lot of great expansions to MXNet's functionality and
> family
> > > of
> > > > tools in recent months. I would like to gauge the temp on what would
> be
> > > > good to highlight, and what would be good as navigation items with
> > actual
> > > > landing pages.
> > > >
> > > > For example, when ONNX was added, being in a contrib package, it was
> > > going
> > > > to totally buried, so it has a navigation item under Docs and a
> landing
> > > > page with some usage details. This page could certainly be enhanced,
> or
> > > > there could also be a landing page for it in the docs folder.
> > > > https://mxnet.incubator.apache.org/api/python/contrib/onnx.html
> > > >
> > > > Gluon needs a new landing page, and could probably be folded into the
> > > Docs
> > > > navigation. Why landing pages? We shouldn't have navigation items
> that
> > > take
> > > > you off of the site without warning. Github would be an exception.
> But
> > > for
> > > > books and tutorials suites that are off-deck, I think it would be a
> > good
> > > > habit to describe what it is and indicate where it goes. The
> tutorials
> > > page
> > > > has this notion with little icons now.
> > > >
> > > > The new Scala infer package will be buried once it rolls off of the
> new
> > > > highlights section of the home page. Maybe we should have navigation
> > > items
> > > > for things like model serving and inference along with landing pages
> > for
> > > > each?
> > > >
> > > > Then we have a couple of projects outside MXNet, but directly add
> > value,
> > > > and could be highlighted with a landing page to describe what it
> does,
> > > how
> > > > to install it, plus links to the projects and some examples:
> > > >
> > > > * MXNet Model Server
> > > > * Keras-MXNet
> > > >
> > > > I'm sure there's more. Let's discuss and promote all these good
> things.
> > > >
> > > > Cheers,
> > > > Aaron
> > > >
> > >
> >
>
Re: landing pages for the website
Posted by Ivan Serdyuk <lo...@gmail.com>.
I wonder if there would be a page for a list of startups, which use your
project (integration)? With details of type of cloud/inter-cloud (private;
hybrid; big commercail ones)
On Fri, Jun 22, 2018 at 9:44 PM, Steffen Rochel <st...@gmail.com>
wrote:
> Hi Aaron - support Mu's suggestion to add an ecosystems page to add links
> to MXNet related projects (gluon toolkits, mxnet model server, keras, onnx,
> sockeye etc) to promote the solutions in the MXNet ecosystem. What do you
> suggest as next steps?
> Steffen
>
> On Mon, Jun 11, 2018 at 5:19 PM Mu Li <mu...@gmail.com> wrote:
>
> > Thanks for the proposal, Aaron. The landing page idea is great. I feel we
> > should group MXNet topics into landing pages, such as Gluon you
> mentioned,
> > also performance, and deployment. But I'm less sure if we want to add too
> > many contents from 3rd party projects into MXNet, otherwise, it may make
> > the MXnet docs have too many dependencies and hard to maintain. We may
> just
> > create an "ecosystem" page to add links to all high-quality 3rd party
> > libraries.
> >
> > On Mon, Jun 11, 2018 at 5:11 PM, Aaron Markham <
> aaron.s.markham@gmail.com>
> > wrote:
> >
> > > Hi dev@,
> > > We've had a lot of great expansions to MXNet's functionality and family
> > of
> > > tools in recent months. I would like to gauge the temp on what would be
> > > good to highlight, and what would be good as navigation items with
> actual
> > > landing pages.
> > >
> > > For example, when ONNX was added, being in a contrib package, it was
> > going
> > > to totally buried, so it has a navigation item under Docs and a landing
> > > page with some usage details. This page could certainly be enhanced, or
> > > there could also be a landing page for it in the docs folder.
> > > https://mxnet.incubator.apache.org/api/python/contrib/onnx.html
> > >
> > > Gluon needs a new landing page, and could probably be folded into the
> > Docs
> > > navigation. Why landing pages? We shouldn't have navigation items that
> > take
> > > you off of the site without warning. Github would be an exception. But
> > for
> > > books and tutorials suites that are off-deck, I think it would be a
> good
> > > habit to describe what it is and indicate where it goes. The tutorials
> > page
> > > has this notion with little icons now.
> > >
> > > The new Scala infer package will be buried once it rolls off of the new
> > > highlights section of the home page. Maybe we should have navigation
> > items
> > > for things like model serving and inference along with landing pages
> for
> > > each?
> > >
> > > Then we have a couple of projects outside MXNet, but directly add
> value,
> > > and could be highlighted with a landing page to describe what it does,
> > how
> > > to install it, plus links to the projects and some examples:
> > >
> > > * MXNet Model Server
> > > * Keras-MXNet
> > >
> > > I'm sure there's more. Let's discuss and promote all these good things.
> > >
> > > Cheers,
> > > Aaron
> > >
> >
>
Re: landing pages for the website
Posted by Steffen Rochel <st...@gmail.com>.
Hi Aaron - support Mu's suggestion to add an ecosystems page to add links
to MXNet related projects (gluon toolkits, mxnet model server, keras, onnx,
sockeye etc) to promote the solutions in the MXNet ecosystem. What do you
suggest as next steps?
Steffen
On Mon, Jun 11, 2018 at 5:19 PM Mu Li <mu...@gmail.com> wrote:
> Thanks for the proposal, Aaron. The landing page idea is great. I feel we
> should group MXNet topics into landing pages, such as Gluon you mentioned,
> also performance, and deployment. But I'm less sure if we want to add too
> many contents from 3rd party projects into MXNet, otherwise, it may make
> the MXnet docs have too many dependencies and hard to maintain. We may just
> create an "ecosystem" page to add links to all high-quality 3rd party
> libraries.
>
> On Mon, Jun 11, 2018 at 5:11 PM, Aaron Markham <aa...@gmail.com>
> wrote:
>
> > Hi dev@,
> > We've had a lot of great expansions to MXNet's functionality and family
> of
> > tools in recent months. I would like to gauge the temp on what would be
> > good to highlight, and what would be good as navigation items with actual
> > landing pages.
> >
> > For example, when ONNX was added, being in a contrib package, it was
> going
> > to totally buried, so it has a navigation item under Docs and a landing
> > page with some usage details. This page could certainly be enhanced, or
> > there could also be a landing page for it in the docs folder.
> > https://mxnet.incubator.apache.org/api/python/contrib/onnx.html
> >
> > Gluon needs a new landing page, and could probably be folded into the
> Docs
> > navigation. Why landing pages? We shouldn't have navigation items that
> take
> > you off of the site without warning. Github would be an exception. But
> for
> > books and tutorials suites that are off-deck, I think it would be a good
> > habit to describe what it is and indicate where it goes. The tutorials
> page
> > has this notion with little icons now.
> >
> > The new Scala infer package will be buried once it rolls off of the new
> > highlights section of the home page. Maybe we should have navigation
> items
> > for things like model serving and inference along with landing pages for
> > each?
> >
> > Then we have a couple of projects outside MXNet, but directly add value,
> > and could be highlighted with a landing page to describe what it does,
> how
> > to install it, plus links to the projects and some examples:
> >
> > * MXNet Model Server
> > * Keras-MXNet
> >
> > I'm sure there's more. Let's discuss and promote all these good things.
> >
> > Cheers,
> > Aaron
> >
>
Re: landing pages for the website
Posted by Mu Li <mu...@gmail.com>.
Thanks for the proposal, Aaron. The landing page idea is great. I feel we
should group MXNet topics into landing pages, such as Gluon you mentioned,
also performance, and deployment. But I'm less sure if we want to add too
many contents from 3rd party projects into MXNet, otherwise, it may make
the MXnet docs have too many dependencies and hard to maintain. We may just
create an "ecosystem" page to add links to all high-quality 3rd party
libraries.
On Mon, Jun 11, 2018 at 5:11 PM, Aaron Markham <aa...@gmail.com>
wrote:
> Hi dev@,
> We've had a lot of great expansions to MXNet's functionality and family of
> tools in recent months. I would like to gauge the temp on what would be
> good to highlight, and what would be good as navigation items with actual
> landing pages.
>
> For example, when ONNX was added, being in a contrib package, it was going
> to totally buried, so it has a navigation item under Docs and a landing
> page with some usage details. This page could certainly be enhanced, or
> there could also be a landing page for it in the docs folder.
> https://mxnet.incubator.apache.org/api/python/contrib/onnx.html
>
> Gluon needs a new landing page, and could probably be folded into the Docs
> navigation. Why landing pages? We shouldn't have navigation items that take
> you off of the site without warning. Github would be an exception. But for
> books and tutorials suites that are off-deck, I think it would be a good
> habit to describe what it is and indicate where it goes. The tutorials page
> has this notion with little icons now.
>
> The new Scala infer package will be buried once it rolls off of the new
> highlights section of the home page. Maybe we should have navigation items
> for things like model serving and inference along with landing pages for
> each?
>
> Then we have a couple of projects outside MXNet, but directly add value,
> and could be highlighted with a landing page to describe what it does, how
> to install it, plus links to the projects and some examples:
>
> * MXNet Model Server
> * Keras-MXNet
>
> I'm sure there's more. Let's discuss and promote all these good things.
>
> Cheers,
> Aaron
>