diff --git a/docs/advanced/7_docker/as_flow.png b/docs/advanced/7_docker/as_flow.png
index 1d641264c..4af003af7 100644
Binary files a/docs/advanced/7_docker/as_flow.png and b/docs/advanced/7_docker/as_flow.png differ
diff --git a/docs/advanced/7_docker/as_flow.png.avif b/docs/advanced/7_docker/as_flow.png.avif
deleted file mode 100644
index c18b5bf31..000000000
Binary files a/docs/advanced/7_docker/as_flow.png.avif and /dev/null differ
diff --git a/docs/advanced/7_docker/as_flow.png.webp b/docs/advanced/7_docker/as_flow.png.webp
deleted file mode 100644
index cac3b0bb5..000000000
Binary files a/docs/advanced/7_docker/as_flow.png.webp and /dev/null differ
diff --git a/docs/advanced/7_docker/as_flow2.png b/docs/advanced/7_docker/as_flow2.png
index 9059788e9..4b3d86533 100644
Binary files a/docs/advanced/7_docker/as_flow2.png and b/docs/advanced/7_docker/as_flow2.png differ
diff --git a/docs/advanced/7_docker/as_flow2.png.avif b/docs/advanced/7_docker/as_flow2.png.avif
deleted file mode 100644
index 8bb6277d6..000000000
Binary files a/docs/advanced/7_docker/as_flow2.png.avif and /dev/null differ
diff --git a/docs/advanced/7_docker/as_flow2.png.webp b/docs/advanced/7_docker/as_flow2.png.webp
deleted file mode 100644
index fc7cae0d7..000000000
Binary files a/docs/advanced/7_docker/as_flow2.png.webp and /dev/null differ
diff --git a/docs/advanced/7_docker/as_script.png b/docs/advanced/7_docker/as_script.png
index f9f35395c..8182c2b17 100644
Binary files a/docs/advanced/7_docker/as_script.png and b/docs/advanced/7_docker/as_script.png differ
diff --git a/docs/advanced/7_docker/as_script.png.avif b/docs/advanced/7_docker/as_script.png.avif
deleted file mode 100644
index 6eab4d838..000000000
Binary files a/docs/advanced/7_docker/as_script.png.avif and /dev/null differ
diff --git a/docs/advanced/7_docker/as_script.png.webp b/docs/advanced/7_docker/as_script.png.webp
deleted file mode 100644
index c2757ae37..000000000
Binary files a/docs/advanced/7_docker/as_script.png.webp and /dev/null differ
diff --git a/docs/advanced/7_docker/as_script2.png b/docs/advanced/7_docker/as_script2.png
index 58c5e657a..a41f9e373 100644
Binary files a/docs/advanced/7_docker/as_script2.png and b/docs/advanced/7_docker/as_script2.png differ
diff --git a/docs/advanced/7_docker/as_script2.png.avif b/docs/advanced/7_docker/as_script2.png.avif
deleted file mode 100644
index 6ff8e3bf3..000000000
Binary files a/docs/advanced/7_docker/as_script2.png.avif and /dev/null differ
diff --git a/docs/advanced/7_docker/as_script2.png.webp b/docs/advanced/7_docker/as_script2.png.webp
deleted file mode 100644
index 1870db95a..000000000
Binary files a/docs/advanced/7_docker/as_script2.png.webp and /dev/null differ
diff --git a/docs/advanced/7_docker/index.md b/docs/advanced/7_docker/index.mdx
similarity index 78%
rename from docs/advanced/7_docker/index.md
rename to docs/advanced/7_docker/index.mdx
index a33e0ba87..a80b7ec7b 100644
--- a/docs/advanced/7_docker/index.md
+++ b/docs/advanced/7_docker/index.mdx
@@ -1,12 +1,24 @@
+import DocCard from '@site/src/components/DocCard';
+
 # Run Docker Containers
 
