holoviz · philippjfr · Feb 25, 2024 · Jan 16, 2024 · Jan 16, 2024 · Jan 16, 2024
diff --git a/doc/_static/css/custom.css b/doc/_static/css/custom.css
@@ -77,3 +77,7 @@ button.copybtn:hover {
 .o-tooltip--left:after {
   background: none;
 }
+
+video {
+  max-width: 100%;
+}
diff --git a/doc/_static/images/align-cards-solution.png b/doc/_static/images/align-cards-solution.png
diff --git a/doc/_static/images/awesome-panel.png b/doc/_static/images/awesome-panel.png
diff --git a/doc/_static/images/build_chatbot_chat_section.png b/doc/_static/images/build_chatbot_chat_section.png
diff --git a/doc/_static/images/develop_editor_breakpoint.png b/doc/_static/images/develop_editor_breakpoint.png
diff --git a/doc/_static/images/develop_editor_click_me.png b/doc/_static/images/develop_editor_click_me.png
diff --git a/doc/_static/images/develop_editor_hover.png b/doc/_static/images/develop_editor_hover.png
diff --git a/doc/_static/images/develop_editor_layout0.png b/doc/_static/images/develop_editor_layout0.png
diff --git a/doc/_static/images/develop_editor_layout1.png b/doc/_static/images/develop_editor_layout1.png
diff --git a/doc/_static/images/develop_editor_panel_serve_after.png b/doc/_static/images/develop_editor_panel_serve_after.png
diff --git a/doc/_static/images/develop_editor_panel_serve_before.png b/doc/_static/images/develop_editor_panel_serve_before.png
diff --git a/doc/_static/images/develop_editor_param.png b/doc/_static/images/develop_editor_param.png
diff --git a/doc/_static/images/develop_editor_reference_guide.png b/doc/_static/images/develop_editor_reference_guide.png
diff --git a/doc/_static/images/develop_editor_serve_app.png b/doc/_static/images/develop_editor_serve_app.png
diff --git a/doc/_static/images/develop_notebook_panel_serve_after.png b/doc/_static/images/develop_notebook_panel_serve_after.png
diff --git a/doc/_static/images/develop_notebook_panel_serve_before.png b/doc/_static/images/develop_notebook_panel_serve_before.png
diff --git a/doc/_static/images/develop_notebook_reload_preview.png b/doc/_static/images/develop_notebook_reload_preview.png
diff --git a/doc/_static/images/develop_notebook_simple_example.png b/doc/_static/images/develop_notebook_simple_example.png
diff --git a/doc/_static/images/develop_notebook_simple_example_add_hello_again.png b/doc/_static/images/develop_notebook_simple_example_add_hello_again.png
diff --git a/doc/_static/images/develop_notebook_simple_example_add_hello_again_and_again.png b/doc/_static/images/develop_notebook_simple_example_add_hello_again_and_again.png
diff --git a/doc/_static/images/develop_notebook_simple_example_open_preview.png b/doc/_static/images/develop_notebook_simple_example_open_preview.png
diff --git a/doc/_static/images/editor_server_app.png b/doc/_static/images/editor_server_app.png
diff --git a/doc/_static/images/explore_data_perspective_chart.png b/doc/_static/images/explore_data_perspective_chart.png
diff --git a/doc/_static/images/explore_data_perspective_table.png b/doc/_static/images/explore_data_perspective_table.png
diff --git a/doc/_static/images/hugging_face_spaces_delete.png b/doc/_static/images/hugging_face_spaces_delete.png
diff --git a/doc/_static/images/hugging_face_spaces_duplicate.png b/doc/_static/images/hugging_face_spaces_duplicate.png
diff --git a/doc/_static/images/hugging_face_spaces_duplicate_form.png b/doc/_static/images/hugging_face_spaces_duplicate_form.png
diff --git a/doc/_static/images/hugging_face_spaces_files.png b/doc/_static/images/hugging_face_spaces_files.png
diff --git a/doc/_static/images/hugging_face_spaces_panel.png b/doc/_static/images/hugging_face_spaces_panel.png
diff --git a/doc/_static/images/indicators_section.png b/doc/_static/images/indicators_section.png
diff --git a/doc/_static/images/join_community_discord.png b/doc/_static/images/join_community_discord.png
diff --git a/doc/_static/images/join_community_discourse.png b/doc/_static/images/join_community_discourse.png
diff --git a/doc/_static/images/join_community_github.png b/doc/_static/images/join_community_github.png
diff --git a/doc/_static/images/join_community_linkedin.png b/doc/_static/images/join_community_linkedin.png
diff --git a/doc/_static/images/join_community_open_source.png b/doc/_static/images/join_community_open_source.png
diff --git a/doc/_static/images/join_community_twitter.png b/doc/_static/images/join_community_twitter.png
diff --git a/doc/_static/images/jupyter_panel_preview_in_action.png b/doc/_static/images/jupyter_panel_preview_in_action.png
diff --git a/doc/_static/images/layouts_section.png b/doc/_static/images/layouts_section.png
diff --git a/doc/_static/images/monitoring_dashboard.png b/doc/_static/images/monitoring_dashboard.png
diff --git a/doc/_static/images/notebook_inspect_param_class.png b/doc/_static/images/notebook_inspect_param_class.png
diff --git a/doc/_static/images/notebook_inspect_param_instance.png b/doc/_static/images/notebook_inspect_param_instance.png
diff --git a/doc/_static/images/notebook_inspect_print.png b/doc/_static/images/notebook_inspect_print.png
diff --git a/doc/_static/images/notebook_inspect_print_1.png b/doc/_static/images/notebook_inspect_print_1.png
diff --git a/doc/_static/images/notebook_inspect_question_mark.png b/doc/_static/images/notebook_inspect_question_mark.png
diff --git a/doc/_static/images/notebook_inspect_shift_tab.png b/doc/_static/images/notebook_inspect_shift_tab.png
diff --git a/doc/_static/images/notebook_inspect_shift_tab_link.png b/doc/_static/images/notebook_inspect_shift_tab_link.png
diff --git a/doc/_static/images/notebook_intslider_reference_doc.png b/doc/_static/images/notebook_intslider_reference_doc.png
diff --git a/doc/_static/images/panel-chat-examples.png b/doc/_static/images/panel-chat-examples.png
diff --git a/doc/_static/images/panel-serve-ipynb-app.png b/doc/_static/images/panel-serve-ipynb-app.png
diff --git a/doc/_static/images/panel-serve-ipynb-notebook.png b/doc/_static/images/panel-serve-ipynb-notebook.png
diff --git a/doc/_static/images/panel-serve-multipage-app.png b/doc/_static/images/panel-serve-multipage-app.png
diff --git a/doc/_static/images/panel-serve-py-app.png b/doc/_static/images/panel-serve-py-app.png
diff --git a/doc/_static/images/panes.png b/doc/_static/images/panes.png
diff --git a/doc/_static/images/panes_markdown_reference.png b/doc/_static/images/panes_markdown_reference.png
diff --git a/doc/_static/images/structure_data_store_app.png b/doc/_static/images/structure_data_store_app.png
diff --git a/doc/_static/images/templates_customized_dark.png b/doc/_static/images/templates_customized_dark.png
diff --git a/doc/_static/images/templates_customized_default.png b/doc/_static/images/templates_customized_default.png
diff --git a/doc/_static/images/templates_hello_world.png b/doc/_static/images/templates_hello_world.png
diff --git a/doc/_static/images/templates_hello_world_notebook.png b/doc/_static/images/templates_hello_world_notebook.png
diff --git a/doc/_static/images/templates_section.png b/doc/_static/images/templates_section.png
diff --git a/doc/_static/images/understand_load.png b/doc/_static/images/understand_load.png
diff --git a/doc/_static/images/understand_load_refresh.png b/doc/_static/images/understand_load_refresh.png
diff --git a/doc/_static/images/vscode-script.png b/doc/_static/images/vscode-script.png
diff --git a/doc/_static/images/widgets_button_reference.png b/doc/_static/images/widgets_button_reference.png
diff --git a/doc/_static/images/widgets_textinput_reference.png b/doc/_static/images/widgets_textinput_reference.png
diff --git a/doc/explanation/components/components_overview.md b/doc/explanation/components/components_overview.md
diff --git a/doc/tutorials/development.md → doc/explanation/develop_seamlessly.md b/doc/tutorials/development.md → doc/explanation/develop_seamlessly.md
@@ -1,19 +1,17 @@
-# Effective Development
+# Develop Seamlessly Across Environments
 
-:::{note} Tutorial 4. **Efficient Development**
-:icon: false
+Our objective is to empower teams to seamlessly utilize Panel regardless of the development environment, e.g. Jupyter Notebook, Jupyter Lab, Binder, Google Colab, Spyder, VS Code, and PyCharm.
 
- It's also important for you to be able to use a coding environment you are comfortable with. To this end, Panel offers very good support for Jupyter Notebooks (Classic and JupyterLab) and editors like Visual Studio Code, which are the two environments we will cover in this guide.
-
-:::
 
 ## Notebook
 
+We love notebooks.
+
 ### Notebook friendly
 
-Jupyter notebooks have been supported in Panel since day 1 and more generally since the inception of the HoloViz project. Notebooks are environments that allow to iterate quickly, running some code and observing instantaneously its output. Notebooks also happen to be a valid deployment option:
+Jupyter notebooks have been supported in Panel since day 1. Notebooks are environments that allow one to iterate quickly, running some code and observing instantaneously its output. Notebooks also happen to be a valid deployment option:
 
-- you can actually develop apps that are meant to live only in a notebook, that you will share as a file with your colleagues and friends. Panel allows you to make your notebooks more user friendly, like IPywidgets does.
+- you can actually develop apps that are meant to live only in a notebook, that you will share as a file with your colleagues and friends. Panel allows you to make your notebooks more user friendly, like [IPywidgets](https://ipywidgets.readthedocs.io/en/stable/) does.
 - you can serve a notebook with `panel serve file.ipynb`, Panel will parse your notebook to collect all of its code and run it as if it were a Python script.
 
 Jupyter notebooks aren't the only flavor of notebooks available, Panel also supports Visual Studio Code and Google Colab notebooks, and probably works fine on other platforms. For Visual Studio Code notebooks, you will need to install the `jupyter_bokeh` package in your environment.
@@ -28,7 +26,7 @@ import panel as pn
 pn.extension()
 ```
 
-The extension ensures that all required Javascript and CSS resources are added to your notebook environment. If you are going to be using any custom extensions, such as [Vega](../reference/panes/Vega.md) or [Tabulator](../reference/widgets/Tabulator.md) you must ensure that you initialize these as well.
+The extension ensures that the [`pyviz_comms`](https://github.com/holoviz/pyviz_comms) and all required Javascript and CSS resources are added to your notebook environment. If you are going to be using any custom extensions, such as [Vega](../reference/panes/Vega.md) or [Tabulator](../reference/widgets/Tabulator.md) you must ensure that you initialize these as well.
 
 ```{pyodide}
 pn.extension('vega', 'tabulator')
@@ -69,7 +67,7 @@ pn.Row(w, pn.bind(compute, w))
 
 ### Render templates
 
-You have been told in the previous guide to avoid rendering Panel templates in a notebook. That's however not a dead end! There are two approaches you can leverage to display an app that is wrapped in a template while working from a notebook, in addition to just being able to serve the notebook with `panel serve notebook.ipynb`.
+You have been told in the Panel tutorial to avoid rendering Panel templates in a notebook. That's however not a dead end! There are two approaches you can leverage to display an app that is wrapped in a template while working from a notebook, in addition to just being able to serve the notebook with `panel serve notebook.ipynb`.
 
 Templates, as any other Panel visual components, are equipped with the `.show()` method that when called starts a Bokeh server, serves your app and opens it in a new tab. While this approach doesn't allow you to iterate super quickly, it's a simple way to check what your app looks like when served.
 
@@ -116,11 +114,13 @@ This is what you should be able to see after a little while. Now tick `Render on
 
 ![alt text](../_static/images/jlabpreview.png)
 
-## Visual Studio Code
+## Editor
+
+Editors like VS Code and PyCharm have quickly become some of the most popular Python coding environment.
 
-Visual Studio Code (VS Code) has quickly become one of the most popular Python coding environment. In this section you will see how you can to set yourself a nice developer experience with VS Code when developing a Panel app.
+### Serve apps with autoreload
 
-### Setup and autoreload
+To enable a quick feedback loop while developing, we support serving your apps with autoreload.
 
 Save the content of the next cell in a file named `app.py`.
 
@@ -153,35 +153,15 @@ The `--show` flag will open a browser tab with the live app and the `--autoreloa
 
 ![VSCode Preview](../_static/images/vscode_preview.png)
 
-### Debugging
-
-While you can debug your app using the often blamed but never outperformed `print`, or by manually adding breakpoints with `breakpoint()`, the VS Code integrated debugger offers a more user friendly experience.
-
-To configure the integrated debugger for Panel, you will need to add a debugging configuration like the following.
-
-```json
-// .vscode/launch.json
-{
-    "version": "0.2.0",
-    "configurations": [
-        {
-            "name": "panel serve",
-            "type": "python",
-            "request": "launch",
-            "program": "-m",
-            "args": [
-                "panel",
-                "serve",
-                "${relativeFile}",
-                "--show"
-            ],
-            "console": "integratedTerminal",
-            "justMyCode": true
-        }
-    ]
-}
-```
+## Resources
+
+### Tutorials
+
+- [Develop in an Editor (Basic)](../tutorials/basic/develop_editor.md)
+- [Develop in an Editor (Intermediate)](../tutorials/intermediate/develop_editor.md)¨
+- [Develop in a Notebook (Basic)](../tutorials/basic/develop_notebook.md)
 
-With this configuration in place, launching the debugger will serve the file you are working on with Panel, open a new browser tab pointing at the served app. Interact then with your app to hit one of the breakpoints you set up in VS Code.
+### How-to
 
-![VSCode Debugging](../static/images/vscode_debug.png)
+- [Configure VS Code](../how_to/editor/vscode_configure.md)
+- [Write apps in Markdown](../how_to/editor/markdown.md)
diff --git a/doc/explanation/index.md b/doc/explanation/index.md
@@ -4,6 +4,20 @@ The explanation section aims to clarify, deepen, and broaden the understanding o
 
 Beyond the [Getting Started > Core Concepts](../getting_started/core_concepts.md), which new users must complete before working with Panel, this explanation section is intended to help practitioners form and strengthen a conceptual web that facilitates new and advanced usage directions.
 
+## Develop
+
+::::{grid} 1 2 2 3
+:gutter: 1 1 1 2
+
+:::{grid-item-card} {octicon}`code;2.5em;sd-mr-1 sd-animate-grow50` Develop Seamlessly
+:link: api/index
+:link-type: doc
+
+Learn how we enable you and your team to work seamlessly with Panel across a wide range of development environments
+:::
+
+::::
+
 ## APIs
 
 ::::{grid} 1 2 2 3

diff --git a/doc/getting_started/index.md b/doc/getting_started/index.md
@@ -2,7 +2,7 @@
 
 Welcome to Panel!
 
-The getting started guide will get you set up with Panel and provide a basic overview of the features and strengths of Panel.
+The getting started guides are for those who would like to **quickly try out Panel** and **explore the features and strengths of Panel**.
 
 ---
 
@@ -33,14 +33,16 @@ Before we dig into some of the core concepts behind Panel this guide gives you a
 :link: core_concepts
 :link-type: doc
 
-Introduces you to some of the core concepts behind Panel, how to develop Panel applications effectively both in your IDE and in the notebook and some of the core features that make Panel such a powerful library.
+Introduces you to some of the core concepts behind Panel, how to develop Panel applications effectively both in your Editor and in the notebook and some of the core features that make Panel such a powerful library.
 
 +++
 [Learn more »](core_concepts)
 :::
 
 ::::
 
+As the next step after this Getting Started guide, we recommend learning the basics of Panel systematically via the *in depth* [Basic Tutorials](../tutorials/basic/index.md).
+
 ## Additional Resources
 
 - The [original announcement of Panel from 2019](https://blog.holoviz.org/panel_announcement.html).

diff --git a/doc/how_to/authentication/basic.md b/doc/how_to/authentication/basic.md
@@ -59,7 +59,7 @@ panel serve app.py --basic-auth credentials.json --cookie-secret my_super_safe_c
 
 The basic auth provider will now check the provided credentials against the credentials declared in this file.
 
-:::note
+:::{admonition} Note
 When serving an application dynamically using `pn.serve` you can also provide a dictionary of usernames and passwords via the `basic_auth` keyword argument.
 :::
 

diff --git a/doc/how_to/components/construct_panes.md b/doc/how_to/components/construct_panes.md
@@ -6,7 +6,7 @@ This guide addresses how to construct Pane objects for displaying visible compon
 
 There are two main ways to construct a pane - explicitly or automatically.
 
-To explicitly construct a pane, use one of the pane types listed in the [component gallery](../../reference/index.md#panes). For example, you can create a Markdown pane as follows:
+To explicitly construct a pane, use one of the pane types listed in the [component gallery](https://panel.holoviz.org/reference/index.md#panes). For example, you can create a Markdown pane as follows:
 
 ```{pyodide}
 import panel as pn

diff --git a/doc/how_to/editor/editor.md b/doc/how_to/editor/editor.md
diff --git a/doc/how_to/editor/editor_debug.md b/doc/how_to/editor/editor_debug.md
diff --git a/doc/how_to/editor/index.md b/doc/how_to/editor/index.md
@@ -5,20 +5,6 @@ One of the main design goals for Panel was to make it seamless to work across de
 ::::{grid} 1 2 2 3
 :gutter: 1 1 1 2
 
-:::{grid-item-card} {octicon}`code-square;2.5em;sd-mr-1 sd-animate-grow50` Develop apps in an editor
-:link: editor
-:link-type: doc
-
-How to rapidly develop a Panel application in your favorite IDE or editor.
-:::
-
-:::{grid-item-card} {octicon}`bug;2.5em;sd-mr-1 sd-animate-grow50` Debug apps in an editor
-:link: editor_debug
-:link-type: doc
-
-How to debug a Panel application in your favorite IDE or editor.
-:::
-
 :::{grid-item-card} {octicon}`gear;2.5em;sd-mr-1 sd-animate-grow50` Configure VS Code
 :link: vscode_configure
 :link-type: doc
@@ -40,6 +26,6 @@ How to write Panel applications inside Markdown files.
 :hidden:
 :maxdepth: 2
 
-editor
+vscode_configure
 markdown
 ```
diff --git a/doc/how_to/editor/vscode_configure.md b/doc/how_to/editor/vscode_configure.md
@@ -4,7 +4,7 @@ This guide addresses how to configure VS Code for an efficient Panel development
 
 We assume you have
 
-- a basic understanding of [developing Panel apps in an editor](editor.md) and [working with Python in VS Code](https://code.visualstudio.com/docs/python/python-tutorial).
+- a basic understanding of [working with Python in VS Code](https://code.visualstudio.com/docs/python/python-tutorial).
 - installed the VS Code [Python extension](https://github.com/Microsoft/vscode-python)
 
 ---

diff --git a/doc/how_to/index.md b/doc/how_to/index.md
@@ -3,7 +3,7 @@
 The Panel How-to guides provide step by step recipes for solving essential problems and tasks that arise during your work. They assume that you've completed the Getting Started material and therefore already have some knowledge of how Panel works. There is no order to the guides, other than any potential prerequisites listed at the top of a page. Jump to the topic that is relevant to you now.
 
 
-## Prepare to develop
+## Develop Efficiently
 
 ::::{grid} 1 2 2 3
 :gutter: 1 1 1 2

diff --git a/doc/how_to/notebook/jupyterlabpreview.md b/doc/how_to/notebook/jupyterlabpreview.md
@@ -20,7 +20,7 @@ The *Preview* offers two update modes that are configurable in the preview tab:
 - automatic: toggle the *Render on save* checkbox ({far}`square-check`) for the app to be automatically re-rendered when you save your notebook.
 
 :::{tip}
-Panel [built-in templates](../../reference/index.md#templates) don't render necessarily well in a notebook as their styling can badly interact with the notebook built-in styling. Using the *Preview* is a good way to circumvent this issue, while still being able to work within JupyterLab .
+Panel [built-in templates](https://panel.holoviz.org/reference/index.md#templates) don't render necessarily well in a notebook as their styling can badly interact with the notebook built-in styling. Using the *Preview* is a good way to circumvent this issue, while still being able to work within JupyterLab .
 :::
 
 ## Related Resources
diff --git a/doc/how_to/server/commandline.md b/doc/how_to/server/commandline.md
@@ -1,4 +1,4 @@
-# Launching a server on the commandline
+# Launch a server on the commandline
 
 Once the app is ready for deployment it can be served using the Bokeh server.  For a detailed breakdown of the design and functionality of Bokeh server, see the [Bokeh documentation](https://bokeh.pydata.org/en/latest/docs/user_guide/server.html). The most important thing to know is that Panel (and Bokeh) provide a CLI command to serve a Python script, app directory, or Jupyter notebook containing a Bokeh or Panel app. To launch a server using the CLI, simply run:
 
@@ -20,7 +20,7 @@ We recommend installing `watchfiles`, which will provide a significantly better
 
 The ``panel serve`` command has the following options:
 
-``` console
+```bash
 positional arguments:
   DIRECTORY-OR-SCRIPT   The app directories or scripts to serve (serve empty document if not specified)
 

diff --git a/doc/how_to/streamlit_migration/caching.md b/doc/how_to/streamlit_migration/caching.md
@@ -14,7 +14,7 @@ In Panel
 - your script is run once when a user visits the page.
 - only *specific, bound functions* are rerun on user interactions.
 
-Thus with Panel you *may use* caching to to make the user experience nice and fast.
+Thus with Panel you *may use* caching to make the user experience nice and fast.
 
 In Panel you use `pn.cache` to speed up your apps. Check out the [Cache How-To Guides](../caching/index.md) for more details.
 

diff --git a/doc/how_to/streamlit_migration/get_started.md b/doc/how_to/streamlit_migration/get_started.md
@@ -1,6 +1,6 @@
-# Get Started migrating from Streamlit to Panel
+# Serve Apps
 
-This guide addresses the basics of migrating from Streamlit to Panel.
+This guide will show you how-to migrate and serve a *Hello World* application.
 
 ---
 

diff --git a/doc/how_to/streamlit_migration/index.md b/doc/how_to/streamlit_migration/index.md
@@ -14,14 +14,14 @@ These guides can also be used as:
 ::::{grid} 1 2 2 3
 :gutter: 1 1 1 2
 
-:::{grid-item-card} {octicon}`rocket;2.5em;sd-mr-1 sd-animate-grow50` Get Started
+:::{grid-item-card} {octicon}`rocket;2.5em;sd-mr-1 sd-animate-grow50` Serve Apps
 :link: get_started
 :link-type: doc
 
-How to convert a Hello World application from Streamlit to Panel
+How to convert a *Hello World* application from Streamlit to Panel and serve it
 :::
 
-:::{grid-item-card} {octicon}`device-desktop;2.5em;sd-mr-1 sd-animate-grow50` Display Content
+:::{grid-item-card} {octicon}`device-desktop;2.5em;sd-mr-1 sd-animate-grow50` Display Objects
 :link: panes
 :link-type: doc
 

diff --git a/doc/how_to/streamlit_migration/interactivity.md b/doc/how_to/streamlit_migration/interactivity.md
@@ -93,7 +93,7 @@ data = np.random.normal(1, 1, size=100)
 bins_input = pn.widgets.IntSlider(value=20, start=10, end=30, step=1, name="Bins")
 bplot = pn.bind(plot, data=data, bins=bins_input)
 
-pn.Column(bins, bplot).servable()
+pn.Column(bins_input, bplot).servable()
 ```
 
 ![Panel Basic Interactivity Example](https://assets.holoviz.org/panel/gifs/panel_interactivity_example.gif)

diff --git a/doc/how_to/streamlit_migration/layouts.md b/doc/how_to/streamlit_migration/layouts.md
@@ -1,6 +1,6 @@
-# Organize Components with Layouts
+# Layout Objects
 
-*Layouts* helps you organize your Panel *components*, i.e. *panes*, *widgets* and *layouts*.
+*Layouts* helps you organize your *objects* including Panel *components*.
 
 Panel provides layouts similar to the ones you know from Streamlit and many unique ones too.
 

diff --git a/doc/how_to/streamlit_migration/panes.md b/doc/how_to/streamlit_migration/panes.md
@@ -1,4 +1,4 @@
-# Displaying Content with Panes
+# Display Objects with Panes
 
 In Panel the objects that can display your Python objects are called *panes*. With Panels *panes* you will be able to:
 

diff --git a/doc/how_to/styling/design.md b/doc/how_to/styling/design.md
@@ -34,7 +34,7 @@ def create_components(design):
         pn.widgets.FloatSlider(name='Slider', design=design),
         pn.widgets.TextInput(name='TextInput', design=design),
         pn.widgets.Select(
-		    name='Select', options=['Biology', 'Chemistry', 'Physics'], design=design
+            name='Select', options=['Biology', 'Chemistry', 'Physics'], design=design
         ),
         pn.widgets.Button(
             name='Click me!', icon='hand-click', button_type='primary', design=design