diff --git a/docs/apps/4_app_configuration_settings/4_app_styling.mdx b/docs/apps/4_app_configuration_settings/4_app_styling.mdx
index 39b528fa0..51281838d 100644
--- a/docs/apps/4_app_configuration_settings/4_app_styling.mdx
+++ b/docs/apps/4_app_configuration_settings/4_app_styling.mdx
@@ -67,7 +67,7 @@ The Global CSS Editor is a feature exclusive to [Enterprise Edition](../../misc/
 
 Styling on a component level can be replicated to all the components of the same class from the Rich Editor.
 
-Just click on `Copy style to global CSS`.
+Just click on `Convert to global CSS`.
 
 <video
     className="border-2 rounded-xl object-cover w-full h-full dark:border-gray-800"
diff --git a/docs/compared_to/peers.mdx b/docs/compared_to/peers.mdx
index f809ced17..9c88c4c6f 100644
--- a/docs/compared_to/peers.mdx
+++ b/docs/compared_to/peers.mdx
@@ -37,7 +37,7 @@ From a tech stack perspective, we rely on the ACID properties of PostgreSQL to a
 <br/>
 
 To do a fair comparison, looking at the quickstart is a great way to see the different orientation of the product.
-The [Airflow quickstart](https://airflow.apache.org/docs/apache-airflow/stable/tutorial/fundamentals.html#example-pipeline-definition) is a great starting point. One has to learn what is an Airflow pipeline before being able to create or edit them. They also do not provide a great way to debug locally and iterate on those pipelines. You have to write them, deploy them, and then test them. By comparison, in Windmill you can [write scripts locally](../advanced/4_local_development/index.mdx), or test them either step by step or the full flow in the [web UI](../core_concepts/6_auto_generated_uis/index.md).
+The [Airflow quickstart](https://airflow.apache.org/docs/apache-airflow/stable/tutorial/fundamentals.html#example-pipeline-definition) is a great starting point. One has to learn what is an Airflow pipeline before being able to create or edit them. They also do not provide a great way to debug locally and iterate on those pipelines. You have to write them, deploy them, and then test them. By comparison, in Windmill you can [write scripts locally](../advanced/4_local_development/index.mdx), or test them either step by step or the full flow in the [web UI](../core_concepts/6_auto_generated_uis/index.mdx).
 
 <br/>
 
diff --git a/docs/compared_to/prefect.mdx b/docs/compared_to/prefect.mdx
index b6d368296..294e0dfcb 100644
--- a/docs/compared_to/prefect.mdx
+++ b/docs/compared_to/prefect.mdx
@@ -94,7 +94,7 @@ The structuring of the flow and the configurations for each step are defined fro
 
 <br/>
 
-In particular, Windmill [generates automatically UIs](../core_concepts/6_auto_generated_uis/index.md) for flows and steps and lets users [test](../core_concepts/23_instant_preview/index.mdx) flows, steps or flow until a given step, from the UI.
+In particular, Windmill [generates automatically UIs](../core_concepts/6_auto_generated_uis/index.mdx) for flows and steps and lets users [test](../core_concepts/23_instant_preview/index.mdx) flows, steps or flow until a given step, from the UI.
 
 Flows can be [defined visually / YAML](../advanced/4_local_development/index.mdx) on a local environment. Windmill will soon unveil an extension to facilitate the editing of flows in local development.
 
diff --git a/docs/compared_to/retool.mdx b/docs/compared_to/retool.mdx
index 2613e66b1..5a07335eb 100644
--- a/docs/compared_to/retool.mdx
+++ b/docs/compared_to/retool.mdx
@@ -83,7 +83,7 @@ For each of those languages, scripts can be run [without having to deal with sep
 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.
+executable through [autogenerated UIs](../core_concepts/6_auto_generated_uis/index.mdx), [webhooks](../core_concepts/4_webhooks/index.md), etc.
 
 <div class="grid grid-cols-2 gap-6 mb-4">
 	<DocCard
diff --git a/docs/core_concepts/0_draft_and_deploy/index.mdx b/docs/core_concepts/0_draft_and_deploy/index.mdx
index 100b68f7a..c023cbd69 100644
--- a/docs/core_concepts/0_draft_and_deploy/index.mdx
+++ b/docs/core_concepts/0_draft_and_deploy/index.mdx
@@ -38,7 +38,7 @@ 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 [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.
+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.mdx), [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`.
 
diff --git a/docs/core_concepts/11_persistent_storage/index.mdx b/docs/core_concepts/11_persistent_storage/index.mdx
index 7c8d2c4f5..1fe1656fd 100644
--- a/docs/core_concepts/11_persistent_storage/index.mdx
+++ b/docs/core_concepts/11_persistent_storage/index.mdx
@@ -170,7 +170,7 @@ For Postgres databases (best for structured data storage and retrieval, where yo
    - Click `Database`.
    - Find your Connection Info and Connection String. Direct connections are on port 5432.
 
-4. From Windmill, add your Supabase connection string as a [Postgresql resource](https://hub.windmill.dev/resource_types/6/postgresql) and [Execute queries](https://hub.windmill.dev/scripts/postgresql/1294/execute-query-and-return-results-postgresql). Tip: you might need to set the `sslmode` to "disable".
+4. From Windmill, add your Supabase connection string as a [Postgresql resource](https://hub.windmill.dev/resource_types/114/postgresql) and [Execute queries](https://hub.windmill.dev/scripts/postgresql/1294/execute-query-and-return-results-postgresql). Tip: you might need to set the `sslmode` to "disable".
 
 <video
     className="border-2 rounded-xl object-cover w-full h-full dark:border-gray-800"
@@ -208,7 +208,7 @@ More tutorials on Supabase:
 
 3. Get a [Connection string](https://neon.tech/docs/connect/query-with-psql-editor). You can obtain it connection string from the Connection Details widget on the Neon Dashboard: select a branch, a role, and the database you want to connect to and a connection string will be constructed for you.
 
-4. From Windmill, add your Neon.tech connection string as a [Postgresql resource](https://hub.windmill.dev/resource_types/6/postgresql) and [Execute queries](https://hub.windmill.dev/scripts/postgresql/1294/execute-query-and-return-results-postgresql).
+4. From Windmill, add your Neon.tech connection string as a [Postgresql resource](https://hub.windmill.dev/resource_types/114/postgresql) and [Execute queries](https://hub.windmill.dev/scripts/postgresql/1294/execute-query-and-return-results-postgresql).
 
 <video
     className="border-2 rounded-xl object-cover w-full h-full dark:border-gray-800"
diff --git a/docs/core_concepts/13_json_schema_and_parsing/index.md b/docs/core_concepts/13_json_schema_and_parsing/index.md
index b64628236..e1344fee2 100644
--- a/docs/core_concepts/13_json_schema_and_parsing/index.md
+++ b/docs/core_concepts/13_json_schema_and_parsing/index.md
@@ -140,7 +140,7 @@ Resource types in Windmill are associated with JSON Schemas. A resource type def
 
 ## Advanced Settings
 
-Some arguments' types can be given advanced settings that will affect the inputs' [auto-generated UI](../../core_concepts/6_auto_generated_uis/index.md) and JSON Schema.
+Some arguments' types can be given advanced settings that will affect the inputs' [auto-generated UI](../../core_concepts/6_auto_generated_uis/index.mdx) and JSON Schema.
 
 Here is an example on how to define a python list as an enum of strings using the `Customize` menu.
 
diff --git a/docs/core_concepts/16_roles_and_permissions/index.mdx b/docs/core_concepts/16_roles_and_permissions/index.mdx
index 52fdff9f8..82f77d59c 100644
--- a/docs/core_concepts/16_roles_and_permissions/index.mdx
+++ b/docs/core_concepts/16_roles_and_permissions/index.mdx
@@ -42,7 +42,7 @@ Users can be given different levels of permissions:
 3. **Author**: Authors can execute and view scripts, flows, and apps within a workspace. Authors see the full interface of Windmill and contrary to the Operators, they have the ability to create and edit scripts, flows and apps. Authors have read and write access to the entities they create or have been [granted access to by others](../8_groups_and_folders/index.mdx).
 
 4. **Operator**: Operators have limited access within a workspace. They can only execute and view scripts, flows, and apps that they have visibility on, and only those that are within their allowed path or [folders](../8_groups_and_folders/index.mdx). Operators do not have the ability to create or modify entities.
-The recommended way to share scripts and flows with operators is through [auto-generated apps](../6_auto_generated_uis/index.md#automatically-generated-apps).
+The recommended way to share scripts and flows with operators is through [auto-generated apps](../6_auto_generated_uis/index.mdx#automatically-generated-apps).
 With the second option being of sharing the script and [variables](../2_variables_and_secrets/index.mdx) it depends on (but operators won't be able to load variable directly from the UI/api, only use them within the scripts they have access to).
 
 5. **Anonymous app viewers**: Anonymous app viewers are individuals who can access and view Windmill apps without being a user but by knowing the [secret URL](../../apps/0_toolbar.md#deploy) that allows app viewing. They do not have any editing or privileges to execute scripts and flows. The apps that they see execute the scripts and flows that are part of the app but only on behalf of the app author. The anonymous user cannot execute any of the scripts and flows part of the apps outside of the inputs authorized by the app through a policy that is automatically generated by the app.
diff --git a/docs/core_concepts/1_scheduling/index.md b/docs/core_concepts/1_scheduling/index.md
index 606306cdf..d64cb5a98 100644
--- a/docs/core_concepts/1_scheduling/index.md
+++ b/docs/core_concepts/1_scheduling/index.md
@@ -162,7 +162,7 @@ If you want to handle failure and receive another message in that case, add an [
 
 ### Manage permissions from the workflow
 
-From the metadata menu, change the owner to a [folder](../../core_concepts/8_groups_and_folders/index.mdx#folders) (group of people) to manage view and editing rights.
+From the settings menu, change the owner to a [folder](../../core_concepts/8_groups_and_folders/index.mdx#folders) (group of people) to manage view and editing rights.
 
 ![Manage permissions](./5-manage-rights.png.webp 'Manage permissions')
 
diff --git a/docs/core_concepts/21_concurrency_limits/index.md b/docs/core_concepts/21_concurrency_limits/index.md
index d31278a43..884e5c19f 100644
--- a/docs/core_concepts/21_concurrency_limits/index.md
+++ b/docs/core_concepts/21_concurrency_limits/index.md
@@ -8,7 +8,7 @@ When jobs reach the concurrency limit, they are automatically queued for executi
 
 ## Concurrency limit of Script
 
-Concurrency limit can be set from the metadata menu. Pick "Concurrency" and define a time window and max number of executions of the flow within that time window.
+Concurrency limit can be set from the Settings menu. Pick "Concurrency" and define a time window and max number of executions of the flow within that time window.
 
 ![Concurrency Limit](../../assets/code_editor/concurrency_limit.png.webp)
 
diff --git a/docs/core_concepts/24_caching/index.md b/docs/core_concepts/24_caching/index.md
index eacf4218b..0f6bc0a85 100644
--- a/docs/core_concepts/24_caching/index.md
+++ b/docs/core_concepts/24_caching/index.md
@@ -18,9 +18,9 @@ Caching a script means caching the results of that script for a certain duration
 
 <br/>
 
-You can enable caching for a script directly in the script metadata. Here's how you can do it:
+You can enable caching for a script directly in the script Settings. Here's how you can do it:
 
-1. **Metadata**: From the Script Editor, pick the "Metdata" menu an scroll to "Cache".
+1. **Settings**: From the Script Editor, pick the "Settings" menu an scroll to "Cache".
 
 2. **Enable Caching**: To enable caching, toggle on "Cache the results for each possible inputs" and specify the desired duration for caching results (in seconds.)
 
diff --git a/docs/core_concepts/25_dedicated_workers/index.mdx b/docs/core_concepts/25_dedicated_workers/index.mdx
index 3bae66402..4c6834143 100644
--- a/docs/core_concepts/25_dedicated_workers/index.mdx
+++ b/docs/core_concepts/25_dedicated_workers/index.mdx
@@ -19,7 +19,7 @@ To use:
 
 The worker group will restart (assuming the pods/restart are set to restart automatically) and will now wait for step 2. below to happen:
 
-2. toggle the "Dedicated Workers" option for that script in the metadata:
+2. toggle the "Dedicated Workers" option for that script in the Settings:
 
 ![Dedicated Workers](./dedicated_workers.png)
 
diff --git a/docs/core_concepts/6_auto_generated_uis/index.md b/docs/core_concepts/6_auto_generated_uis/index.mdx
similarity index 66%
rename from docs/core_concepts/6_auto_generated_uis/index.md
rename to docs/core_concepts/6_auto_generated_uis/index.mdx
index 0eedab733..330c59925 100644
--- a/docs/core_concepts/6_auto_generated_uis/index.md
+++ b/docs/core_concepts/6_auto_generated_uis/index.mdx
@@ -1,3 +1,5 @@
+import DocCard from '@site/src/components/DocCard';
+
 # Auto-Generated UIs
 
 Windmill automatically generates user interfaces (UIs) for scripts and flows based on their parameters.
@@ -18,25 +20,25 @@ You might also be interested by Windmill's [App editor](../../getting_started/7_
 
 :::
 
-## Details Page
-
 By analyzing the parameters of the main function, Windmill generates an input specification for the script or flow in the [JSON Schema](../13_json_schema_and_parsing/index.md) format. Windmill then renders the UI for the Script or Flow from that specification.
 
 You don't need to directly interact with the JSON Schema associated with the Script or Flow. It is the result of the analysis of the script parameters of the main function and the optional UI customization.
 
-In the UI customization interface, you can refine information that couldn't be inferred directly from the parameters, such as specifying string enums or restricting lists to numbers. You can also add helpful descriptions to each field.
+In the [UI customization interface](../../script_editor/customize_ui.mdx), you can refine information that couldn't be inferred directly from the parameters, such as specifying string enums or restricting lists to numbers. You can also add helpful descriptions to each field.
 
 ![Customize inputs](./customize_inputs.png.webp)
 
-> The inputs' positions and properties can be customized
-
-<br/>
-
-:::tip Test code
+<div class="grid grid-cols-2 gap-6 mb-4">
+	<DocCard
+		title="Customize UI"
+		description="Some arguments' types can be given advanced settings that will affect the inputs' auto-generated UI and JSON Schema."
+		href="/docs/script_editor/generated_ui"
+	/>
+</div>
 
-This feature can be directly used in the [script](../../getting_started/0_scripts_quickstart/index.mdx) & [flow](../../getting_started/6_flows_quickstart/index.mdx) editors to test your code.
+## Test code
 
-<br/>
+This feature can be directly used in the [script](../../getting_started/0_scripts_quickstart/index.mdx) & [flow](../../getting_started/6_flows_quickstart/index.mdx) editors to [test your code](../23_instant_preview/index.mdx).
 
 <video
     className="border-2 rounded-xl object-cover w-full h-full dark:border-gray-800"
@@ -44,9 +46,17 @@ This feature can be directly used in the [script](../../getting_started/0_script
     src="/videos/ui_from_script_editor.mp4"
 />
 
-:::
+<br/>
 
-## Automatically Generated Apps
+<div class="grid grid-cols-2 gap-6 mb-4">
+	<DocCard
+    	title="Instant Preview & Testing"
+    	description="Windmill allows users to test what they are building directly from the editor, even before deployment."
+    	href="/docs/core_concepts/instant_preview"
+    />
+</div>
+
+## Build App
 
 You can generate a dedicated [app](../../apps/0_app_editor/index.mdx) to execute your script or flow.
 
@@ -68,4 +78,12 @@ The apps will be permissioned on behalf of the [admin/author](../16_roles_and_pe
 
 <br/>
 
-At last, this is an easy way to get an app for your scripts and flows to be customized with [Styling](../../apps/4_app_configuration_settings/4_app_styling.mdx) and [Components](../../apps/4_app_configuration_settings/1_app_component_library.mdx).
\ No newline at end of file
+At last, this is an easy way to get an app for your scripts and flows to be customized with [Styling](../../apps/4_app_configuration_settings/4_app_styling.mdx) and [Components](../../apps/4_app_configuration_settings/1_app_component_library.mdx).
+
+<div class="grid grid-cols-2 gap-6 mb-4">
+	<DocCard
+    	title="Instant Preview & Testing"
+    	description="Windmill allows users to test what they are building directly from the editor, even before deployment."
+    	href="/docs/core_concepts/instant_preview"
+    />
+</div>
\ No newline at end of file
diff --git a/docs/core_concepts/9_worker_groups/index.mdx b/docs/core_concepts/9_worker_groups/index.mdx
index 202632f2a..b99f9eb7f 100644
--- a/docs/core_concepts/9_worker_groups/index.mdx
+++ b/docs/core_concepts/9_worker_groups/index.mdx
@@ -72,7 +72,7 @@ WORKER_TAGS=tag1,tag2
 
 ## 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.
+For scripts saved on the script editor, select the corresponding worker group tag in the settings section.
 
 ![Worker group tag](./select_script_builder.png.webp)
 
diff --git a/docs/core_concepts/index.mdx b/docs/core_concepts/index.mdx
index 5f06fcb10..776479326 100644
--- a/docs/core_concepts/index.mdx
+++ b/docs/core_concepts/index.mdx
@@ -179,9 +179,9 @@ All details on Scripts can be found in the [Script section](../script_editor/ind
 		href="/docs/script_editor/script_kinds"
 	/>
     <DocCard
-		title="Customize Arguments"
+		title="Customize UI"
 		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"
+		href="/docs/script_editor/customize_ui"
     />
     <DocCard
 		title="Versioning"
diff --git a/docs/flows/3_editor_components.mdx b/docs/flows/3_editor_components.mdx
index 89c001f9e..e33693455 100644
--- a/docs/flows/3_editor_components.mdx
+++ b/docs/flows/3_editor_components.mdx
@@ -78,7 +78,7 @@ This is where you can give instructions to users on how to run your Flow. It sup
 
 ### Schedule
 
-Flows can be [triggered](../getting_started/9_trigger_flows/index.mdx) by any [schedules](../core_concepts/1_scheduling/index.md), their [webhooks](../core_concepts/4_webhooks/index.md) or their [UI](../core_concepts/6_auto_generated_uis/index.md) but they only have only one primary schedules with which they share the same path. The primary schedule can be set here.
+Flows can be [triggered](../getting_started/9_trigger_flows/index.mdx) by any [schedules](../core_concepts/1_scheduling/index.md), their [webhooks](../core_concepts/4_webhooks/index.md) or their [UI](../core_concepts/6_auto_generated_uis/index.mdx) but they only have only one primary schedules with which they share the same path. The primary schedule can be set here.
 
 A CRON expression is used to define the schedule. Schedules can also be disabled.
 
@@ -155,7 +155,7 @@ Flows can be assigned custom [worker groups](../core_concepts/9_worker_groups/in
 
 ## Test flow
 
-Test your current version of the flow with the `Test flow` button. This will opens a menu with an [auto-generated UI](../core_concepts/6_auto_generated_uis/index.md) of your current configuration.
+Test your current version of the flow with the `Test flow` button. This will opens a menu with an [auto-generated UI](../core_concepts/6_auto_generated_uis/index.mdx) of your current configuration.
 
 You can also test up to a certain step by clicking on an action (x) and then on `Test up to x`.
 
@@ -202,14 +202,14 @@ It will open a slider where you can configure the flow input.
 - **Type**: the type of the flow input: Integer, Number, String, Boolean, Array, Object, or Any.
 - **Default value**: the default value of the flow input.
 
-Some arguments' types can be given advanced settings that will affect the inputs' [auto-generated UI](../core_concepts/6_auto_generated_uis/index.md) and [JSON Schema](../core_concepts/13_json_schema_and_parsing/index.md).
+Some arguments' types can be given advanced settings that will affect the inputs' [auto-generated UI](../core_concepts/6_auto_generated_uis/index.mdx) and [JSON Schema](../core_concepts/13_json_schema_and_parsing/index.md).
 
 Here is an example on how to define a list as an enum of strings using the `Customize` menu.
 
 <video
 	className="border-2 rounded-xl object-cover w-full h-full dark:border-gray-800"
 	controls
-	src="customize_arguments_flow.mp4"
+	src="generated_ui_flow.mp4"
 />
 
 <br />
diff --git a/docs/getting_started/0_scripts_quickstart/1_typescript_quickstart/create_script_deno.png b/docs/getting_started/0_scripts_quickstart/1_typescript_quickstart/create_script_deno.png
index a811e0106..1cd9c0d37 100644
Binary files a/docs/getting_started/0_scripts_quickstart/1_typescript_quickstart/create_script_deno.png and b/docs/getting_started/0_scripts_quickstart/1_typescript_quickstart/create_script_deno.png differ
diff --git a/docs/getting_started/0_scripts_quickstart/1_typescript_quickstart/customize_ts.png b/docs/getting_started/0_scripts_quickstart/1_typescript_quickstart/customize_ts.png
index 4ee58e6f9..a87b66f5f 100644
Binary files a/docs/getting_started/0_scripts_quickstart/1_typescript_quickstart/customize_ts.png and b/docs/getting_started/0_scripts_quickstart/1_typescript_quickstart/customize_ts.png differ
diff --git a/docs/getting_started/0_scripts_quickstart/1_typescript_quickstart/customize_ts.png.avif b/docs/getting_started/0_scripts_quickstart/1_typescript_quickstart/customize_ts.png.avif
deleted file mode 100644
index decf2c179..000000000
Binary files a/docs/getting_started/0_scripts_quickstart/1_typescript_quickstart/customize_ts.png.avif and /dev/null differ
diff --git a/docs/getting_started/0_scripts_quickstart/1_typescript_quickstart/customize_ts.png.webp b/docs/getting_started/0_scripts_quickstart/1_typescript_quickstart/customize_ts.png.webp
deleted file mode 100644
index dc73fc6f2..000000000
Binary files a/docs/getting_started/0_scripts_quickstart/1_typescript_quickstart/customize_ts.png.webp and /dev/null differ
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 26f6fc2c9..75a70cb1e 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
@@ -37,7 +37,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.
-- [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).
+- [Settings](#settings): settings & 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`.
 
@@ -63,11 +63,11 @@ In this quick start guide, we'll create a script that greets the operator runnin
 From the Home page, click `+Script`. This will take you to the
 first step of script creation: Metadata.
 
-## Metadata
+## Settings
 
 ![New script](./create_script_deno.png)
 
-Each script has metadata associated with it, enabling it to be defined and configured in depth.
+As part of the settings menu, 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.
@@ -76,16 +76,22 @@ Each script has metadata associated with it, enabling it to be defined and confi
   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)
+- **Description** is where you can give instructions through the [auto-generated UI](../../../core_concepts/6_auto_generated_uis/index.mdx)
   to users on how to run your Script. It supports markdown.
+- **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).
+
+This menu also has additional settings, such as:
+
 - **[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).
+- **[Cache](../../../core_concepts/24_caching/index.md)** to cache the results for each possible inputs for a given time.
+- **[Dedicated Workers](../../../core_concepts/25_dedicated_workers/index.mdx)** to run the script on, to run the script at native speed. Only available on enterprise edition and for the Bun language.
 
 <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"
+		title="Settings"
+		description="Each script has metadata & settings associated with it, enabling it to be defined and configured in depth."
+		href="/docs/script_editor/settings"
 	/>
 </div>
 
@@ -94,7 +100,7 @@ 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
+the editor itself. The right-side [previews the UI](../../../core_concepts/6_auto_generated_uis/index.mdx) 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.
 
@@ -149,7 +155,7 @@ entrypoint. There are a few important things to note about the `main`.
 
 - The main arguments are used for generating
 	1. the [input spec](../../../core_concepts/13_json_schema_and_parsing/index.md) of the Script
-	2. the [frontend](../../../core_concepts/6_auto_generated_uis/index.md) that you see when running the Script as a standalone app.
+	2. the [frontend](../../../core_concepts/6_auto_generated_uis/index.mdx) that you see when running the Script as a standalone app.
 - Type annotations are used to generate the UI form, and help pre-validate
   inputs. While not mandatory, they are highly recommended. You can customize
   the UI in later steps (but not change the input type!).
@@ -224,7 +230,7 @@ entrypoint. There are a few important things to note about the `main`.
 
 - The main arguments are used for generating
 	1. the [input spec](../../../core_concepts/13_json_schema_and_parsing/index.md) of the Script
-	2. the [frontend](../../../core_concepts/6_auto_generated_uis/index.md) that you see when running the Script as a standalone app.
+	2. the [frontend](../../../core_concepts/6_auto_generated_uis/index.mdx) that you see when running the Script as a standalone app.
 - Type annotations are used to generate the UI form, and help pre-validate
   inputs. While not mandatory, they are highly recommended. You can customize
   the UI in later steps (but not change the input type!).
@@ -298,19 +304,15 @@ main(name: string = "you")
 	/>
 </div>
 
-Now let's go to the last step: the "Customise" settings.
+Now let's go to the last step: the "Generated UI" settings.
 
-## Customize Settings
+## Customize UI
 
-In this menu, you can:
+From the Settings menu, the "Generated UI" tab lets you customize the script's arguments.
 
-- 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.
+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 TypeScript](./customize_ts.png.webp)
-
-We're done! Save your script. Note that Scripts are versioned in Windmill, and
-each script version is uniquely identified by a hash.
+![Advanced settings for TypeScript](./customize_ts.png)
 
 <div class="grid grid-cols-2 gap-6 mb-4">
 	<DocCard
@@ -319,17 +321,20 @@ each script version is uniquely identified by a hash.
 		href="/docs/script_editor/script_kinds"
 	/>
 	<DocCard
-		title="Customize Arguments"
+		title="Customize UI"
 		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"
+		href="/docs/script_editor/customize_ui"
 	/>
 </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
+We're done! 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.
 
+Note that Scripts are versioned in Windmill, and
+each script version is uniquely [identified by a hash](../../../script_editor/versioning.mdx)
+
 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.
@@ -378,9 +383,9 @@ For each script, a UI is autogenerated from the jsonchema inferred from the scri
 		href="/docs/core_concepts/auto_generated_uis"
 	/>
 	<DocCard
-		title="Customize Arguments"
+		title="Customize UI"
 		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"
+		href="/docs/script_editor/customize_ui"
 	/>
 </div>
 
diff --git a/docs/getting_started/0_scripts_quickstart/2_python_quickstart/create_script_python.png b/docs/getting_started/0_scripts_quickstart/2_python_quickstart/create_script_python.png
index e96145a00..34872d241 100644
Binary files a/docs/getting_started/0_scripts_quickstart/2_python_quickstart/create_script_python.png and b/docs/getting_started/0_scripts_quickstart/2_python_quickstart/create_script_python.png differ
diff --git a/docs/getting_started/0_scripts_quickstart/2_python_quickstart/create_script_python.png.avif b/docs/getting_started/0_scripts_quickstart/2_python_quickstart/create_script_python.png.avif
deleted file mode 100644
index 70e4232ff..000000000
Binary files a/docs/getting_started/0_scripts_quickstart/2_python_quickstart/create_script_python.png.avif and /dev/null differ
diff --git a/docs/getting_started/0_scripts_quickstart/2_python_quickstart/create_script_python.png.webp b/docs/getting_started/0_scripts_quickstart/2_python_quickstart/create_script_python.png.webp
deleted file mode 100644
index 1c4d08222..000000000
Binary files a/docs/getting_started/0_scripts_quickstart/2_python_quickstart/create_script_python.png.webp and /dev/null differ
diff --git a/docs/getting_started/0_scripts_quickstart/2_python_quickstart/customize_python.png b/docs/getting_started/0_scripts_quickstart/2_python_quickstart/customize_python.png
index d8fbfa00b..a91697e97 100644
Binary files a/docs/getting_started/0_scripts_quickstart/2_python_quickstart/customize_python.png and b/docs/getting_started/0_scripts_quickstart/2_python_quickstart/customize_python.png differ
diff --git a/docs/getting_started/0_scripts_quickstart/2_python_quickstart/customize_python.png.avif b/docs/getting_started/0_scripts_quickstart/2_python_quickstart/customize_python.png.avif
deleted file mode 100644
index 8c8fc3609..000000000
Binary files a/docs/getting_started/0_scripts_quickstart/2_python_quickstart/customize_python.png.avif and /dev/null differ
diff --git a/docs/getting_started/0_scripts_quickstart/2_python_quickstart/customize_python.png.webp b/docs/getting_started/0_scripts_quickstart/2_python_quickstart/customize_python.png.webp
deleted file mode 100644
index ced98daed..000000000
Binary files a/docs/getting_started/0_scripts_quickstart/2_python_quickstart/customize_python.png.webp and /dev/null differ
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 6c155e013..971f64631 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
@@ -37,7 +37,7 @@ Scripts are the basic building blocks in Windmill. They can be [run and schedule
 Scripts consist of 2 parts:
 
 - [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).
+- [Settings](#settings): settings & 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`
 
@@ -58,11 +58,11 @@ In this quick start guide, we'll create a script that greets the operator runnin
 From the Home page, click `+Script`. This will take you to the
 first step of script creation: Metadata.
 
-## Metadata
+## Settings
 
-![New script](./create_script_python.png.webp)
+![New script](./create_script_python.png)
 
-Each script has metadata associated with it, enabling it to be defined and configured in depth.
+As part of the settings menu, 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.
@@ -71,15 +71,21 @@ Each script has metadata associated with it, enabling it to be defined and confi
   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)
+- **Description** is where you can give instructions through the [auto-generated UI](../../../core_concepts/6_auto_generated_uis/index.mdx)
   to users on how to run your Script. It supports markdown.
+- **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).
+
+This menu also has additional settings, such as:
+
 - **[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).
+- **[Cache](../../../core_concepts/24_caching/index.md)** to cache the results for each possible inputs for a given time.
+- **[Dedicated Workers](../../../core_concepts/25_dedicated_workers/index.mdx)** to run the script on, to run the script at native speed. Only available on enterprise edition and for the Bun language.
 
 <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."
+		title="Settings"
+		description="Each script has metadata & settings associated with it, enabling it to be defined and configured in depth."
 		href="/docs/script_editor/metadata"
 	/>
 </div>
@@ -89,7 +95,7 @@ Now click on the code editor on the left side, and let's build our Hello World!
 ## 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
+the editor itself. The right-side [previews the UI](../../../core_concepts/6_auto_generated_uis/index.mdx) 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.
 
@@ -159,7 +165,7 @@ entrypoint. There are a few important things to note about the `main`.
 
 - The main arguments are used for generating
 	1. the [input spec](../../../core_concepts/13_json_schema_and_parsing/index.md) of the Script
-	2. the [frontend](../../../core_concepts/6_auto_generated_uis/index.md) that you see when running the Script as a standalone app.
+	2. the [frontend](../../../core_concepts/6_auto_generated_uis/index.mdx) that you see when running the Script as a standalone app.
 - Type annotations are used to generate the UI form, and help pre-validate
   inputs. While not mandatory, they are highly recommended. You can customize
   the UI in later steps (but not change the input type!).
@@ -228,19 +234,15 @@ main(name: str = "you")
 	/>
 </div>
 
-Now let's go to the last step: the "Customise" settings.
+Now let's go to the last step: the "Generated UI" settings.
 
-## Customize Settings
+## Customize UI
 
-In this step, you can:
+From the Settings menu, the "Generated UI" tab lets you customize the script's arguments.
 
-- 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.
+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 Python](./customize_python.png.webp)
-
-We're done! Save your script. Note that Scripts are versioned in Windmill, and
-each script version is uniquely identified by a hash.
+![Advanced settings for Python](./customize_python.png)
 
 <div class="grid grid-cols-2 gap-6 mb-4">
 	<DocCard
@@ -249,17 +251,20 @@ each script version is uniquely identified by a hash.
 		href="/docs/script_editor/script_kinds"
 	/>
 	<DocCard
-		title="Customize Arguments"
+		title="Customize UI"
 		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"
+		href="/docs/script_editor/customize_ui"
 	/>
 </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
+We're done! 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.
 
+Note that Scripts are versioned in Windmill, and
+each script version is uniquely [identified by a hash](../../../script_editor/versioning.mdx)
+
 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.
@@ -308,9 +313,9 @@ For each script, a UI is autogenerated from the jsonchema inferred from the scri
 		href="/docs/core_concepts/auto_generated_uis"
 	/>
 	<DocCard
-		title="Customize Arguments"
+		title="Customize UI"
 		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"
+		href="/docs/script_editor/customize_ui"
 	/>
 </div>
 
diff --git a/docs/getting_started/0_scripts_quickstart/3_go_quickstart/create_script_go.png b/docs/getting_started/0_scripts_quickstart/3_go_quickstart/create_script_go.png
index 9cb366a08..e4063ab47 100644
Binary files a/docs/getting_started/0_scripts_quickstart/3_go_quickstart/create_script_go.png and b/docs/getting_started/0_scripts_quickstart/3_go_quickstart/create_script_go.png differ
diff --git a/docs/getting_started/0_scripts_quickstart/3_go_quickstart/customize_go.png b/docs/getting_started/0_scripts_quickstart/3_go_quickstart/customize_go.png
index 34d1ba770..571bbc181 100644
Binary files a/docs/getting_started/0_scripts_quickstart/3_go_quickstart/customize_go.png and b/docs/getting_started/0_scripts_quickstart/3_go_quickstart/customize_go.png differ
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 1f70e2e1e..798c7ed19 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
@@ -37,7 +37,7 @@ Scripts are the basic building blocks in Windmill. They can be [run and schedule
 Scripts consist of 2 parts:
 
 - [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).
+- [Settings](#settings): settings & 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`.
 
@@ -72,11 +72,11 @@ In this quick start guide, we'll create a script that greets the operator runnin
 From the Home page, click `+Script`. This will take you to the
 first step of script creation: Metadata.
 
-## Metadata
+## Settings
 
 ![New script](./create_script_go.png)
 
-Each script has metadata associated with it, enabling it to be defined and configured in depth.
+As part of the settings menu, 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.
@@ -85,16 +85,22 @@ Each script has metadata associated with it, enabling it to be defined and confi
   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)
+- **Description** is where you can give instructions through the [auto-generated UI](../../../core_concepts/6_auto_generated_uis/index.mdx)
   to users on how to run your Script. It supports markdown.
+- **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).
+
+This menu also has additional settings, such as:
+
 - **[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).
+- **[Cache](../../../core_concepts/24_caching/index.md)** to cache the results for each possible inputs for a given time.
+- **[Dedicated Workers](../../../core_concepts/25_dedicated_workers/index.mdx)** to run the script on, to run the script at native speed. Only available on enterprise edition and for the Bun language.
 
 <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"
+		title="Settings"
+		description="Each script has metadata & settings associated with it, enabling it to be defined and configured in depth."
+		href="/docs/script_editor/settings"
 	/>
 </div>
 
@@ -103,7 +109,7 @@ 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
+the editor itself. The right-side [previews the UI](../../../core_concepts/6_auto_generated_uis/index.mdx) 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.
 
@@ -152,7 +158,7 @@ entrypoint. There are a few important things to note about the `main`.
 
 - The main arguments are used for generating
 	1. the [input spec](../../../core_concepts/13_json_schema_and_parsing/index.md) of the Script
-	2. the [frontend](../../../core_concepts/6_auto_generated_uis/index.md) that you see when running the Script as a standalone app.
+	2. the [frontend](../../../core_concepts/6_auto_generated_uis/index.mdx) that you see when running the Script as a standalone app.
 - Type annotations are used to generate the UI form, and help pre-validate
   inputs. While not mandatory, they are highly recommended. You can customize
   the UI in later steps (but not change the input type!).
@@ -217,20 +223,16 @@ signature. Run a test (`Ctrl` + `Enter`) to verify everything works.
 	/>
 </div>
 
-Now let's go to the last step: the "Customise" settings.
+Now let's go to the last step: the "Generated UI" settings.
 
-## Customize Settings
+## Customize UI
 
-In this step, you can:
+From the Settings menu, the "Generated UI" tab lets you customize the script's arguments.
 
-- 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.
+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 Python](./customize_go.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"
@@ -238,17 +240,20 @@ each script version is uniquely identified by a hash.
 		href="/docs/script_editor/script_kinds"
 	/>
 	<DocCard
-		title="Customize Arguments"
+		title="Customize UI"
 		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"
+		href="/docs/script_editor/customize_ui"
 	/>
 </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
+We're done! 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.
 
+Note that Scripts are versioned in Windmill, and
+each script version is uniquely [identified by a hash](../../../script_editor/versioning.mdx)
+
 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.
@@ -297,9 +302,9 @@ For each script, a UI is autogenerated from the jsonchema inferred from the scri
 		href="/docs/core_concepts/auto_generated_uis"
 	/>
 	<DocCard
-		title="Customize Arguments"
+		title="Customize UI"
 		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"
+		href="/docs/script_editor/customize_ui"
 	/>
 </div>
 
diff --git a/docs/getting_started/0_scripts_quickstart/4_bash_quickstart/create_script_bash.png b/docs/getting_started/0_scripts_quickstart/4_bash_quickstart/create_script_bash.png
index f057ce6f1..d4fe92291 100644
Binary files a/docs/getting_started/0_scripts_quickstart/4_bash_quickstart/create_script_bash.png and b/docs/getting_started/0_scripts_quickstart/4_bash_quickstart/create_script_bash.png differ
diff --git a/docs/getting_started/0_scripts_quickstart/4_bash_quickstart/customize_bash.png b/docs/getting_started/0_scripts_quickstart/4_bash_quickstart/customize_bash.png
index c3ca21b17..e88ea689d 100644
Binary files a/docs/getting_started/0_scripts_quickstart/4_bash_quickstart/customize_bash.png and b/docs/getting_started/0_scripts_quickstart/4_bash_quickstart/customize_bash.png differ
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 b6fde9022..224d5f3a9 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
@@ -19,7 +19,7 @@ In this quick start guide, we will write our first script in Bash and PowerShell
 	src="/videos/bash_quickstart.mp4"
 />
 
-<br />
+<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).
 
