Update jhub apps related docs (#490)

* update jhub apps images and text

* update default value of app launcher

Author: kcpevey

docs/docs/how-tos/jhub-app-launcher.md

@@ -6,8 +6,14 @@ description: Using JHub App Launcher with Nebari
 
 # JHub App Launcher with Nebari
 
-[JHub App Launcher](https://github.com/nebari-dev/jhub-apps) is a generalized server launcher
-for JupyterHub. You can use it to create and share apps using various frameworks like:
+[JHub App Launcher](https://jhub-apps.nebari.dev/) is a generalized server launcher
+for deploying web applications via JupyterHub. The App Launcher serves as the "home"
+page for Nebari - providing access to various Nebari services (e.g. JupyterLab, VS Code, 
+conda-store) and access to deploy custom web apps. 
+
+![JHub App Launcher home screen](/img/how-tos/jhub_apps_home.png)
+
+You can use it to create and share apps using various frameworks such as:
 
 - Panel
 - Bokeh
@@ -16,9 +22,9 @@ for JupyterHub. You can use it to create and share apps using various frameworks
 - Voila
 - Gradio
 - JupyterLab
-- Generic Python Command
+- Any generic Python command
 
-## Installation
+## Installation on Nebari
 
 JHub App Launcher can be enabled on Nebari by adding the following in the
 `nebari-config.yml`:
@@ -29,12 +35,18 @@ jhub_apps:
 ```
 
 :::note
-JHub App Launcher is enabled by default in the Nebari after version
-[2023.12.1](https://github.com/nebari-dev/nebari/releases/tag/2023.12.1).
+JHub App Launcher is was integrated into Nebari in version
+[2023.12.1](https://github.com/nebari-dev/nebari/releases/tag/2023.12.1)
+and is not enabled by default.
 :::
 
-## Environment
+## Usage
 
-To be able to create apps using the JHub App Launcher in Nebari,
-you need to have `jhub-apps` and the corresponding framework (for example, `panel`)
-in your conda-store generated conda environment.
+Documentation on how to create apps is included in the 
+[JHub Apps documentation](https://jhub-apps.nebari.dev/docs/category/create-apps).
+Deployed apps on Nebari will utilize environments from conda-store. All apps 
+will need to include `jhsingle-native-proxy >= 0.8.2` in their environment along with 
+other framework-specific dependencies. For example, deploying a `panel` app will 
+require `panel` itself and additional tools for deploying `panel` apps such as 
+`bokeh-root-cmd >= 0.1.2`. See the documentation for specific requirements on 
+each framework. 

docs/docs/tutorials/create-dashboard.md

@@ -6,7 +6,7 @@ description: Quickly build and deploy a panel dashboard in Nebari
 
 # Create, deploy, and share dashboards and apps
 
-Analyzing data with visualizations provides insights, and a dashboard stitches these insights into a meaningful story. There are many great open source dashboards tools out there that you can use to organize and display your data in an engaging and digestible way.
+Analyzing data with visualizations provides insights, and a dashboard stitches these insights into a meaningful story. There are many great open source dashboarding tools out there that you can use to organize and display your data in an engaging and digestible way.
 
 In this tutorial, you'll learn how to create a new dashboard with [Panel](https://panel.holoviz.org/) within Nebari. You'll also learn how to share your newly created dashboard with other users using JHub App Launcher.
 
@@ -19,15 +19,15 @@ Since, CDS Dashboards is deprecated, the documentation will be removed soon.
 
 ## Supported frameworks
 
-This tutorials demonstrates a Panel dashboard built with HoloViews and Bokeh as the backend, but Nebari supports several other frameworks:
+This tutorial demonstrates a Panel dashboard built with HoloViews and Bokeh as the backend, but Nebari supports several other frameworks:
 
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
 <Tabs>
 <TabItem value="jhub-apps" label="JHub App Launcher" default>
 
-JHub App launcher supports `Panel`, `Bokeh`, `Streamlit`, `Plotly Dash`, `Voila`, `Gradio`, `JupyterLab`, `Generic Python Command`.
+JHub App launcher supports `Panel`, `Bokeh`, `Streamlit`, `Plotly Dash`, `Voila`, `Gradio`, `JupyterLab`, and `Any generic Python command`.
 
 </TabItem>
 <TabItem value="cds-dashboards" label="CDS Dashboards">
@@ -115,11 +115,7 @@ hover = HoverTool(tooltips=[("avg diameter", "@avg_diameter_inch"),
 combine_plot = plot_bar.opts(tools=[hover]) + plot_curve.opts(line_dash='dashed')
 
 # creating a dashboard using panel
-dashboard = pn.template.BootstrapTemplate(
-          site="About 🌳",
-          title="Species and more",
-          main=[combine_plot]
-          ).servable()
+pn.Row(combine_plot).servable()
 ```
 
 You can run all the cells in your notebook and view the Panel dashboard using the "Preview with Panel" button in the notebook toolbar:
@@ -129,30 +125,24 @@ You can run all the cells in your notebook and view the Panel dashboard using th
 This interactive feature of Panel makes it possible to rapidly prototype and iterate on dashboards.
 Feel free to add more plots or different styles to your plots!
 
-## Deploy the dashboard with JHub App Launcher
+## Deploy the dashboard
 
-1. In the Nebari Home Page (in the top navigation, `Nebari` -> `Hub Control Panel`) click on **"Create App"** to create a new web application for your dashboard.
-2. In the app creation interface, enter or select the following:
-   - **Display Name** - Provide meaningful name for your application
-   - **Description (optional)** - Add addition information about the application
-   - **Thumbnail (optional)** - Choose a meaningful thumbnail for your application. The default thumbnail is the application framework's logo.
-   - **Framework** - Select the framework used by your application. For this tutorial, select Panel.
-   - **Filepath** - Path (from root in JupyterLab) to your application code file. For this tutorial, path to the Jupyter Notebook.
-   - **Conda Environment** - Same [environment](#1-create-environment-and-notebook) used while developing your notebook/script which has `jhub-apps` and the corresponding framework.
-   - **Spawner profile** - Instance type (i.e. machines with CPU/RAM/GPU resources) required for running your application.
-   - **Allow Public Access** - Toggle to share the application with your team.
+<Tabs>
+<TabItem value="jhub-apps" label="JHub App Launcher" default>
 
-  <p align="center">
-    <img src="/img/tutorials/jhub-apps-create-new-app.png" width="50%"/>
-  </p>
+1. On the Nebari Home Page (from JupyterLab, click on the Nebari logo in the top right corner or go to `File` -> `Home`) click on **"Create App"** to create a new web application for your dashboard.
+2. Follow the [general instructions](https://jhub-apps.nebari.dev/docs/create-apps/general-app) from the JHub Apps documentation to fill out the `Create app` form.
+3. Click **Next**. You'll be redirected to the Spawner profile page. This page will allow you to select the server in which you want your app to run. These options will vary based on the setup of your Nebari deployment (which server types are available overall) and the permissions of your user (which server types you personally have access to). 
+4. JHub App Launcher will deploy your app (which can take several minutes to complete) and automatically redirect you to it.
 
-3. Click on **Submit**. JHub App Launcher deploy your app (which can take a few minutes to complete) and automatically redirect you to it.
+Your dashboard app will be available in the Nebari Home page, under "My Apps". If you allowed shared access, it will be available under "Shared Apps" for those with whom you have shared the app.
+
+</TabItem>
 
-Your dashboard app will be available in the Nebari Home page, under "My Apps". If you allowed public access, it will be available under "Shared Apps" for your team.
 
-## Deploy and share the dashboard with CDS Dashboards (Nebari v2023.7.1 or earlier)
+<TabItem value="cds-dashboards" label="CDS Dashboard" default>
 
-In this section, you'll use CDS Dashboards to publish and share your newly created `panel` dashboard.
+In this section, you'll use CDS Dashboards ((Nebari v2023.7.1 or earlier)) to publish and share your newly created `panel` dashboard.
 
 :::warning
 CDS Dashboards has been deprecated in 2023.9.1. Nebari 2023.7.1 is the last release that support CDS Dashboards.
@@ -193,12 +183,15 @@ This will trigger the deployment of your dashboard, and you'll be presented with
 
 If there are no errors encountered during this process, you will be automatically redirected to the dashboard!
 
+</TabItem>
+</Tabs>
+
 ## Manage apps in Nebari
 
 <Tabs>
 <TabItem value="jhub-apps" label="JHub App Launcher" default>
 
-All applications are available on the Nebari home page. From JupyterLAb, you can click on the `Nebari` menu tab and select `Hub Control Panel` to go to the home page.
+All applications are available on the Nebari home page (from JupyterLab, click on the Nebari logo in the top right corner or go to `File` -> `Home`).
 
 To manage an application, click on the three dots in the top right of the corresponding application card where you can:
 
@@ -234,7 +227,7 @@ You should be mindful of the incurring ongoing costs while the dashboard is runn
 
 ---
 
-Dashboards and apps can be a very handy tool to share information and insights with colleagues and external customers or collaborators. You can use this basic dashboard to build more complex dashboards, add more dynamic features, and start sharing data insights with others.
+Dashboards and apps can be very handy tools to share information and insights with colleagues and external customers or collaborators. You can use this basic dashboard to build more complex dashboards, add more dynamic features, and start sharing data insights with others.
 
 <!-- Internal links -->
 

docs/docs/tutorials/login-with-keycloak.md

@@ -13,8 +13,7 @@ This guide provides a basic overview of how to log in to your Nebari instance (t
 
 Navigate to the instance homepage.
 
-Once on the site, you will be prompted to log in, similar to
-the login page shown in the image below.
+Once on the site, you will be prompted to log in, similar to the login page shown in the image below. The text on this screen is configurable so your deployment may look slightly different.
 
 ![Nebari login screen](/img/how-tos/nebari_login_screen.png)
 
@@ -53,7 +52,7 @@ The home page, also referred to as
 "Landing page", "JupyterHub launcher", or "App Launcher",
 lists Nebari's core **services** and allows you to [create and share web apps][create-dashboard].
 
-Click on the **"JupyterLab"** button under **"Services"** to start a server and launch JupyterLab:
+Click on the **"JupyterLab"** button under **"Quick Access"** to start a server and launch JupyterLab:
 
 ![Nebari home page with Services: JupyterLab, Argo, Users, Environments, Monitoring, VSCode; My Apps: JupyterLab (default JupyterLab instance); and Shared Apps.](/img/tutorials/nebari-home.png)
 
@@ -89,11 +88,11 @@ Select an appropriate profile and click **"Start"**.
 
 ## 5. Start your server
 
-JupyterLab starts to launch.
+After clicking "Start", your JupyterLab instance starts to launch.
 
-This step may take up to several minutes due to Nebari use of autoscaling under the hood. Ultimately this autoscaling feature helps reduce costs when the cluster is idle.
+This step may take up to several minutes due to Nebari's use of autoscaling under the hood. Ultimately this autoscaling feature helps reduce costs when the cluster is idle.
 
-A successful launch process shows a purple progress bar:
+A progress bar is shown while the server is being set up:
 
 ![Nebari start server](/img/how-tos/nebari_server_start.png)
 
@@ -109,7 +108,7 @@ During this time you might see some log messages that detail the autoscaling pro
 :::warning
 
 - The starting up sequence can take up to several minutes, depending on the size of the cluster. If the server is not accessible **after 10 minutes**, an error will be shown, and you will be redirected to the Home page. Please check the [troubleshooting docs][troubleshooting] for more information.
-- The Event logs may include warnings about `"[Warning] 0/2 nodes are available: 2 node(s) didn't match Pod's node affinity/selector ..." `. This is normal behaviour as cluster sometimes need to expand in order to start the server.
+- The Event logs may include warnings about `"[Warning] 0/2 nodes are available: 2 node(s) didn't match Pod's node affinity/selector ..." `. This is **normal behaviour** as the cluster sometimes need to expand in order to start the server.
 - Warning such as `"[Warning]" Unable to retrieve some image pull secrets ..."` can also be safely ignored.
   :::