Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions src/pages/docs/platform-hub/templates/index.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
layout: src/layouts/Default.astro
pubDate: 2026-03-05
modDate: 2026-03-06
modDate: 2026-09-03
title: Templates
subtitle: Reusable templates for processes and projects in Platform Hub
icon: fa-solid fa-layer-group
Expand All @@ -17,7 +17,7 @@ Platform Hub provides two types of templates that help you standardize and share

**[Process templates](/docs/platform-hub/templates/process-templates)** are reusable sets of deployment steps. Instead of copying and pasting deployment processes across projects, you define the steps once and share them. Teams can opt into using a process template within their deployment process, and can remove it if it no longer fits their needs.

**[Project templates](/docs/platform-hub/templates/project-templates)** give platform engineering teams a way to define a golden path for how projects are structured. The deployment process is defined by the template and can't be modified in projects based on it. Through parameters exposed by the platform team, project teams can deploy using their own packages, accounts, worker pools, and target tags, while the underlying process stays consistent across every project based on the template. Project templates are currently in Alpha, see the [installation guide](/docs/platform-hub/templates/project-templates/installation-guide) to get started.
**[Project templates](/docs/platform-hub/templates/project-templates)** give platform engineering teams a way to define a golden path for how projects are structured. The deployment process is defined by the template and can't be modified in projects based on it. Through parameters exposed by the platform team, project teams can deploy using their own packages, accounts, worker pools, and target tags, while the underlying process stays consistent across every project based on the template. Project templates are currently in Public Preview, see the [installation guide](/docs/platform-hub/templates/project-templates/installation-guide) to get started.

Both template types use [parameters](/docs/platform-hub/templates/parameters) to expose configurable inputs, letting you define what a project must supply while keeping the core template consistent across teams and spaces.

Expand Down
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
layout: src/layouts/Default.astro
pubDate: 2026-03-05
modDate: 2026-05-28
modDate: 2026-09-03
title: Troubleshooting
subtitle: Known issues and limitations for project templates
icon: fa-solid fa-layer-group
Expand Down Expand Up @@ -62,7 +62,7 @@ You can't clone a project template through the Octopus UI. To clone a template:

## Public API

The Alpha release doesn't support creating and managing project templates through the REST API. We're planning REST API support for a future release.
The Public Preview doesn't support creating and managing project templates through the REST API. We're planning REST API support for a future release.

## Losing access to an Octopus Enterprise license

Expand Down
Loading