@@ -39,7 +39,7 @@ Scripts are the basic building blocks in Windmill. They can be [run and schedule
 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).
+- [Settings](#settings): settings & 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`.
 
@@ -85,11 +85,11 @@ In this quick start guide, we'll create a script that greets the operator runnin
 From the Home page, click `+Script`. This will take you to the
 first step of script creation: Metadata.
 
-## Metadata
+## Settings
 
 ![New script](./create_script_bash.png)
 
-Each script has metadata associated with it, enabling it to be defined and configured in depth.
+As part of the settings menu, 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.
@@ -98,16 +98,22 @@ Each script has metadata associated with it, enabling it to be defined and confi
   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)
+- **Description** is where you can give instructions through the [auto-generated UI](../../../core_concepts/6_auto_generated_uis/index.mdx)
   to users on how to run your Script. It supports markdown.
+- **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).
+
+This menu also has additional settings, such as:
+
 - **[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).
+- **[Cache](../../../core_concepts/24_caching/index.md)** to cache the results for each possible inputs for a given time.
+- **[Dedicated Workers](../../../core_concepts/25_dedicated_workers/index.mdx)** to run the script on, to run the script at native speed. Only available on enterprise edition and for the Bun language.
 
 <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"
+		title="Settings"
+		description="Each script has metadata & settings associated with it, enabling it to be defined and configured in depth."
+		href="/docs/script_editor/settings"
 	/>
 </div>
 
