I agree with this approach, although I’d like buy-in from (minimally) @rolweber and @lresende regarding the reorganization/introduction of the various gateway projects. So, assuming we would be moving forward, here would be my proposals for the various descriptions…
(I reluctantly used JupyterHub’s “A place to discuss” preamble. These are nothing more than seeding suggestions.)
Jupyter Server: A place to discuss Jupyter Server, the next-generation backend for Jupyter-based applications.
Gateway Projects: A place to discuss the gateway projects Jupyter Kernel Gateway, Jupyter Enterprise Gateway and NB2KG.
We’ll want a couple “When to use” topics right off the bat here.
@choldgraf - Can topics from a sub-category be pinned in the parent category? For example, each “when to use” would be useful in the sub-categories as well - so I’m thinking they should reside there and let the parent reference them (pinned as well).
Kernel Gateway: A place to discuss Jupyter Kernel Gateway, a web-server that headless access to Jupyter kernels.
Enterprise Gateway: A place to discuss Jupyter Enterprise Gateway, which extends Kernel Gateway to provide functionality for distributing Jupyter kernels across managed compute clusters and other enterprise-level functionality.
NB2KG: A place to discuss the NB2KG (Notebook 2 Kernel Gateway) project - a Notebook server extension that proxies kernel-related requests to Jupyter Kernel or Enterprise Gateway on behalf of the Jupyter Notebook or Lab web applications.