Inflight variable and parameters doc updates

src/pages/docs/platform-hub/templates/parameters.md

@@ -1,7 +1,7 @@
 ---
 layout: src/layouts/Default.astro
 pubDate: 2026-03-05
-modDate: 2026-09-21
+modDate: 2026-11-04
 title: Template parameters
 subtitle: A reference for parameters in Platform Hub templates
 icon: fa-solid fa-layer-group
@@ -41,7 +41,7 @@ Templates can manage the following as parameters:
 - Project
 - A previous step name (process templates only)
 
-To create a parameter, navigate to **Parameters** on a template and add a new parameter.
+To create a parameter, navigate to **Parameters** on a template and select **Add parameter**. You can also create a parameter from the step that uses it. See [Create a parameter from a step](/docs/platform-hub/templates/process-templates#create-parameter-from-step) for process templates, and [Create a parameter or variable from a step](/docs/platform-hub/templates/project-templates#create-from-step) for project templates.
 
 ## Parameter values
 

src/pages/docs/platform-hub/templates/process-templates/index.md

@@ -1,7 +1,7 @@
 ---
 layout: src/layouts/Default.astro
 pubDate: 2025-09-23
-modDate: 2026-03-05
+modDate: 2026-11-04
 title: Process Templates
 subtitle: An overview of Process Templates
 icon: fa-solid fa-layer-group
@@ -52,12 +52,41 @@ Parameters help you easily manage and apply the correct values during a deployme
 
 For a full reference of supported parameter types and default values, see [Template parameters](/docs/platform-hub/templates/parameters).
 
-To create a parameter, navigate to the **Parameters** tab on a process template and add a new parameter.
+To create a parameter, navigate to the **Parameters** tab on a process template and select **Add parameter**. You can also [create a parameter from the step that uses it](#create-parameter-from-step).
 
 :::figure
 ![The parameters section in a process template](/docs/img/platform-hub/process-template-parameters.png)
 :::
 
+### Create a parameter from a step {#create-parameter-from-step}
+
+Create a parameter while you configure a step, so you don't have to switch to the **Parameters** tab and back. The parameter is added to the template and inserted into the field you're working in.
+
+To create a parameter from a step:
+
+1. In your process template, open the step you want to configure.
+2. In a text field or the script editor, select the **Insert a parameter** button (**#\{\}**).
+3. In the search box, enter a name for the parameter.
+4. Select the **Create Parameter** button, which shows the name you entered. The **Create Parameter** drawer opens with **Name** already filled in.
+5. Enter a **Label** for the parameter.
+6. Optionally, enter **Help text** and a **Default value**.
+7. Select **Create and Insert**.
+8. Commit your changes to the process template.
+
+:::figure
+![The parameters drawer in a process template](/docs/img/platform-hub/process-template-parameters-drawer.png)
+:::
+
+The parameter appears on the **Parameters** tab, and the field you started from references it.
+
+:::div{.hint}
+A new parameter isn't saved until you commit the process template. If you discard your changes, the parameter is discarded with them.
+:::
+
+:::div{.hint}
+Fields that take a specific kind of value, such as an account, worker pool, environment, or target tag field, have an **Add** button next to the field instead. It opens the same drawer, offers only the parameter type the field accepts, and selects the new parameter in the field.
+:::
+
 ### Sensitive parameter defaults
 
 :::div{.hint}
@@ -126,3 +155,7 @@ To define a simple deployment process in Octopus that executes a hello world scr
 17. Add any steps before or after the process template
 
 You can now deploy this process to say "Hello, World!".
+
+## Version notes
+
+- Creating a parameter from a step in the process editor is available from [PLACEHOLDER: the first self-hosted Octopus Server version that includes creating variables and parameters from the process editor, with build number — needs: release version from Travis].

src/pages/docs/platform-hub/templates/project-templates/index.md

@@ -1,7 +1,7 @@
 ---
 layout: src/layouts/Default.astro
 pubDate: 2026-03-05
-modDate: 2026-10-12
+modDate: 2026-11-04
 title: Project templates
 subtitle: An overview of project templates
 icon: fa-solid fa-layer-group
@@ -127,7 +127,7 @@ If your license changes after you've published a template version, Octopus doesn
 Project templates don't yet support parameter scoping or sensitive parameter default values. We're still shaping how parameters, variables, and scoping work together and expect this area to evolve. We'd love your [feedback](#feedback).
 :::
 
-To create a parameter, navigate to **Parameters** on your project template and add a new parameter.
+To create a parameter, navigate to **Parameters** on your project template and select **Add parameter**. You can also [create a parameter or variable from the step that uses it](#create-from-step).
 
 :::figure
 ![The Parameters tab in a project template](/docs/img/platform-hub/project-templates/project-templates-parameters.png)
@@ -171,6 +171,44 @@ Scoping is fixed at the template level. The same scoping rules apply to every pr
 ![The Variables tab in a project template](/docs/img/platform-hub/project-templates/project-templates-variables.png)
 :::
 
+## Create a parameter or variable from a step {#create-from-step}
+
+Create a parameter or variable while you configure a step in the template's deployment process, so you don't have to switch to **Parameters** or **Variables** and back. Whichever you create is inserted into the field you're working in.
+
+The **Create Parameter Value** drawer asks you to choose a **Type**:
+
+- **Variable**: the value is fixed by the project template, and every project created from it gets the same value.
+- **Parameter**: the value is supplied by each project that uses the template.
+
+To create a parameter or variable from a step:
+
+1. In your project template, open the step you want to configure.
+2. In a text field or the script editor, select the **Insert a variable or parameter** button (**#\{\}**).
+3. In the search box, enter a name for the parameter or variable.
+4. Select the **Create Variable/Parameter** button, which shows the name you entered. The **Create Parameter Value** drawer opens.
+5. In **Type**, select **Variable** or **Parameter**.
+6. Enter the details for the value. A variable takes a value and optional scopes. A parameter takes a **Label** and optional **Help text** and **Default value**.
+7. Select **Create and Insert**.
+8. Commit your changes to the project template.
+
+:::figure
+![The parameters/variables drawer in a project template](/docs/img/platform-hub/project-template-parameters-variable-drawer.png)
+:::
+
+The new variable appears under **Variables**, or the new parameter under **Parameters**, and the field you started from references it.
+
+:::div{.hint}
+A variable is committed to the template's branch as soon as you select **Create and Insert**. A parameter isn't saved until you commit your other changes to the template. Because the variable is saved first, you can only scope it to parameters that have already been committed.
+:::
+
+:::div{.hint}
+Some values can only be supplied by the project, such as worker pools and target tags. For those, the drawer skips the **Type** choice and creates a parameter.
+:::
+
+:::div{.hint}
+On a protected branch you can still create a parameter, but not a variable. On a tag or commit you can't create a variable. Switch to an unprotected branch to create one.
+:::
+
 ## Project settings
 
 Project templates let you set a few project-level defaults that flow through to every project created from the template. Configure these in **Settings** on the project template.
@@ -216,5 +254,7 @@ Project templates are in Public Preview and we're actively shaping how the featu
 
 ## Version notes
 
+- Creating a parameter or variable from a step in the process editor is available from [PLACEHOLDER: the first self-hosted Octopus Server version that includes creating variables and parameters from the process editor, with build number — needs: release version from Travis].
+
 - [Channels](#channels) and [Lifecycles](#lifecycles) in Project Templates are available from Octopus Server version `2026.4.4005`.
 - Retention policies in project template lifecycles are applied from Octopus Server version `2026.4.7884`.

src/pages/docs/platform-hub/templates/project-templates/using-project-templates.md

@@ -1,7 +1,7 @@
 ---
 layout: src/layouts/Default.astro
 pubDate: 2026-03-16
-modDate: 2026-10-12
+modDate: 2026-11-04
 title: Templated projects
 subtitle: How to create and manage projects from a project template
 icon: fa-solid fa-layer-group
@@ -68,6 +68,8 @@ Template values are the parameters the template owner has defined to let you cus
 ![The Template values page for a templated project](/docs/img/platform-hub/project-templates/templated-project-values.png)
 :::
 
+To use a project variable as a template value, select the **Insert a variable** button (**#\{\}**) next to the field. If the variable doesn't exist yet, select **Create Variable** to create it without leaving the page. It's saved to the project's variables and inserted into the field. For the fields in the drawer, see [Create a variable from the process editor](/docs/projects/variables/getting-started#create-from-process-editor).
+
 After you've provided the required values, you can create a release as usual.
 
 :::div{.hint}
@@ -104,3 +106,7 @@ When a new version of the template is published, you'll receive the update. How
 ## Limitations
 
 Some features are not yet supported for templated projects. For a full list, see [Troubleshooting](/docs/platform-hub/templates/project-templates/troubleshooting).
+
+## Version notes
+
+- Creating a project variable from the **Template values** page is available from [PLACEHOLDER: the first self-hosted Octopus Server version that includes creating variables and parameters from the process editor, with build number — needs: release version from Travis].

src/pages/docs/projects/variables/getting-started.mdx

@@ -1,7 +1,7 @@
 ---
 layout: src/layouts/Default.astro
 pubDate: 2024-03-06
-modDate: 2024-08-28
+modDate: 2026-11-04
 title: Getting started with variables
 icon: fa-solid fa-play
 description: A guide to getting started with variables in Octopus Deploy.
@@ -46,6 +46,63 @@ In this example, we'll add a variable to a Hello World project that runs a scrip
 
 When a release of the project is deployed, the script step will run with the string *Hello, Test* on the Test environment, and with the string *Hello, Production*, on the Production environment.
 
+## Create a variable from the process editor \{#create-from-process-editor}
+
+You can create a project variable without leaving the step you're editing. The variable is saved to the project and inserted into the field you're working in, so you don't have to switch to **Project Variables** and back. This example builds the same Hello World script as the previous section.
+
+**Before you begin**
+
+You'll need:
+
+- A [project](/docs/projects) with a deployment process.
+- Permission to edit variables in the project.
+- For a project that stores its variables in Git, an unprotected branch selected in the branch switcher.
+- Octopus Deploy on version `>= REPLACE_ME_WITH_VERSION_NUMBER`.
+
+To create a variable from the process editor:
+
+1. In your project, select **Process**.
+2. Select **Add Step**, then select **Run a Script**.
+3. In the **Script** section, enter the following PowerShell into the script editor, followed by a space:
+
+   ```powershell
+   Write-Host
+   ```
+
+4. Select the **Insert a variable** button (**#\{\}**) in the script editor.
+5. In the search box, enter *Greeting*.
+6. Select **Create “Greeting” Variable**. The **Create Variable** drawer opens with *Greeting* already in **Variable name**.
+
+    :::figure
+    ![Using a variable in a Hello World script in Octopus Deploy](/docs/img/projects/variables/images/hello-world-greeting-script-process.png)
+    :::
+
+7. In **Type**, keep **Text** selected.
+8. In **Value 1**, enter *Hello, Test*.
+9. Select **Add scope**, then select **Environments**.
+10. In **Environments**, select *Test*.
+11. Select **Add Value**.
+12. In **Value 2**, enter *Hello, Production*.
+13. Select **Add scope**, then select **Environments**.
+14. In **Environments**, select *Production*.
+
+    :::figure
+    ![Using a variable in a Hello World script in Octopus Deploy](/docs/img/projects/variables/images/hello-world-greeting-script-process-creation.png)
+    :::
+
+15. Select **Create and Insert**.
+16. Select **Save** to save the step.
+
+The drawer closes, `$Greeting`(if using Powershell syntax) appears in the script after `Write-Host`, and *Greeting* is listed with both values under **Project Variables**. When a release is deployed, the step prints *Hello, Test* on the Test environment and *Hello, Production* on the Production environment.
+
+:::div{.hint}
+Fields that take a variable rather than free text, such as a certificate or account field, have their own **Create Variable** button next to the field. It opens the same drawer, offers only the variable types the field accepts, and selects the new variable in the field when you select **Create and Insert**.
+:::
+
+:::div{.hint}
+If your project stores variables in Git and you're viewing a protected branch, a tag, or a commit, the drawer is read-only. Switch to an unprotected branch to create the variable.
+:::
+
 ## Scoping variables \{#scoping-variables}
 
 The variables that you define for your projects in Octopus can be scoped in the following ways:
@@ -249,6 +306,10 @@ If you have many configuration settings for your application and are using a var
 
 If the answer to either question is yes, consider an external store for your variables. This might be a source control repository, a configuration management system, or a database.
 
+## Version notes
+
+- Creating a project variable from the process editor is available from [PLACEHOLDER: the first self-hosted Octopus Server version that includes creating variables from the process editor, with build number — needs: release version from Travis].
+
 ## Learn more
 
 - [Using variables in your scripts](/docs/deployments/custom-scripts)