@@ -116,7 +122,7 @@ 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
+the editor itself. The right-side [previews the UI](../../../core_concepts/6_auto_generated_uis/index.mdx) 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.
 
@@ -213,20 +219,16 @@ $argument_name = "Its default value"
 	/>
 </div>
 
-Now let's go to the last step: the "Customise" settings.
+Now let's go to the last step: the "Generated UI" settings.
 
-## Customize Settings
+## Customize UI
 
-In this menu, you can:
+From the Settings menu, the "Generated UI" tab lets you customize the script's arguments.
 
-- 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.
+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](./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"
@@ -234,17 +236,20 @@ each script version is uniquely identified by a hash.
 		href="/docs/script_editor/script_kinds"
 	/>
 	<DocCard
-		title="Customize Arguments"
+		title="Customize UI"
 		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"
+		href="/docs/script_editor/customize_ui"
 	/>
 </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
+We're done! 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.
 
+Note that Scripts are versioned in Windmill, and
+each script version is uniquely [identified by a hash](../../../script_editor/versioning.mdx)
+
 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.
@@ -307,9 +312,9 @@ For each script, a UI is autogenerated from the jsonchema inferred from the scri
 		href="/docs/core_concepts/auto_generated_uis"
 	/>
 	<DocCard
-		title="Customize Arguments"
+		title="Customize UI"
 		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"
+		href="/docs/script_editor/customize_ui"
 	/>
 </div>
 
diff --git a/docs/getting_started/0_scripts_quickstart/5_sql_quickstart/customize_sql.png b/docs/getting_started/0_scripts_quickstart/5_sql_quickstart/customize_sql.png
new file mode 100644
index 000000000..ea0664aaa
Binary files /dev/null and b/docs/getting_started/0_scripts_quickstart/5_sql_quickstart/customize_sql.png differ
diff --git a/docs/getting_started/0_scripts_quickstart/5_sql_quickstart/index.mdx b/docs/getting_started/0_scripts_quickstart/5_sql_quickstart/index.mdx
index 26d313278..35415b12e 100644
--- a/docs/getting_started/0_scripts_quickstart/5_sql_quickstart/index.mdx
+++ b/docs/getting_started/0_scripts_quickstart/5_sql_quickstart/index.mdx
@@ -27,7 +27,7 @@ Windmill supports [PostgreSQL](https://www.postgresql.org/), [MySQL](https://www
 Windmill provides integrations with many different apps and services with the use
 of [Resources](../../../core_concepts/3_resources_and_types/index.mdx). Resources are rich objects in JSON that allow to store configuration and credentials.
 
-Each Resource has a _Resource Type_ ([PostgreSQL](https://hub.windmill.dev/resource_types/6/postgresql), [MySQL](https://hub.windmill.dev/resource_types/111/mysql), [BigQuery](https://hub.windmill.dev/resource_types/108/bigquery), [Snowflake](https://hub.windmill.dev/resource_types/107/snowflake))
+Each Resource has a _Resource Type_ ([PostgreSQL](https://hub.windmill.dev/resource_types/114/postgresql), [MySQL](https://hub.windmill.dev/resource_types/111/mysql), [BigQuery](https://hub.windmill.dev/resource_types/108/bigquery), [Snowflake](https://hub.windmill.dev/resource_types/107/snowflake))
 that defines the schema that the resource of this type needs to implement. Schemas implement the
 [JSON Schema specification](https://json-schema.org/).
 
@@ -234,7 +234,7 @@ click on the "+Script" button. Name the Script, give it a summary, and select yo
 
 ![Script creation first step](../../../assets/integrations/sql_new_script.png)
 
-You can also give more details to your script, in the [metadata section](../../../script_editor/metadata.mdx), you can also get back to that later at any point.
+You can also give more details to your script, in the [settings section](../../../script_editor/settings.mdx), you can also get back to that later at any point.
 
 ### PostgreSQL
 
@@ -357,18 +357,22 @@ After you're done, click on "[Deploy](../../../core_concepts/0_draft_and_deploy/
 
 ## Customize your script
 
-Feel free to customize your script's metadata ([path](../../../core_concepts/16_roles_and_permissions/index.mdx#path), name, description, [concurrency limits](../../../script_editor/concurrency_limit.mdx), [worker group](../../../script_editor/worker_group_tag.mdx)) and [arguments](../../../script_editor/customize_arguments.mdx).
+Feel free to customize your script's metadata ([path](../../../core_concepts/16_roles_and_permissions/index.mdx#path), name, description),
+runtime ([concurrency limits](../../../script_editor/concurrency_limit.mdx), [worker group](../../../script_editor/worker_group_tag.mdx),
+[cache](../../../core_concepts/24_caching/index.md), [dedicated workers](../../../core_concepts/25_dedicated_workers/index.mdx)) and [generated UI](../../../script_editor/customize_ui.mdx).
+
+![Customize SQL](./customize_sql.png "Customize SQL")
 
 <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"
+		title="Settings"
+		description="Each script has metadata & settings associated with it, enabling it to be defined and configured in depth."
+		href="/docs/script_editor/settings"
 	/>
 	<DocCard
-		title="Customize Arguments"
+		title="Customize UI"
 		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"
+		href="/docs/script_editor/customize_ui"
 	/>
 </div>
 
@@ -404,9 +408,9 @@ For each script, a UI is autogenerated from the jsonchema inferred from the scri
 		href="/docs/core_concepts/auto_generated_uis"
 	/>
 	<DocCard
-		title="Customize Arguments"
+		title="Customize UI"
 		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"
+		href="/docs/script_editor/customize_ui"
 	/>
 </div>
 
diff --git a/docs/getting_started/0_scripts_quickstart/6_rest_grapqhql_quickstart/create_script_rest.png b/docs/getting_started/0_scripts_quickstart/6_rest_grapqhql_quickstart/create_script_rest.png
index d95f2ce08..be352c799 100644
Binary files a/docs/getting_started/0_scripts_quickstart/6_rest_grapqhql_quickstart/create_script_rest.png and b/docs/getting_started/0_scripts_quickstart/6_rest_grapqhql_quickstart/create_script_rest.png differ
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 bd163ef30..775ae897f 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
@@ -37,7 +37,7 @@ Scripts are the basic building blocks in Windmill. They can be [run and schedule
 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).
+- [Settings](#settings): settings & 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`.
 
@@ -55,11 +55,11 @@ export async function main() {
 }
 ```
 
-## Metadata
+## Settings
 
 ![New script](./create_script_rest.png)
 
-Each script has metadata associated with it, enabling it to be defined and configured in depth.
+As part of the settings menu, 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.
@@ -68,16 +68,22 @@ Each script has metadata associated with it, enabling it to be defined and confi
   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)
+- **Description** is where you can give instructions through the [auto-generated UI](../../../core_concepts/6_auto_generated_uis/index.mdx)
   to users on how to run your Script. It supports markdown.
+- **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).
+
+This menu also has additional settings, such as:
+
 - **[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).
+- **[Cache](../../../core_concepts/24_caching/index.md)** to cache the results for each possible inputs for a given time.
+- **[Dedicated Workers](../../../core_concepts/25_dedicated_workers/index.mdx)** to run the script on, to run the script at native speed. Only available on enterprise edition and for the Bun language.
 
 <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"
+		title="Settings"
+		description="Each script has metadata & settings associated with it, enabling it to be defined and configured in depth."
+		href="/docs/script_editor/settings"
 	/>
 </div>
 
@@ -86,7 +92,7 @@ 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
+the editor itself. The right-side [previews the UI](../../../core_concepts/6_auto_generated_uis/index.mdx) 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.
 
@@ -129,7 +135,7 @@ benefits from a highly efficient runtime.
 
 Replace the `<jsonplaceholder>` URL with the API endpoint of your choice and customize the headers object according to your fetch requirements.
 
-REST scripts benefit from the [auto-generated UI](../../../core_concepts/6_auto_generated_uis/index.md) capabilities of any Windmill script.
+REST scripts benefit from the [auto-generated UI](../../../core_concepts/6_auto_generated_uis/index.mdx) capabilities of any Windmill script.
 The arguments of the `main` function are used for generating 1. the input spec of the Script,
 and 2. the frontend that you see when running the Script as a standalone app.
 Type annotations are used to generate the UI form, and help pre-validate
@@ -214,7 +220,7 @@ To trigger each GraphQL script, an input named 'api' will be required. This is a
 </div>
 
 The arguments of the query will be used for generating 1. the input spec of the Script,
-and 2. the frontend that you see when running the Script with an [auto-generated UI](../../../core_concepts/6_auto_generated_uis/index.md).
+and 2. the frontend that you see when running the Script with an [auto-generated UI](../../../core_concepts/6_auto_generated_uis/index.mdx).
 Type annotations are used to generate the UI form, and help pre-validate
 inputs. While not mandatory, they are highly recommended. You can customize the UI in later steps (but not change the input type).
 
@@ -228,20 +234,16 @@ The UI is available in the script editor to [test your code](../../../core_conce
 
 <br/>
 
-> In the example above, a [GraphQL resource](https://hub.windmill.dev/resource_types/112/graphql) is used with details on base URL and bearer token. Also was used the [auto-generated UI](../../../core_concepts/6_auto_generated_uis/index.md) to fill the argument `login`.
+> In the example above, a [GraphQL resource](https://hub.windmill.dev/resource_types/112/graphql) is used with details on base URL and bearer token. Also was used the [auto-generated UI](../../../core_concepts/6_auto_generated_uis/index.mdx) to fill the argument `login`.
 
-## Customize Settings
+## Customize UI
 
-In the "Customize settings" menu, you can:
+From the Settings menu, the "Generated UI" tab lets you customize the script's arguments.
 
-- 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.
+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 TypeScript](./customize_graphql.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"
@@ -249,17 +251,20 @@ each script version is uniquely identified by a hash.
 		href="/docs/script_editor/script_kinds"
 	/>
 	<DocCard
-		title="Customize Arguments"
+		title="Customize UI"
 		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"
+		href="/docs/script_editor/customize_ui"
 	/>
 </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
+We're done! 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.
 
+Note that Scripts are versioned in Windmill, and
+each script version is uniquely [identified by a hash](../../../script_editor/versioning.mdx)
+
 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.
@@ -308,9 +313,9 @@ For each script, a UI is autogenerated from the jsonchema inferred from the scri
 		href="/docs/core_concepts/auto_generated_uis"
 	/>
 	<DocCard
-		title="Customize Arguments"
+		title="Customize UI"
 		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"
+		href="/docs/script_editor/customize_ui"
 	/>
 </div>
 
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
index 9ac956222..3155e3097 100644
--- a/docs/getting_started/0_scripts_quickstart/7_docker_quickstart/index.mdx
+++ b/docs/getting_started/0_scripts_quickstart/7_docker_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).
-- [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).
+- [Settings](#settings): settings & 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`.
 
@@ -73,11 +73,11 @@ To set-up Docker, see:
 From the Home page of Windmill App, click `+Script`. This will take you to the
 first step of script creation: Metadata.
 
-### Metadata
+## Settings
 
 ![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.
+As part of the settings menu, 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.
@@ -86,16 +86,22 @@ Each script has metadata associated with it, enabling it to be defined and confi
   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)
+- **Description** is where you can give instructions through the [auto-generated UI](../../../core_concepts/6_auto_generated_uis/index.mdx)
   to users on how to run your Script. It supports markdown.
+- **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).
+
+This menu also has additional settings, such as:
+
 - **[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).
+- **[Cache](../../../core_concepts/24_caching/index.md)** to cache the results for each possible inputs for a given time.
+- **[Dedicated Workers](../../../core_concepts/25_dedicated_workers/index.mdx)** to run the script on, to run the script at native speed. Only available on enterprise edition and for the Bun language.
 
 <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"
+		title="Settings"
+		description="Each script has metadata & settings associated with it, enabling it to be defined and configured in depth."
+		href="/docs/script_editor/settings"
 	/>
 </div>
 
@@ -104,7 +110,7 @@ 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
+the editor itself. The right-side [previews the UI](../../../core_concepts/6_auto_generated_uis/index.mdx) 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.
 
@@ -179,19 +185,18 @@ signature. Run a test (`Ctrl` + `Enter`) to verify everything works.
 	/>
 </div>
 
-Now let's go to the last step: the "Customise" settings.
+Now let's go to the last step: the "Generated UI" settings.
 
-### Customize Settings
+## Customize UI
 
-In this menu, you can:
+From the Settings menu, the "Generated UI" tab lets you customize the script's arguments.
 
-- 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.
+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.
+each script version is uniquely [identified by a hash](../../../script_editor/versioning.mdx)
 
 <div class="grid grid-cols-2 gap-6 mb-4">
 	<DocCard
@@ -200,9 +205,9 @@ each script version is uniquely identified by a hash.
 		href="/docs/script_editor/script_kinds"
 	/>
 	<DocCard
-		title="Customize Arguments"
+		title="Customize UI"
 		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"
+		href="/docs/script_editor/customize_ui"
 	/>
 </div>
 
@@ -259,9 +264,9 @@ For each script, a UI is autogenerated from the jsonchema inferred from the scri
 		href="/docs/core_concepts/auto_generated_uis"
 	/>
 	<DocCard
-		title="Customize Arguments"
+		title="Customize UI"
 		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"
+		href="/docs/script_editor/customize_ui"
 	/>
 </div>
 
diff --git a/docs/getting_started/6_flows_quickstart/index.mdx b/docs/getting_started/6_flows_quickstart/index.mdx
index 04fb64e33..64b4b60bd 100644
--- a/docs/getting_started/6_flows_quickstart/index.mdx
+++ b/docs/getting_started/6_flows_quickstart/index.mdx
@@ -212,7 +212,7 @@ You can find all the flows' features in their [dedicated section](../../flows/1_
 
 There are several ways to trigger a flow with Windmill.
 
-1. The most direct one is from the [autogenerated UI provided by Windmill](../../core_concepts/6_auto_generated_uis/index.md). It is the one you will see from the flow editor.
+1. The most direct one is from the [autogenerated UI provided by Windmill](../../core_concepts/6_auto_generated_uis/index.mdx). It is the one you will see from the flow editor.
 2. A similar but more customized way is to use Windmill Apps using the [App editor](../7_apps_quickstart/index.mdx).
 3. We saw above that you can trigger flows using [schedules](../../core_concepts/1_scheduling/index.md) that you can check from the [Runs](../../core_concepts/5_monitor_past_and_future_runs/index.mdx) page. One special way to use scheduling is to combine it with [trigger scripts](../../flows/10_flow_trigger.md).
 4. [Execute flows from the CLI](../../advanced/3_cli/index.mdx) to trigger your flows from your terminal.
@@ -242,6 +242,6 @@ You don't have to explore all flows editor possibilities at once. At each step,
 
 <br/>
 
-When you're done, [deploy](../../core_concepts/0_draft_and_deploy/index.mdx) your flow, schedule it, [create and app from it](../../core_concepts/6_auto_generated_uis/index.md#automatically-generated-apps), or even [publish it to Hub](../../misc/1_share_on_hub/index.md).
+When you're done, [deploy](../../core_concepts/0_draft_and_deploy/index.mdx) your flow, schedule it, [create and app from it](../../core_concepts/6_auto_generated_uis/index.mdx#automatically-generated-apps), or even [publish it to Hub](../../misc/1_share_on_hub/index.md).
 
 Follow our [detailed section](../../flows/1_flow_editor.mdx) on the Flow Editor for more information.
diff --git a/docs/getting_started/7_apps_quickstart/index.mdx b/docs/getting_started/7_apps_quickstart/index.mdx
index 9bf2ea7d7..f962111b6 100644
--- a/docs/getting_started/7_apps_quickstart/index.mdx
+++ b/docs/getting_started/7_apps_quickstart/index.mdx
@@ -18,7 +18,7 @@ Welcome to the Apps Quickstart! This page will provide you with the necessary kn
 
 <br />
 
-Although Windmill provides **[auto-generated UIs to scripts and flows](../../core_concepts/6_auto_generated_uis/index.md)**, you can build your own internal applications designed to your needs. Either with our integrated [app editor](../../apps/0_app_editor/index.mdx), or by [importing your own React/Vue/Svelte apps](../../react_vue_svelte_apps/index.md).
+Although Windmill provides **[auto-generated UIs to scripts and flows](../../core_concepts/6_auto_generated_uis/index.mdx)**, you can build your own internal applications designed to your needs. Either with our integrated [app editor](../../apps/0_app_editor/index.mdx), or by [importing your own React/Vue/Svelte apps](../../react_vue_svelte_apps/index.md).
 
 <div class="grid grid-cols-2 gap-6 mb-4">
 	<DocCard
diff --git a/docs/getting_started/8_trigger_scripts/index.mdx b/docs/getting_started/8_trigger_scripts/index.mdx
index 42645d723..74b77e4e1 100644
--- a/docs/getting_started/8_trigger_scripts/index.mdx
+++ b/docs/getting_started/8_trigger_scripts/index.mdx
@@ -77,7 +77,7 @@ Windmill provides a WYSIWYG app editor. It allows you to build your own UI with
 	/>
 </div>
 
-You can also [automatically generate](../../core_concepts/6_auto_generated_uis/index.md#automatically-generated-apps) a dedicated app to execute your script.
+You can also [automatically generate](../../core_concepts/6_auto_generated_uis/index.mdx#automatically-generated-apps) a dedicated app to execute your script.
 
 <video
     className="border-2 rounded-xl object-cover w-full h-full dark:border-gray-800"
diff --git a/docs/getting_started/9_trigger_flows/index.mdx b/docs/getting_started/9_trigger_flows/index.mdx
index d068186ce..f790a1ed2 100644
--- a/docs/getting_started/9_trigger_flows/index.mdx
+++ b/docs/getting_started/9_trigger_flows/index.mdx
@@ -72,7 +72,7 @@ Windmill provides a WYSIWYG app editor. It allows you to build your own UI with
 	/>
 </div>
 
-You can also [automatically generate](../../core_concepts/6_auto_generated_uis/index.md#automatically-generated-apps) a dedicated app to execute your flow.
+You can also [automatically generate](../../core_concepts/6_auto_generated_uis/index.mdx#automatically-generated-apps) a dedicated app to execute your flow.
 
 <video
     className="border-2 rounded-xl object-cover w-full h-full dark:border-gray-800"
diff --git a/docs/integrations/neon.md b/docs/integrations/neon.md
index d05234701..5c39eb8cc 100644
--- a/docs/integrations/neon.md
+++ b/docs/integrations/neon.md
@@ -19,7 +19,7 @@ As a Postgres database service provider, Neon.tech follows the regular Postgres
 
 3. Get a [Connection string](https://neon.tech/docs/connect/query-with-psql-editor). You can obtain it connection string from the Connection Details widget on the Neon Dashboard: select a branch, a role, and the database you want to connect to and a connection string will be constructed for you.
 
-4. From Windmill, add your Neon.tech connection string as a [Postgresql resource](https://hub.windmill.dev/resource_types/6/postgresql) and [Execute queries](https://hub.windmill.dev/scripts/postgresql/1294/execute-query-and-return-results-postgresql).
+4. From Windmill, add your Neon.tech connection string as a [Postgresql resource](https://hub.windmill.dev/resource_types/114/postgresql) and [Execute queries](https://hub.windmill.dev/scripts/postgresql/1294/execute-query-and-return-results-postgresql).
 
 :::tip
 
diff --git a/docs/misc/12_support_and_sla/index.mdx b/docs/misc/12_support_and_sla/index.mdx
index 2bb9f50c7..e13e77474 100644
--- a/docs/misc/12_support_and_sla/index.mdx
+++ b/docs/misc/12_support_and_sla/index.mdx
@@ -42,7 +42,7 @@ Our SLA defines the expected response times for each priority level:
 
 ## Security
 
-Windmill adheres to SOC 2 Type II compliance. We are currently in the process of completing our Type II audit to further enhance our security measures. As part of our commitment to maintaining a secure platform, we conduct regular penetration testing. Any identified vulnerabilities are treated with utmost priority (P0) and addressed promptly, with same-day fixes being our standard practice. We prioritize the security of our users and strive to provide a safe environment for their automation needs.
+Windmill adheres to SOC 2 Type II compliance. As part of our commitment to maintaining a secure platform, we conduct regular penetration testing. Any identified vulnerabilities are treated with utmost priority (P0) and addressed promptly, with same-day fixes being our standard practice. We prioritize the security of our users and strive to provide a safe environment for their automation needs.
 
 ## Contacting Support
 
diff --git a/docs/script_editor/concurrency_limit.mdx b/docs/script_editor/concurrency_limit.mdx
index 7ea178dd3..0514f8159 100644
--- a/docs/script_editor/concurrency_limit.mdx
+++ b/docs/script_editor/concurrency_limit.mdx
@@ -12,6 +12,6 @@ The Concurrency Limits feature allows you to define concurrency limits for scrip
 
 The Concurrency Limit operates globally and across flow runs. It involves two key parameters: "Maximum number of runs" and the "Per time window (seconds)."
 
-Concurrency limit can be set from the metadata menu.
+Concurrency limit can be set from the Settings menu.
 
 When jobs reach the concurrency limit, they are automatically queued for execution at the next available optimal slot given the time window.
diff --git a/docs/script_editor/customize_arguments.mdx b/docs/script_editor/customize_ui.mdx
similarity index 92%
rename from docs/script_editor/customize_arguments.mdx
rename to docs/script_editor/customize_ui.mdx
index 427a00075..defcb6077 100644
--- a/docs/script_editor/customize_arguments.mdx
+++ b/docs/script_editor/customize_ui.mdx
@@ -1,8 +1,10 @@
 import DocCard from '@site/src/components/DocCard';
 
-# Customize Arguments
+# Customize UI
 
-Some arguments' types can be given advanced settings that will affect the inputs' [auto-generated UI](../core_concepts/6_auto_generated_uis/index.md) and [JSON Schema](../core_concepts/13_json_schema_and_parsing/index.md).
+Some arguments' types can be given advanced settings that will affect the inputs' [auto-generated UI](../core_concepts/6_auto_generated_uis/index.mdx) and [JSON Schema](../core_concepts/13_json_schema_and_parsing/index.md).
+
+From the script's [Settings](./settings.mdx), pick "Generated UI" tab.
 
 Here is an example on how to define a python list as an enum of strings using the `Customize` menu.
 
diff --git a/docs/script_editor/index.mdx b/docs/script_editor/index.mdx
index 7cad28e4a..0d04c45b5 100644
--- a/docs/script_editor/index.mdx
+++ b/docs/script_editor/index.mdx
@@ -80,9 +80,9 @@ The Script Editor is made of the following features:
 
 <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"
+		title="Settings"
+		description="Each script has metadata & settings associated with it, enabling it to be defined and configured in depth."
+		href="/docs/script_editor/settings"
 	/>
     <DocCard
 		title="Script Kinds"
@@ -90,9 +90,9 @@ The Script Editor is made of the following features:
 		href="/docs/script_editor/script_kinds"
 	/>
     <DocCard
-		title="Customize Arguments"
+		title="Customize UI"
 		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"
+		href="/docs/script_editor/customize_ui"
     />
     <DocCard
 		title="Versioning"
diff --git a/docs/script_editor/script_kinds.mdx b/docs/script_editor/script_kinds.mdx
index 7f1f32cad..9f986fd25 100644
--- a/docs/script_editor/script_kinds.mdx
+++ b/docs/script_editor/script_kinds.mdx
@@ -5,6 +5,8 @@ import DocCard from '@site/src/components/DocCard';
 You can attach additional functionalities to Scripts by specializing them into
 specific Script kinds.
 
+From the [Settings](./settings.mdx) of a script, the "Metadata" tab lets you define the following Script kinds:
+
 ## Actions
 
 Actions - or Common Scripts - are the basic building blocks for the flows.
diff --git a/docs/script_editor/metadata.mdx b/docs/script_editor/settings.mdx
similarity index 99%
rename from docs/script_editor/metadata.mdx
rename to docs/script_editor/settings.mdx
index 1094b7881..31e25c1f0 100644
--- a/docs/script_editor/metadata.mdx
+++ b/docs/script_editor/settings.mdx
@@ -1,6 +1,6 @@
 import DocCard from '@site/src/components/DocCard';
 
-# Metadata
+# Settings
 
 Each script has metadata associated with it, enabling it to be defined and configured in depth.
 
diff --git a/docs/script_editor/worker_group_tag.mdx b/docs/script_editor/worker_group_tag.mdx
index e20f65a02..523f3b66a 100644
--- a/docs/script_editor/worker_group_tag.mdx
+++ b/docs/script_editor/worker_group_tag.mdx
@@ -4,7 +4,7 @@ import DocCard from '@site/src/components/DocCard';
 
 Scripts can be assigned custom [worker groups](../core_concepts/9_worker_groups/index.mdx) for efficient execution on different machines with varying specifications.
 
-For scripts saved on the script editor, select the corresponding worker group tag in the metadata section.
+For scripts saved on the script editor, select the corresponding worker group tag in the [settings](../script_editor/settings.mdx) section.
 
 ![Worker group tag](../core_concepts/9_worker_groups/select_script_builder.png.webp)
 
diff --git a/sidebars.js b/sidebars.js
index 84b32e264..ebbd04e67 100644
--- a/sidebars.js
+++ b/sidebars.js
@@ -88,9 +88,9 @@ const sidebars = {
 						id: 'script_editor/index'
 					},
 					items: [
-						'script_editor/metadata',
+						'script_editor/settings',
 						'script_editor/script_kinds',
-						'script_editor/customize_arguments',
+						'script_editor/customize_ui',
 						'script_editor/versioning',
 						'script_editor/worker_group_tag',
 						'script_editor/concurrency_limit',
diff --git a/static/videos/copy_style_global_css.mp4 b/static/videos/copy_style_global_css.mp4
index 37cc1fe71..04c85d405 100644
Binary files a/static/videos/copy_style_global_css.mp4 and b/static/videos/copy_style_global_css.mp4 differ
diff --git a/static/videos/global-css.mp4 b/static/videos/global-css.mp4
index b17adb63a..fcd07eee6 100644
Binary files a/static/videos/global-css.mp4 and b/static/videos/global-css.mp4 differ