[EPIC] Improve the Jupyter Book 2 Launch Button UX

[agoose77]

Context

At the time of the MyST retreat co-located with AGU, there was a discussion around the benefits of collapsing the two-tab "hub" and "binder" UI for bring-your-own-binder/hub (BYOB) into a single URL and launch button. Theoretically, we should be able to detect what kind of deployment the user is trying to make according to the URL. Simplifying this will reduce the amount of UI we need to show the user, and make it possible start talking at a higher-level with respect to the "launch" feature.

We also want to support pre-defining a set of BinderHub / JupyterHub targets that community readers can jump into. These are normally resources that are associated with the deployment e.g. https://docs.<COMMUNITY>.2i2c.cloud/. We should extend the theme component to facilitate this.

Making this enhancement will require some changes in jupyter-book/myst-theme, jupyterhub, etc.

Task list

• Allow CORS requests to /hub/api by default jupyterhub/jupyterhub#4966
• Detect Hub vs Binder in launch button jupyter-book/myst-theme#507
• Add UX guidance to communicate Hub/Binder feature requirements of launch button jupyter-book/myst-theme#511
• Support the definition of pre-populated Binder and JupyterHub services jupyter-book/myst-theme#512

Definition of Done

• Each of the user stories above is enabled, or explicitly pushed to a future initiative.
• All new functionality is fully documented in the upstream documentation.

[agoose77]

Closing this in favour of lifting Epics into their parent Initiative for easier tracking.