-Windmill support running any docker container through its bash support. As a pre-requisite, the host docker daemon need to be mounted into the worker container. This is done through a simple volume mount: `/var/run/docker.sock:/var/run/docker.sock`.
+Windmill supports running any [Docker](https://www.docker.com/) container through its [Bash](../../getting_started/0_scripts_quickstart/4_bash_quickstart/index.mdx) support. As a pre-requisite, the host docker daemon needs to be mounted into the worker container. This is done through a simple volume mount: `/var/run/docker.sock:/var/run/docker.sock`.
+
+Once Docker is set up, see:
+
+<div class="grid grid-cols-2 gap-6 mb-4">
+	<DocCard
+		title="Docker Quickstart"
+		description="Learn to run a script using from Docker containers."
+		href="/docs/getting_started/scripts_quickstart/docker"
+	/>
+</div>
 
 ## Setup
 
 ### Docker compose
 
-On the docker-compose, it is enough to uncomment the volume mount of the windmill worker
+On the docker-compose, it is enough to uncomment the volume mount of the Windmill worker
 
 ```dockerfile
       # mount the docker socket to allow to run docker containers from within the workers
@@ -15,7 +27,7 @@ On the docker-compose, it is enough to uncomment the volume mount of the windmil
 
 ### Helm charts
 
-In the charts values of our [helm charts](https://github.com/windmill-labs/windmill-helm-charts), set `windmill.exposeHostDocker` to `true`
+In the charts values of our [helm charts](https://github.com/windmill-labs/windmill-helm-charts), set `windmill.exposeHostDocker` to `true`.
 
 ### Remote Docker Daemon
 
@@ -39,7 +51,6 @@ spec:
       privileged: true
 ```
 
-
 ## Use
 
 The default code is as follows:
@@ -70,15 +81,15 @@ Like any bash script, it will return the last line of the stdout. So be sure to
 
 As a script:
 
-![script 1](./as_script.png.webp)
+![script 1](./as_script.png)
 
-![script 2](./as_script2.png.webp)
+![script 2](./as_script2.png)
 
 As a flow step:
 
-![flow step 1](./as_flow.png.webp)
+![flow step 1](./as_flow.png)
 
-![flow step 2](./as_flow2.png.webp)
+![flow step 2](./as_flow2.png)
 
 ## Use with Remote Docker Daemon
 
diff --git a/docs/advanced/index.md b/docs/advanced/index.md
index a78661c3a..a9b07f3f6 100644
--- a/docs/advanced/index.md
+++ b/docs/advanced/index.md
@@ -14,6 +14,6 @@ Windmill's most advanced guides.
   </a>
   <a href="/docs/advanced/docker" class="rounded-md p-6 border border-gray-200 hover:border-blue-500 transition-all cursor-pointer flex flex-col gap-2 !no-underline" >
    <div class="text-lg font-semibold text-gray-900">Run Docker Containers</div>
-    <div class="text-sm text-gray-500">Windmill support running any docker container through its bash support.</div>
+    <div class="text-sm text-gray-500">Windmill supports running any docker container through its Bash support.</div>
   </a>
 </div>
diff --git a/docs/apps/0_app_editor/index.mdx b/docs/apps/0_app_editor/index.mdx
index d4ea42b64..2ecb06f68 100644
--- a/docs/apps/0_app_editor/index.mdx
+++ b/docs/apps/0_app_editor/index.mdx
@@ -21,13 +21,14 @@ The app editor is a low-code builder to create apps with components, create inte
 
 <br />
 
-The app editor is composed of 5 main sections:
+The app editor is composed of 6 main sections:
 
 1. [Toolbar](/docs/apps/app_editor#toolbar)
 2. [Canvas](#canvas)
 3. [Outputs](#outputs)
 4. [Runnables panel](#runnables-panel)
 5. [Component Library and Settings](#component-library-and-settings)
+6. [App Styling]
 
 ![App Editor](../../assets/apps/0_app_editor/plain-app-editor.png.webp)
 
@@ -35,7 +36,7 @@ The app editor is composed of 5 main sections:
 
 The topbar helps you in your app editing.
 
-![App Menu](../../assets/apps/1_app_toolbar/app-toolbar.png.webp)
+![App Menu](../../assets/apps/1_app_toolbar/app-toolbar.png)
 
 #### Learn more
 
@@ -79,7 +80,7 @@ The canvas at the center of the editor is where you design and see the overall U
 
 ## Outputs
 
-On the left panel of the editor, you can see the list of outputs of the app. These outputs represent the state of the app and are categorized into four types:
+On the left panel of the editor, you can see the list of outputs of the app. These outputs represent the states & results of the app and are categorized into four types:
 
 - **Context**: The context holds information such as the user email, username, workspace, query parameters, and more.
 - **State**: The state holds the app's current state, which can be manipulated by the frontend scripts.
@@ -100,8 +101,8 @@ You can perform the following actions with the outputs:
 <div class="grid grid-cols-2 gap-6 mb-4">
 	<DocCard
 		color="orange"
-		title="Context"
-		description="The context holds such information as the user email, username, the workspace, the query parameters, etc."
+		title="Outputs"
+		description="The outputs represent the states & results of the app"
 		href="/docs/apps/outputs"
 	/>
 	<DocCard
@@ -152,6 +153,26 @@ Finally, on the right panel of the editor, you can insert a new component, confi
 		description="Learn how to trigger a runnable."
 		href="/docs/apps/app_configuration-settings/app_runnable_triggers"
 	/>
+</div>
+
+## Styling
+
+Styling on the app editor can be managed at the component and app-level, with pre-set configurations or using CSS & [Tailwind](https://tailwindcss.com/).
+
+#### Learn more
+
+<div class="grid grid-cols-2 gap-2 my-4">
+	<DocCard
+		color="orange"
+		title="Styling"
+		description="Learn how to edit the component styles."
+		href="/docs/apps/app_configuration-settings/app_styling"
+	/>
+</div>
+
+## Other app features
+
+<div class="grid grid-cols-2 gap-2 my-4">
 	<DocCard
 		title="Group of Components"
 		description="Components can be grouped within containers."
@@ -159,9 +180,9 @@ Finally, on the right panel of the editor, you can insert a new component, confi
 		color="orange"
 	/>
 	<DocCard
+		title="Public Apps"
+		description="Apps can be accessed as a standalone app by anyone who has the secret URL"
+		href="/docs/apps/public_apps"
 		color="orange"
-		title="Styling"
-		description="Learn how to edit the component styles."
-		href="/docs/apps/app_configuration-settings/app_styling"
 	/>
-</div>
+</div>
\ No newline at end of file
diff --git a/docs/apps/0_toolbar.md b/docs/apps/0_toolbar.md
index de5bba2d9..d5fd397c3 100644
--- a/docs/apps/0_toolbar.md
+++ b/docs/apps/0_toolbar.md
@@ -1,21 +1,8 @@
 # Toolbar Guide
 
-The app toolbar is located at the top of the app editor. It enables you to adjust app settings, toggle between desktop/mobile preview, and debug runs.
-
-![App Menu](../assets/apps/1_app_toolbar/app-toolbar.png.webp)
-
-- [App Summary](#app-summary): The summary is the name that will be displayed for your app.
-- [Undo/Redo](#app-summary): Perform undo or redo actions.
-- [Desktop/Mobile Mode](#desktopmobile-mode): Switch between Mobile and Desktop layout.
-- [Width](#width): Switch between full and max width.
-- [Deployement history](#deployement-history): View the deployment history of the app.
-- [JSON](#json): Export your app as a JSON or [Hub](https://hub.windmill.dev/) compatible file.
-- [Hub compatible JSON](#hub-compatible-json): View the JSON representation of the app in a format that is compatible with the [Windmill Hub](https://hub.windmill.dev/).
-- [App Inputs Configuration](#app-inputs-configuration): the app inputs menu displays a list of all the inputs of each component.
-- [Debugging](#debug-runs): Open the debugging panel.
-- [Editor/Preview Mode](#preview-mode): Toggle between the Editor and Preview modes.
-- [Save as Draft](#save-as-draft): Save your app as a [draft](../core_concepts/0_draft_and_deploy/index.mdx#draft).
-- [Deploy](#deploy): [Deploy](../core_concepts/0_draft_and_deploy/index.mdx#deployed-version) your app.
+The app toolbar is located at the top of the app editor. It enables you to adjust app settings.
+
+![App Menu](../assets/apps/1_app_toolbar/app-toolbar.png)
 
 ## App Summary
 
@@ -41,19 +28,19 @@ The `⋮` menu provides access to the following options:
 
 ### Deployement history
 
-In the menu, you can view the deployment history of the app. It displays the date and time of the deployment, the user who deployed the app, and the version of the app.
+In the menu, you can view the [deployment](./6_app_deployment.mdx) history of the app. It displays the date and time of the deployment, the user who deployed the app, and the version of the app.
 
 You can:
 
 - View the app at a specific version.
-- Restore a fork
-- Restore here
+- Restore a fork.
+- Restore here.
 
 ![Deployement history](../assets/apps/1_app_toolbar/deployement-history.png.webp)
 
 ### JSON
 
-View the JSON representation of the app.
+View the [JSON representation](../core_concepts/13_json_schema_and_parsing/index.md) of the app.
 
 ### Hub compatible JSON
 
@@ -67,7 +54,7 @@ The app inputs menu displays a list of all the inputs of each component. A toggl
 
 ## Debug Runs
 
-The app builder enables you to examine recent runs to identify potential bugs.
+The app builder enables you to examine recent runs to [identify potential bugs](./5_app_debugging.md).
 
 ![App Debug Runs](../assets/apps/1_app_toolbar/app-debug-runs.png.webp)
 
@@ -77,13 +64,12 @@ The app editor mode can be toggled between `Editor` and `Preview` modes. The pre
 
 ## Save as draft
 
-You can [save](../core_concepts/0_draft_and_deploy/index.mdx) the app. The first time you save the app, you'll be asked to select the owner of the app. You can choose either a user or a [folder](../core_concepts/8_groups_and_folders/index.mdx#folders).
+You can [save](./6_app_deployment.mdx) the app. The first time you save the app, you'll be asked to select the owner of the app. You can choose either a user or a [folder](../core_concepts/8_groups_and_folders/index.mdx#folders).
 
 ## Deploy
 
-You can [deploy](../core_concepts/0_draft_and_deploy/index.mdx#deployed-version) the app as a standalone app via a URL. There are two ways to publish an app:
-
-- Read-Access Required: The app can be accessed by anyone who has read access to the app.
-- Publish Publicly: The app can be accessed by anyone who knows the secret URL. If set to `Publish Publicly`, the secret URL will be displayed here.
+Windmill apps are custom-made user interfaces meant to interact with scripts and flows.
 
-![App Publish](../assets/apps/1_app_toolbar/app-publish.png.webp)
\ No newline at end of file
+There are two ways to [deploy](./6_app_deployment.mdx) an app:
+- **Read-Access Required**: The app can be accessed & triggered by anyone who has [read access](../core_concepts/16_roles_and_permissions/index.mdx) to the app.
+- **Publish Publicly**: The app can be accessed as a standalone app by anyone who has the secret URL.
\ No newline at end of file
diff --git a/docs/apps/2_outputs.md b/docs/apps/2_outputs.md
index 16cccf258..ebf103ad2 100644
--- a/docs/apps/2_outputs.md
+++ b/docs/apps/2_outputs.md
@@ -1,6 +1,8 @@
 # Outputs Guide
 
-On the left-hand side of the app editor, you can find the app outputs. They are three kind of outputs:
+The outputs represent the states & results of the app.
+
+All outputs can be found on the left-hand side of the app editor. There are three kind of outputs:
 
 - Context and state
 - Component outputs
diff --git a/docs/apps/6_app_deployment.mdx b/docs/apps/6_app_deployment.mdx
index b7f25f9b2..73fb45e74 100644
--- a/docs/apps/6_app_deployment.mdx
+++ b/docs/apps/6_app_deployment.mdx
@@ -2,16 +2,27 @@ import DocCard from '@site/src/components/DocCard';
 
 # Deployment
 
-Apps can be saved as draft before being published.
+Windmill apps are custom-made user interfaces meant to interact with scripts and flows.
+
+There are two ways to [deploy](../core_concepts/0_draft_and_deploy/index.mdx) an app:
+- **Read-Access Required**: The app can be accessed & triggered by anyone who has [read access](../core_concepts/16_roles_and_permissions/index.mdx) to the app.
+- **Publish Publicly**: The app can be accessed as a standalone app by anyone who has the secret URL.
+
+Apps can be saved as [draft](../core_concepts/0_draft_and_deploy/index.mdx#draft) before being published.
 
 ### Learn more
 
 <div class="grid grid-cols-2 gap-6 mb-4">
-
 <DocCard
 	title="Draft and Deploy"
 	description="Learn how to draft and deploy apps."
 	href="/docs/core_concepts/draft_and_deploy"
 	color="orange"
 />
+<DocCard
+	title="Public Apps"
+	description="Apps can be accessed as a standalone app by anyone who has the secret URL"
+	href="/docs/apps/public_apps"
+	color="orange"
+/>
 </div>
diff --git a/docs/apps/8_public_apps.md b/docs/apps/8_public_apps.md
new file mode 100644
index 000000000..24c0a7651
--- /dev/null
+++ b/docs/apps/8_public_apps.md
@@ -0,0 +1,12 @@
+# Public Apps
+
+Windmill apps are custom-made user interfaces meant to interact with scripts and flows.
+
+There are two ways to [deploy](./6_app_deployment.mdx) an app:
+- **Read-Access Required**: The app can be accessed & triggered by anyone who has [read access](../core_concepts/16_roles_and_permissions/index.mdx) to the app.
+- **Publish Publicly**: The app can be accessed as a standalone app by anyone who has the secret URL.
+This feature requires saving the app at least to [draft](../core_concepts/0_draft_and_deploy/index.mdx#draft) before.
+
+![Read-Access App](../assets/apps/8_public_apps/read_only_app.png "Read-Access App")
+
+![Public App](../assets/apps/8_public_apps/public_app.png "Public App")
\ No newline at end of file
diff --git a/docs/assets/apps/1_app_toolbar/app-publish.png b/docs/assets/apps/1_app_toolbar/app-publish.png
deleted file mode 100644
index 3a773a23d..000000000
Binary files a/docs/assets/apps/1_app_toolbar/app-publish.png and /dev/null differ
diff --git a/docs/assets/apps/1_app_toolbar/app-publish.png.avif b/docs/assets/apps/1_app_toolbar/app-publish.png.avif
deleted file mode 100644
index 575e71223..000000000
Binary files a/docs/assets/apps/1_app_toolbar/app-publish.png.avif and /dev/null differ
diff --git a/docs/assets/apps/1_app_toolbar/app-publish.png.webp b/docs/assets/apps/1_app_toolbar/app-publish.png.webp
deleted file mode 100644
index fde9c81c4..000000000
Binary files a/docs/assets/apps/1_app_toolbar/app-publish.png.webp and /dev/null differ
diff --git a/docs/assets/apps/1_app_toolbar/app-toolbar.png b/docs/assets/apps/1_app_toolbar/app-toolbar.png
index e67bb1bc2..350ea1bd0 100644
Binary files a/docs/assets/apps/1_app_toolbar/app-toolbar.png and b/docs/assets/apps/1_app_toolbar/app-toolbar.png differ
diff --git a/docs/assets/apps/1_app_toolbar/app-toolbar.png.avif b/docs/assets/apps/1_app_toolbar/app-toolbar.png.avif
deleted file mode 100644
index 3f0102df3..000000000
Binary files a/docs/assets/apps/1_app_toolbar/app-toolbar.png.avif and /dev/null differ
diff --git a/docs/assets/apps/1_app_toolbar/app-toolbar.png.webp b/docs/assets/apps/1_app_toolbar/app-toolbar.png.webp
deleted file mode 100644
index c33d7ddfc..000000000
Binary files a/docs/assets/apps/1_app_toolbar/app-toolbar.png.webp and /dev/null differ
diff --git a/docs/assets/apps/8_public_apps/public_app.png b/docs/assets/apps/8_public_apps/public_app.png
new file mode 100644
index 000000000..ee0a0fb4e
Binary files /dev/null and b/docs/assets/apps/8_public_apps/public_app.png differ
diff --git a/docs/assets/apps/8_public_apps/read_only_app.png b/docs/assets/apps/8_public_apps/read_only_app.png
new file mode 100644
index 000000000..3fecd49e3
Binary files /dev/null and b/docs/assets/apps/8_public_apps/read_only_app.png differ
diff --git a/docs/compared_to/retool.mdx b/docs/compared_to/retool.mdx
index eaeb503c9..f30177aad 100644
--- a/docs/compared_to/retool.mdx
+++ b/docs/compared_to/retool.mdx
@@ -78,7 +78,7 @@ However, the possibilities with code on Retool will be much more limited:
 
 Retool only supports JavaScript and SQL. Windmill supports JavaScript ([TypeScript](../getting_started/0_scripts_quickstart/1_typescript_quickstart/index.mdx)), [SQL](../getting_started/0_scripts_quickstart/5_sql_quickstart/index.mdx), but also [Python](../getting_started/0_scripts_quickstart/2_python_quickstart/index.mdx), [Go](../getting_started/0_scripts_quickstart/3_go_quickstart/index.mdx), [Bash](../getting_started/0_scripts_quickstart/4_bash_quickstart/index.mdx).
 For each of those languages, scripts can be run [without having to deal with separate dependency files](../advanced/6_imports/index.md).
-For other languages, Windmill supports [running any docker container](../advanced/7_docker/index.md) through its bash support.
+For other languages, Windmill supports [running any docker container](../advanced/7_docker/index.mdx) through its bash support.
 
 All operations in Windmill are based on scripts. Unlike Retool, scripts in Windmill can be considered as standalone endpoints:
 executable through [autogenerated UIs](../core_concepts/6_auto_generated_uis/index.md), [webhooks](../core_concepts/4_webhooks/index.md), etc.
diff --git a/docs/core_concepts/0_draft_and_deploy/index.mdx b/docs/core_concepts/0_draft_and_deploy/index.mdx
index 5acdad624..100b68f7a 100644
--- a/docs/core_concepts/0_draft_and_deploy/index.mdx
+++ b/docs/core_concepts/0_draft_and_deploy/index.mdx
@@ -6,6 +6,8 @@ Draft, test, and deploy scripts, flows, and apps Windmill to iterate and save sa
 
 Each script, flow or app can be saved (sometimes concurrently) in 3 fashions, by your browser in `local storage`, by the backend as a `draft`, and `deployed`.
 
+Once deployed, scripts, flows and apps will be visible, editable and/or runnable by users [with the right permissions](../16_roles_and_permissions/index.mdx).
+
 <video
 	className="border-2 rounded-xl object-cover w-full h-full dark:border-gray-800"
 	autoPlay
@@ -36,22 +38,16 @@ Drafts can be run and tested only from the editor (script, flow or app) with the
 
 ## Deployed Version
 
-The deployed version is the authoritative version of a runnable. Once deployed, it is not only visible by workspace members but has its own [auto-generated UI](../6_auto_generated_uis/index.md), [webhooks](../4_webhooks/index.md), or can be called from flows and apps (for sripts and flows). This also means that local edits and drafts can be made in parallel to a deployed version of a runnable without affecting its behavior.
+The deployed version is the authoritative version of a runnable. Once deployed, it is not only visible by workspace members [with the right permissions](../16_roles_and_permissions/index.mdx) but has its own [auto-generated UI](../6_auto_generated_uis/index.md), [webhooks](../4_webhooks/index.md), or can be called from flows and apps (for sripts and flows). This also means that local edits and drafts can be made in parallel to a deployed version of a runnable without affecting its behavior.
 
 If you want to have several versions of the same runnable, just fork it with the `Fork` button on the drop down menu of `Deploy`.
 
-## Special case: Deployed versions of scripts
-
-Apps and Flows only have one deployed version at a given path and doing a new deployment overwrite the previous one.
-
-Scripts are special because each deployment of a script creates an immutable hash that will never be overwritten. The path of a script serves as a redirection to the last deployed hash, but all hashes live permanently forever. This ensures that if you refer to a script by its hash, its behavior is guaranteed to remain the same even if a new hash is deployed at the same path.
-
 <div class="grid grid-cols-2 gap-6 mb-4">
 	<DocCard
-		title="Versioning"
-		description="Scripts, when deployed, can have a parent script identified by its hash."
-		href="/docs/script_editor/versioning"
-	/>
+    	title="Roles and Permissions"
+    	description="Control access and manage permissions within your instance and workspaces."
+    	href="/docs/core_concepts/roles_and_permissions"
+    />
 </div>
 
 ## Diff Viewer
@@ -68,6 +64,32 @@ A diff viewer is available when loading scripts from autosave or draft.
 
 > Changes can then be reversed to previous version.
 
+## Special case: Deployed versions of scripts
+
+Apps and Flows only have one deployed version at a given path and doing a new deployment overwrite the previous one.
+
+Scripts are special because each deployment of a script creates an immutable hash that will never be overwritten. The path of a script serves as a redirection to the last deployed hash, but all hashes live permanently forever. This ensures that if you refer to a script by its hash, its behavior is guaranteed to remain the same even if a new hash is deployed at the same path.
+
+<div class="grid grid-cols-2 gap-6 mb-4">
+	<DocCard
+		title="Versioning"
+		description="Scripts, when deployed, can have a parent script identified by its hash."
+		href="/docs/script_editor/versioning"
+	/>
+</div>
+
+## Special case: Public Apps
+
+Windmill apps can be [Published Publicly](../../apps/8_public_apps.md). It means that the app can be accessed as a standalone app by anyone who has the secret URL.
+
+<div class="grid grid-cols-2 gap-6 mb-4">
+	<DocCard
+		title="Public Apps"
+		description="Apps can be accessed as a standalone app by anyone who has the secret URL"
+		href="/docs/apps/public_apps"
+	/>
+</div>
+
 ## Recap
 
 ![Recap Draft and Deploy](./recap_draft_and_deploy.png.webp)
diff --git a/docs/core_concepts/25_dedicated_workers/index.mdx b/docs/core_concepts/25_dedicated_workers/index.mdx
index bd6dcbdb2..9bcb53d58 100644
--- a/docs/core_concepts/25_dedicated_workers/index.mdx
+++ b/docs/core_concepts/25_dedicated_workers/index.mdx
@@ -9,26 +9,24 @@ For now it only work with bun scripts that have been pre-deployed.
 
 The scripts can be used within flows.
 
-To setup, pass:
+To use:
 
-```
-DEDICATED_WORKER=<workspace>:<path>
-```
+1. Assign one worker group to execute that script
 
-to the dedicated worker that will be tasked with executing that script.
+![Worker group config](./worker_group_config.png)
 
-or use the dedicatedWorkers section in the values.yaml of the helm chart.
+The worker group will restart (assuming the pods/restart are set to restart automatically) and will now wait for step 2. below to happen
 
-You will also need to toggle the "Dedicated Workers" option for that script in the metadata:
+2. toggle the "Dedicated Workers" option for that script in the metadata:
 
 ![Dedicated Workers](./dedicated_workers.png)
 
 You might also want to look for [Worker Group Tag](../9_worker_groups/index.mdx), which allows to assign custom worker groups to scripts and flows in Windmill for efficient execution on different machines with varying specifications:
 
 <div class="grid grid-cols-2 gap-6 mb-4">
-    <DocCard
-    	title="Workers and Worker Groups"
-    	description="Worker Groups allow users to run scripts and flows on different machines with varying specifications."
-    	href="/docs/core_concepts/worker_groups"
-    />
-</div>
\ No newline at end of file
+	<DocCard
+		title="Workers and Worker Groups"
+		description="Worker Groups allow users to run scripts and flows on different machines with varying specifications."
+		href="/docs/core_concepts/worker_groups"
+	/>
+</div>
diff --git a/docs/core_concepts/25_dedicated_workers/worker_group_config.png b/docs/core_concepts/25_dedicated_workers/worker_group_config.png
new file mode 100644
index 000000000..07aa6f039
Binary files /dev/null and b/docs/core_concepts/25_dedicated_workers/worker_group_config.png differ
diff --git a/docs/core_concepts/9_worker_groups/index.mdx b/docs/core_concepts/9_worker_groups/index.mdx
index 3ccfab95d..6e317022f 100644
--- a/docs/core_concepts/9_worker_groups/index.mdx
+++ b/docs/core_concepts/9_worker_groups/index.mdx
@@ -36,31 +36,41 @@ Workers can belong to multiple worker groups simultaneously. The default worker
 
 If you assign custom worker groups to all your workers, make sure that they cover all worker groups above, otherwise those jobs will never be executed.
 
-You can customize the worker group of a worker by setting the WORKER_TAGS environment variable.
+To make custom tags available from the UI, go to your workspace settings and click on the "Assignable Tags" button:
+
+![Worker Group Assignable Tags](./worker_group_ui_2.png)
+
+It is possible to restrict some tags to specific workspace using the following syntax:
 
 ```
-WORKER_TAGS=deno,light,gpu
+gpu(workspace+workspace2)
 ```
 
-By default, the `WORKER_TAGS` of workers include `deno, python3, bash, go, flow, hub, dependency`.
+Only 'workspace' and 'workspace2' will be able to use the `gpu` tags.
 
-The configuration above will make the workers accept only deno jobs and jobs with the `light` tag.
+## How to have a worker join a worker group
 
-To make custom tags available from the UI and be authorized to be used, you need to pass the following env variable to the Windmill server:
+Simply pass the worker group as the env variable `WORKER_GROUP`:
 
 ```
-CUSTOM_TAGS=light,gpu
+WORKER_GROUP=worker_group_name
 ```
 
-You can restrict some tags to specific workspace using the following syntax:
+The worker will automatically join the worker group on start and be displayed on the Workers page.
+
+## How to assign worker tags to a worker group
+
+Use the edit/create config next to the worker group name in windmill UI:
+
+![Worker Group edit config](./worker_group_ui.png)
+
+**Note**: The worker group management UI is an enterprise only feature. It is still possible to use worker groups with the community edition by passing to each worker the env variable `WORKER_TAGS`:
 
 ```
-CUSTOM_TAGS=light,gpu(workspace+workspace2)
+WORKER_TAGS=tag1,tag2
 ```
 
-Only workspace and workspace2 will be able to use the `gpu` tags.
-
-## How to assign a custom worker group
+## How to assign a custom worker group to a script or flow
 
 For scripts saved on the script editor, select the corresponding worker group tag in the metadata section.
 
@@ -80,10 +90,10 @@ You can assign a worker group to an entire flow in the flow's settings:
 
 If a workspace tag contains the substring `$workspace`, it will be replaced by the workspace id corresponding to the job. This is especially useful to have the same script deployed to different workspace and have them run on different workers.
 
-In the following setup:
+With the following assignable tag:
 
 ```
-CUSTOM_TAGS=normal-$workspace
+normal-$workspace
 ```
 
 the workspaces, `dev`, `staging`, `prod` and the worker groups: `normal-dev`, `normal-staging`, `normal-prod`. The same script wih the tag `normal-$workspace` will run on the corresponding worker group depending on the workspace it is deployed to. This enable to share the same control plane but use workers with different network restrictions for tighter security.
@@ -98,9 +108,9 @@ They are as fast as running the same logic in a forloop, but keep the benefit of
 Dedicated Workers / Native Performance is an [Enterprise & Team Edition](../../misc/7_plans_details/index.mdx) feature.
 
 <div class="grid grid-cols-2 gap-6 mb-4">
-    <DocCard
-    	title="Dedicated Workers / Native Performance"
-    	description="Dedicated Workers are workers that are dedicated to a particular script."
-    	href="/docs/core_concepts/dedicated_workers"
-    />
-</div>
\ No newline at end of file
+	<DocCard
+		title="Dedicated Workers / Native Performance"
+		description="Dedicated Workers are workers that are dedicated to a particular script."
+		href="/docs/core_concepts/dedicated_workers"
+	/>
+</div>
diff --git a/docs/core_concepts/9_worker_groups/worker_group_ui.png b/docs/core_concepts/9_worker_groups/worker_group_ui.png
new file mode 100644
index 000000000..717483948
Binary files /dev/null and b/docs/core_concepts/9_worker_groups/worker_group_ui.png differ
diff --git a/docs/core_concepts/9_worker_groups/worker_group_ui_2.png b/docs/core_concepts/9_worker_groups/worker_group_ui_2.png
new file mode 100644
index 000000000..738af4195
Binary files /dev/null and b/docs/core_concepts/9_worker_groups/worker_group_ui_2.png differ
diff --git a/docs/core_concepts/index.mdx b/docs/core_concepts/index.mdx
index 74a541671..b5dfccd80 100644
--- a/docs/core_concepts/index.mdx
+++ b/docs/core_concepts/index.mdx
@@ -322,8 +322,9 @@ All details on Apps can be found in the [Apps section](../apps/0_app_editor/inde
 		color="orange"
 	/>
 	<DocCard
-		title="Example: E-commerce CRM app"
-		description="Tutorial on how to build a CRM with Windmill."
+		title="Public Apps"
+		description="Apps can be accessed as a standalone app by anyone who has the secret URL"
+		href="/docs/apps/public_apps"
 		color="orange"
 	/>
 </div>
diff --git a/docs/flows/16_architecture.mdx b/docs/flows/16_architecture.mdx
index e88640e9a..5ac126ffe 100644
--- a/docs/flows/16_architecture.mdx
+++ b/docs/flows/16_architecture.mdx
@@ -6,7 +6,7 @@ In Windmill, a workflow is a JSON serializable value in the [OpenFlow](../openfl
 
 1. Reference to a Script from the [Hub](https://hub.windmill.dev/).
 2. Reference to a Script in your [workspace](../core_concepts/16_roles_and_permissions/index.mdx#workspace).
-3. Inlined Script in [TypeScript](../getting_started/0_scripts_quickstart/1_typescript_quickstart/index.mdx) (Deno), [Python](../getting_started/0_scripts_quickstart/2_python_quickstart/index.mdx), [Go](../getting_started/0_scripts_quickstart/3_go_quickstart/index.mdx), [Bash](../getting_started/0_scripts_quickstart/3_go_quickstart/index.mdx), [SQL](../getting_started/0_scripts_quickstart/5_sql_quickstart/index.mdx) or [non-supported languages](../advanced/7_docker/index.md).
+3. Inlined Script in [TypeScript](../getting_started/0_scripts_quickstart/1_typescript_quickstart/index.mdx) (Deno), [Python](../getting_started/0_scripts_quickstart/2_python_quickstart/index.mdx), [Go](../getting_started/0_scripts_quickstart/3_go_quickstart/index.mdx), [Bash](../getting_started/0_scripts_quickstart/3_go_quickstart/index.mdx), [SQL](../getting_started/0_scripts_quickstart/5_sql_quickstart/index.mdx) or [non-supported languages](../advanced/7_docker/index.mdx).
 4. [Trigger Scripts](./10_flow_trigger.md) which are a kind of Scripts that are meant to be first step of a scheduled Flow, that watch for external events and early exit the Flow if there is no new events.
 5. [For loop](./12_flow_loops.md) that iterates over elements and triggers the execution of an embedded flow for each element. The list is calculated dynamically as an [input transform](#input-transform).
 6. [Branch](./13_flow_branches.md#branch-one) to the first subflow that has a truthy predicate (evaluated in-order).
diff --git a/docs/flows/3_editor_components.mdx b/docs/flows/3_editor_components.mdx
index d7994b32e..89c001f9e 100644
--- a/docs/flows/3_editor_components.mdx
+++ b/docs/flows/3_editor_components.mdx
@@ -284,7 +284,7 @@ You can either create a new action script in:
 - [Typescript](/docs/getting_started/scripts_quickstart/typescript): Windmill uses Deno as the TypeScript runtime.
 - [Go](/docs/getting_started/scripts_quickstart/go).
 - [Bash](/docs/getting_started/scripts_quickstart/bash).
-- Any language [running any docker container](../advanced/7_docker/index.md) through Windmill's bash support.
+- Any language [running any docker container](../advanced/7_docker/index.mdx) through Windmill's bash support.
 
 There are special kinds of scripts:
 
diff --git a/docs/getting_started/00_how_to_use_windmill/index.mdx b/docs/getting_started/00_how_to_use_windmill/index.mdx
index 778e659a0..7c2e746eb 100644
--- a/docs/getting_started/00_how_to_use_windmill/index.mdx
+++ b/docs/getting_started/00_how_to_use_windmill/index.mdx
@@ -2,6 +2,10 @@ import DocCard from '@site/src/components/DocCard';
 
 # Get Started with Windmill
 
+Windmill is an [open-source](https://github.com/windmill-labs/windmill) platform to build all your internal tools (endpoints, workflows, UIs) through the combination of code (in Typescript, Python, Go, Bash, SQL or any docker image) and low code builders.
+
+Windmill can be self-hosted or used on a cloud version.
+
 ### Self-Host Windmill
 
 You can choose to self-host Windmill on your own infra.
diff --git a/docs/getting_started/0_scripts_quickstart/1_typescript_quickstart/index.mdx b/docs/getting_started/0_scripts_quickstart/1_typescript_quickstart/index.mdx
index 91371f070..26f6fc2c9 100644
--- a/docs/getting_started/0_scripts_quickstart/1_typescript_quickstart/index.mdx
+++ b/docs/getting_started/0_scripts_quickstart/1_typescript_quickstart/index.mdx
@@ -36,7 +36,7 @@ Scripts are the basic building blocks in Windmill. They can be [run and schedule
 
 Scripts consist of 2 parts:
 
-- [Code](#code): for typescript scripts, it must have at least a main function.
+- [Code](#code): for TypeScript scripts, it must have at least a main function.
 - [Metadata](#metadata): metadata about the Script such as its path, summary, description, [jsonschema](../../../core_concepts/13_json_schema_and_parsing/index.md) of its inputs (inferred from its signature).
 
 When stored in a code repository, those 2 parts are stored separately at `<path>.ts` and `<path>.script.yaml`.
diff --git a/docs/getting_started/0_scripts_quickstart/2_python_quickstart/index.mdx b/docs/getting_started/0_scripts_quickstart/2_python_quickstart/index.mdx
index 263df2247..6c155e013 100644
--- a/docs/getting_started/0_scripts_quickstart/2_python_quickstart/index.mdx
+++ b/docs/getting_started/0_scripts_quickstart/2_python_quickstart/index.mdx
@@ -36,7 +36,7 @@ Scripts are the basic building blocks in Windmill. They can be [run and schedule
 
 Scripts consist of 2 parts:
 
-- [Code](#code): for typescript scripts, it must have at least a main function.
+- [Code](#code): for Python scripts, it must have at least a main function.
 - [Metadata](#metadata): metadata about the Script such as its path, summary, description, [jsonschema](../../../core_concepts/13_json_schema_and_parsing/index.md) of its inputs (inferred from its signature).
 
 When stored in a code repository, these 2 parts are stored separately at `<path>.ts` and `<path>.script.yaml`
diff --git a/docs/getting_started/0_scripts_quickstart/3_go_quickstart/index.mdx b/docs/getting_started/0_scripts_quickstart/3_go_quickstart/index.mdx
index f49e318a3..1f70e2e1e 100644
--- a/docs/getting_started/0_scripts_quickstart/3_go_quickstart/index.mdx
+++ b/docs/getting_started/0_scripts_quickstart/3_go_quickstart/index.mdx
@@ -36,7 +36,7 @@ Scripts are the basic building blocks in Windmill. They can be [run and schedule
 
 Scripts consist of 2 parts:
 
-- [Code](#code): for typescript scripts, it must have at least a main function.
+- [Code](#code): for Go scripts, it must have at least a main function.
 - [Metadata](#metadata): metadata about the Script such as its path, summary, description, [jsonschema](../../../core_concepts/13_json_schema_and_parsing/index.md) of its inputs (inferred from its signature).
 
 When stored in a code repository, those 2 parts are stored separately at `<path>.ts` and `<path>.script.yaml`.
diff --git a/docs/getting_started/0_scripts_quickstart/4_bash_quickstart/index.mdx b/docs/getting_started/0_scripts_quickstart/4_bash_quickstart/index.mdx
index a2f70a555..b6fde9022 100644
--- a/docs/getting_started/0_scripts_quickstart/4_bash_quickstart/index.mdx
+++ b/docs/getting_started/0_scripts_quickstart/4_bash_quickstart/index.mdx
@@ -38,7 +38,7 @@ Scripts are the basic building blocks in Windmill. They can be [run and schedule
 
 Scripts consist of 2 parts:
 
-- [Code](#code): for typescript scripts, it must have at least a main function.
+- [Code](#code).
 - [Metadata](#metadata): metadata about the Script such as its path, summary, description, [jsonschema](../../../core_concepts/13_json_schema_and_parsing/index.md) of its inputs (inferred from its signature).
 
 When stored in a code repository, those 2 parts are stored separately at `<path>.ts` and `<path>.script.yaml`.
@@ -263,10 +263,9 @@ You can also chose to [run the script from the CLI](../../../advanced/3_cli/inde
 
 ## Run Docker Containers
 
-
 In some cases where your task requires a complex set of dependencies or is implemented in a non-supported language, you can still include it as a flow step or individual script.
 
-Windmill support running any docker container through its bash support. As a pre-requisite, the host docker daemon need to be mounted into the worker container. This is done through a simple volume mount: `/var/run/docker.sock:/var/run/docker.sock`.
+Windmill supports running any docker container through its Bash support. As a pre-requisite, the host docker daemon needs to be mounted into the worker container. This is done through a simple volume mount: `/var/run/docker.sock:/var/run/docker.sock`.
 
 <div class="grid grid-cols-2 gap-6 mb-4">
 	<DocCard
diff --git a/docs/getting_started/0_scripts_quickstart/6_rest_grapqhql_quickstart/index.mdx b/docs/getting_started/0_scripts_quickstart/6_rest_grapqhql_quickstart/index.mdx
index ad89ee14a..bd163ef30 100644
--- a/docs/getting_started/0_scripts_quickstart/6_rest_grapqhql_quickstart/index.mdx
+++ b/docs/getting_started/0_scripts_quickstart/6_rest_grapqhql_quickstart/index.mdx
@@ -36,7 +36,7 @@ Scripts are the basic building blocks in Windmill. They can be [run and schedule
 
 Scripts consist of 2 parts:
 
-- [Code](#code): for typescript scripts, it must have at least a main function.
+- [Code](#code).
 - [Metadata](#metadata): metadata about the Script such as its path, summary, description, [jsonschema](../../../core_concepts/13_json_schema_and_parsing/index.md) of its inputs (inferred from its signature).
 
 When stored in a code repository, those 2 parts are stored separately at `<path>.ts` and `<path>.script.yaml`.
diff --git a/docs/getting_started/0_scripts_quickstart/7_docker_quickstart/index.mdx b/docs/getting_started/0_scripts_quickstart/7_docker_quickstart/index.mdx
new file mode 100644
index 000000000..9ac956222
--- /dev/null
+++ b/docs/getting_started/0_scripts_quickstart/7_docker_quickstart/index.mdx
@@ -0,0 +1,276 @@
+---
+title: Docker Quickstart
+slug: '/getting_started/scripts_quickstart/docker'
+---
+
+import DocCard from '@site/src/components/DocCard';
+
+# Docker Quickstart
+
+In this quick start guide, we will write our first script ran from a [Docker](https://www.docker.com/) container.
+
+Windmill natively supports Python, Typescript, Go, Bash or SQL.
+In some cases where your task requires a complex set of dependencies or is implemented in a non-supported language, Windmill allows running any Docker container through its [Bash](../4_bash_quickstart/index.mdx) support.
+
+As a pre-requisite, the host docker daemon needs to be mounted into the worker container. This is done through a simple volume mount: `/var/run/docker.sock:/var/run/docker.sock`.
+
+![script 1](../../../advanced/7_docker/as_script.png)
+
+<br />
+
+Scripts are the basic building blocks in Windmill. They can be [run and scheduled](../../8_trigger_scripts/index.mdx) as standalone, chained together to create [Flows](../../../flows/1_flow_editor.mdx) or displayed with a personalized User Interface as [Apps](../../7_apps_quickstart/index.mdx).
+
+<div class="grid grid-cols-2 gap-6 mb-4">
+	<DocCard
+		title="Script Editor"
+		description="All the details on scripts."
+		href="/docs/script_editor"
+	/>
+	<DocCard
+		title="Triggering Scripts"
+		description="Trigger flows on-demand, by schedule or on external events."
+		href="/docs/getting_started/trigger_scripts"
+	/>
+</div>
+
+Scripts consist of 2 parts:
+
+- [Code](#code).
+- [Metadata](#metadata): metadata about the Script such as its path, summary, description, [jsonschema](../../../core_concepts/13_json_schema_and_parsing/index.md) of its inputs (inferred from its signature).
+
+When stored in a code repository, those 2 parts are stored separately at `<path>.ts` and `<path>.script.yaml`.
+
+Below is a simple example of a script built using Bash to run Docker containers from Windmill:
+
+```bash
+# shellcheck shell=bash
+# Bash script that calls docker as a client to the host daemon
+# See documentation: https://www.windmill.dev/docs/advanced/docker
+msg="${1:-world}"
+
+IMAGE="alpine:latest"
+COMMAND="/bin/echo Hello $msg"
+
+# ensure that the image is up-to-date
+docker pull $IMAGE
+docker run --rm $IMAGE $COMMAND
+```
+
+## Setup
+
+To set-up Docker, see:
+
+<div class="grid grid-cols-2 gap-6 mb-4">
+	<DocCard
+		title="Docker Set-Up"
+		description="Windmill supports running any Docker container through its Bash support."
+		href="/docs/advanced/docker"
+	/>
+</div>
+
+## Use
+
+From the Home page of Windmill App, click `+Script`. This will take you to the
+first step of script creation: Metadata.
+
+### Metadata
+
+![New script](../4_bash_quickstart/create_script_bash.png)
+
+Each script has metadata associated with it, enabling it to be defined and configured in depth.
+
+- **Path** is the Script's unique identifier that consist of the
+  [script's owner](../../../core_concepts/16_roles_and_permissions/index.mdx), and the script's name.
+  The owner can be either a user, or a group ([folder](../../../core_concepts/8_groups_and_folders/index.mdx#folders)).
+- **Summary** (optional) is a short, human-readable summary of the Script. It
+  will be displayed as a title across Windmill. If omitted, the UI will use the `path` by
+  default.
+- **Language** of the script.
+- **Description** is where you can give instructions through the [auto-generated UI](../../../core_concepts/6_auto_generated_uis/index.md)
+  to users on how to run your Script. It supports markdown.
+- **[Concurrency limits](../../../script_editor/concurrency_limit.mdx)** enable defining concurrency limits for scripts and inline scripts within flows to prevent exceeding the API Limit of the targeted API.
+- **[Worker group tag](../../../core_concepts/9_worker_groups/index.mdx)** to assign scripts to specific worker groups (such as nodes with GPU accelaration).
+
+<div class="grid grid-cols-2 gap-6 mb-4">
+	<DocCard
+		title="Metadata"
+		description="Each script has metadata associated with it, enabling it to be defined and configured in depth."
+		href="/docs/script_editor/metadata"
+	/>
+</div>
+
+Now click on the code editor on the left side.
+
+### Code
+
+Windmill provides an online editor to work on your Scripts. The left-side is
+the editor itself. The right-side [previews the UI](../../../core_concepts/6_auto_generated_uis/index.md) that Windmill will
+generate from the Script's signature - this will be visible to the users of the
+Script. You can easily preview that UI, provide input values, and [test your script](#instant-preview--testing) there.
+
+![Editor for Bash](../4_bash_quickstart/editor_bash.png)
+
+<div class="grid grid-cols-2 gap-6 mb-4">
+	<DocCard
+		title="Code Editor"
+		description="The code editor is Windmill's integrated development environment."
+		href="/docs/code_editor"
+	/>
+	<DocCard
+		title="Auto-generated UIs"
+		description="Windmill creates auto-generated user interfaces for scripts and flows based on their parameters."
+		href="/docs/core_concepts/auto_generated_uis"
+	/>
+</div>
+
+As we picked `Docker` for this example, Windmill provided some Bash
+boilerplate. Let's take a look:
+
+```bash
+# shellcheck shell=bash
+# Bash script that calls docker as a client to the host daemon
+# See documentation: https://www.windmill.dev/docs/advanced/docker
+msg="${1:-world}"
+
+IMAGE="alpine:latest"
+COMMAND="/bin/echo Hello $msg"
+
+# ensure that the image is up-to-date
+docker pull $IMAGE
+docker run --rm $IMAGE $COMMAND
+```
+
+`msg` is just a normal Bash variable. It can be used to pass arguments to the script. This syntax is the standard Bash one to assign default values to parameters.
+
+```
+docker run --rm <image> <command>
+```
+
+--rm is so that the container dispose itself after being executed. It helps unpollute the host.
+
+The image is the docker image to run. It can be any image available on docker hub or any private registry. It can also be a local image.
+
+The command is the command to run inside the container. It can be any command available in the image.
+
+It is just a Bash script so it will behave exactly the same as a local command or if running this as an ssh command on the host. As a consequence, you can use any strategy to cache docker images or handle authentification.
+
+Do not use the deamon mode `-d` otherwise the script will immediately return while the container continue to run in the background. However, in some cases, that might be what you want.
+
+Like any Bash script, it will return the last line of the stdout. So be sure to print the the return value from your command if you'd like to use it as a result.
+
+### Instant Preview & Testing
+
+Look at the UI preview on the right: it was updated to match the input
+signature. Run a test (`Ctrl` + `Enter`) to verify everything works.
+
+<video
+    className="border-2 rounded-xl object-cover w-full h-full dark:border-gray-800"
+    controls
+    src="/videos/auto_g_ui_landing.mp4"
+/>
+
+<br/>
+
+<div class="grid grid-cols-2 gap-6 mb-4">
+	<DocCard
+		title="Instant Preview & Testing"
+		description="On top of its integrated editors, Windmill allows users to test what they are building directly from the editor, even before deployment."
+		href="/docs/core_concepts/instant_preview"
+	/>
+</div>
+
+Now let's go to the last step: the "Customise" settings.
+
+### Customize Settings
+
+In this menu, you can:
+
+- Give a **script kind**: Action (by default), [Trigger](../../../flows/10_flow_trigger.md), [Approval](../../../flows/11_flow_approval.mdx) or [Error Handler](../../../flows/7_flow_error_handler.md). This acts as a tag to filter appropriate scripts from the [flow editor](../../6_flows_quickstart/index.mdx).
+- Customize the script's **Arguments**. The UI is generated from the Script's main function signature, but you can add additional constraints here. For example, we could use the `Customize property`: add a regex by clicking on `Pattern` to make sure users are providing a name with only alphanumeric characters: `^[A-Za-z0-9]+$`. Let's still allow numbers in case you are some tech billionaire's kid.
+
+![Advanced settings for Bash](../4_bash_quickstart/customize_bash.png)
+
+We're done! Save your script. Note that Scripts are versioned in Windmill, and
+each script version is uniquely identified by a hash.
+
+<div class="grid grid-cols-2 gap-6 mb-4">
+	<DocCard
+		title="Script Kinds"
+		description="You can attach additional functionalities to Scripts by specializing them into specific Script kinds."
+		href="/docs/script_editor/script_kinds"
+	/>
+	<DocCard
+		title="Customize Arguments"
+		description="Some arguments' types can be given advanced settings that will affect the inputs' auto-generated UI and JSON Schema."
+		href="/docs/script_editor/customize_arguments"
+	/>
+</div>
+
+### Run!
+
+Now let's look at what users of the script will do. Click on the [Deploy](../../../core_concepts/0_draft_and_deploy/index.mdx) button
+to load the script. You'll see the user input form we defined earlier.
+
+Fill in the input field, then hit "Run". You should see a run view, as well as
+your logs. All script runs are also available in the [Runs](../../../core_concepts/5_monitor_past_and_future_runs/index.mdx) menu on
+the left.
+
+![Run Hello in Bash](../4_bash_quickstart/run_bash.png)
+
+You can also chose to [run the script from the CLI](../../../advanced/3_cli/index.mdx) with the pre-made Command-Line Interface call.
+
+<div class="grid grid-cols-2 gap-6 mb-4">
+	<DocCard
+		title="Triggering Scripts"
+		description="Trigger flows on-demand, by schedule or on external events."
+		href="/docs/getting_started/trigger_scripts"
+	/>
+</div>
+
+## What's next?
+
+This script is a minimal working example, but there's a few more steps that can be useful in a real-world use case:
+
+- Pass [variables and secrets](../../../core_concepts/2_variables_and_secrets/index.mdx)
+  to a script.
+- Connect to [resources](../../../core_concepts/3_resources_and_types/index.mdx).
+- [Trigger that script](../../8_trigger_scripts/index.mdx) in many ways.
+- Compose scripts in [Flows](../../../flows/1_flow_editor.mdx) or [Apps](../../../apps/0_app_editor/index.mdx).
+- You can [share your scripts](../../../misc/1_share_on_hub/index.md) with the community on [Windmill Hub](https://hub.windmill.dev). Once
+  submitted, they will be verified by moderators before becoming available to
+  everyone right within Windmill.
+
+Scripts are immutable and there is an hash for each deployment of a given script. Scripts are never overwritten and referring to a script by path is referring to the latest deployed hash at that path.
+
+<div class="grid grid-cols-2 gap-6 mb-4">
+	<DocCard
+		title="Versioning"
+		description="Scripts, when deployed, can have a parent script identified by its hash."
+		href="/docs/script_editor/versioning"
+	/>
+</div>
+
+For each script, a UI is autogenerated from the jsonchema inferred from the script signature, and can be customized further as standalone or embedded into rich UIs using the [App builder](../../7_apps_quickstart/index.mdx).
+
+<div class="grid grid-cols-2 gap-6 mb-4">
+	<DocCard
+		title="Auto-generated UIs"
+		description="Windmill creates auto-generated user interfaces for scripts and flows based on their parameters."
+		href="/docs/core_concepts/auto_generated_uis"
+	/>
+	<DocCard
+		title="Customize Arguments"
+		description="Some arguments' types can be given advanced settings that will affect the inputs' auto-generated UI and JSON Schema."
+		href="/docs/script_editor/customize_arguments"
+	/>
+</div>
+
+In addition to the UI, sync and async [webhooks](../../../core_concepts/4_webhooks/index.md) are generated for each deployment.
+
+<div class="grid grid-cols-2 gap-6 mb-4">
+	<DocCard
+		title="Webhooks"
+		description="Trigger scripts and flows from webhooks."
+		href="/docs/core_concepts/webhooks"
+	/>
+</div>
\ No newline at end of file
diff --git a/docs/getting_started/0_scripts_quickstart/index.mdx b/docs/getting_started/0_scripts_quickstart/index.mdx
index 55e993531..3475b6cb8 100644
--- a/docs/getting_started/0_scripts_quickstart/index.mdx
+++ b/docs/getting_started/0_scripts_quickstart/index.mdx
@@ -51,9 +51,9 @@ Windmill supports scripts in Python, TypeScript, Go, Bash and Sql.
 		Icon={SiGraphql}
 	/>
 	<DocCard
-		title="Run Docker Containers"
-		description="In some cases where your task requires a complex set of dependencies or is implemented in a non-supported language, you can still include it as a flow step or individual script."
-		href="/docs/advanced/docker"
+		title="Docker"
+		description="Windmill supports running any docker container through its Bash support."
+		href="/docs/getting_started/scripts_quickstart/docker"
 		Icon={SiDocker}
 	/>
 </div>
diff --git a/sidebars.js b/sidebars.js
index f558cfacc..c004ecbf2 100644
--- a/sidebars.js
+++ b/sidebars.js
@@ -48,6 +48,11 @@ const sidebars = {
 							id: 'getting_started/scripts_quickstart/bash_quickstart/index',
 							label: 'Bash / PowerShell'
 						},
+						{
+							type: 'doc',
+							id: 'getting_started/scripts_quickstart/docker_quickstart/index',
+							label: 'Docker'
+						},
 						{
 							type: 'doc',
 							id: 'getting_started/scripts_quickstart/go_quickstart/index',
@@ -147,12 +152,12 @@ const sidebars = {
 								'apps/app_configuration-settings/app_runnable_triggers',
 								'apps/app_configuration-settings/app_component_configuration',
 								'apps/app_configuration-settings/components_groups',
-								'apps/app_configuration-settings/component_template',
 							]
 						},
 						'apps/app_configuration-settings/app_styling',
 						'apps/app_debugging',
 						'apps/app_deployment',
+						'apps/public_apps',
 						'apps/app_e-commerce'
 					],