Conversation
There was a problem hiding this comment.
Pull request overview
Adds/relocates Platform Hub “Templates” documentation, introducing Project Templates docs alongside Process Templates docs, and updates navigation/links to the new structure while preserving legacy URLs via redirects.
Changes:
- Add new Templates overview, parameters reference, and shared “Publishing and sharing” page.
- Add Project Templates docs (overview, best practices, troubleshooting) and related image assets.
- Move Process Templates docs under
/docs/platform-hub/templates/...and convert the old/docs/platform-hub/process-templates/...pages into redirects; update Platform Hub landing page links accordingly.
Reviewed changes
Copilot reviewed 18 out of 45 changed files in this pull request and generated 5 comments.
Show a summary per file
| File | Description |
|---|---|
| src/pages/docs/platform-hub/templates/publishing-and-sharing.md | New shared doc for saving/publishing/sharing templates |
| src/pages/docs/platform-hub/templates/project-templates/index.md | New Project Templates overview doc |
| src/pages/docs/platform-hub/templates/project-templates/best-practices.md | New Project Templates best practices doc |
| src/pages/docs/platform-hub/templates/project-templates/troubleshooting.md | New Project Templates troubleshooting doc |
| src/pages/docs/platform-hub/templates/process-templates/index.md | New Process Templates overview doc under Templates section |
| src/pages/docs/platform-hub/templates/process-templates/best-practices.md | New Process Templates best practices doc under Templates section |
| src/pages/docs/platform-hub/templates/process-templates/troubleshooting.md | New Process Templates troubleshooting doc under Templates section |
| src/pages/docs/platform-hub/templates/parameters.md | New shared parameter reference for template types |
| src/pages/docs/platform-hub/templates/index.md | New Templates landing/overview page |
| src/pages/docs/platform-hub/process-templates/index.md | Redirect legacy Process Templates overview URL to new location |
| src/pages/docs/platform-hub/process-templates/best-practices.md | Redirect legacy Process Templates best practices URL to new location |
| src/pages/docs/platform-hub/process-templates/troubleshooting.md | Redirect legacy Process Templates troubleshooting URL to new location |
| src/pages/docs/platform-hub/index.md | Update Platform Hub landing page to link to new templates structure and add Project Templates link |
| public/docs/img/platform-hub/project-templates/project-templates-usage.png.json | Image metadata for new Project Templates usage screenshot |
| public/docs/img/platform-hub/project-templates/project-templates-process-overview.png.json | Image metadata for new Project Templates process overview screenshot |
| public/docs/img/platform-hub/project-templates/project-templates-onboarding.png.json | Image metadata for new Project Templates onboarding screenshot |
| public/docs/img/platform-hub/project-templates/project-templates-list.png.json | Image metadata for new Project Templates list screenshot |
| public/docs/img/platform-hub/project-templates/project-template-process-editor.png.json | Image metadata for new Project Templates process editor screenshot |
| public/docs/i/600/platform-hub/project-templates/project-templates-usage.webp | 600px responsive image for Project Templates usage screenshot |
| public/docs/i/600/platform-hub/project-templates/project-templates-process-overview.webp | 600px responsive image for Project Templates process overview screenshot |
| public/docs/i/600/platform-hub/project-templates/project-templates-onboarding.webp | 600px responsive image for Project Templates onboarding screenshot |
| public/docs/i/600/platform-hub/project-templates/project-templates-list.webp | 600px responsive image for Project Templates list screenshot |
| public/docs/i/600/platform-hub/project-templates/project-template-process-editor.webp | 600px responsive image for Project Templates process editor screenshot |
| public/docs/i/1000/platform-hub/project-templates/project-templates-process-overview.webp | 1000px responsive image for Project Templates process overview screenshot |
| public/docs/i/1000/platform-hub/project-templates/project-templates-onboarding.webp | 1000px responsive image for Project Templates onboarding screenshot |
| public/docs/i/1000/platform-hub/project-templates/project-templates-list.webp | 1000px responsive image for Project Templates list screenshot |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
src/pages/docs/platform-hub/templates/project-templates/index.md
Outdated
Show resolved
Hide resolved
src/pages/docs/platform-hub/templates/project-templates/troubleshooting.md
Outdated
Show resolved
Hide resolved
|
I had a quick look at the test failure and when I pull the branch I can't see the image: Maybe you have it locally? |
Hey Steve, thanks for looking I managed to name it .../project-templates-parameters.png.png 🤦 should be right now. This is still a WIP, I meant to leave it as a draft sorry if the open setting triggered notifications/checks for you |
N-lson
left a comment
There was a problem hiding this comment.
Reviewed most of the files, will have a look at the rest in a bit
public/docs/i/2000/platform-hub/project-templates/project-template-selection.webp
Show resolved
Hide resolved
src/pages/docs/platform-hub/templates/process-templates/best-practices.md
Show resolved
Hide resolved
src/pages/docs/platform-hub/templates/project-templates/best-practices.md
Outdated
Show resolved
Hide resolved
src/pages/docs/platform-hub/templates/project-templates/best-practices.md
Outdated
Show resolved
Hide resolved
src/pages/docs/platform-hub/templates/project-templates/best-practices.md
Outdated
Show resolved
Hide resolved
src/pages/docs/platform-hub/templates/project-templates/using-project-templates.md
Outdated
Show resolved
Hide resolved
src/pages/docs/platform-hub/templates/project-templates/using-project-templates.md
Show resolved
Hide resolved
src/pages/docs/platform-hub/templates/project-templates/using-project-templates.md
Show resolved
Hide resolved
| - Username Password Account | ||
| - Worker Pool | ||
| - Package | ||
| - A previous step name |
There was a problem hiding this comment.
Always was, weird though I added it and then somehow lost it pulling the parameters page out into a shared one...
src/pages/docs/platform-hub/templates/publishing-and-sharing.md
Outdated
Show resolved
Hide resolved
|
@steve-fenton-octopus We're waiting a couple of days until we can enable this feature toggle for a majority of cloud customers and include a version/link for self hosted testing before merging this one. I haven't done a large docs PR in sometime, is this something your team would want to review before we merge? I'm assuming not because there's no branch protections, just wanted to check first though. |
fda2dbb to
fe692f2
Compare
|
|
||
| ## Deployment process | ||
|
|
||
| The deployment process defines the steps Octopus orchestrates when deploying a project created from this template. Each project template has a single deployment process, and you can use Octopus's built-in steps, Step Templates, Community Step Templates, and Process Templates to define it. |
There was a problem hiding this comment.
| The deployment process defines the steps Octopus orchestrates when deploying a project created from this template. Each project template has a single deployment process, and you can use Octopus's built-in steps, Step Templates, Community Step Templates, and Process Templates to define it. | |
| The deployment process defines the steps Octopus orchestrates when deploying a project created from this template. Each project template has a single deployment process, and you can use Octopus's built-in steps, step templates, community step templates, and process templates to define it. |
Adding this here as I think we may not be following the Octopus grammar rules for proper & common nouns. The way I interpret the style guide is that step templates, community step templates, and process templates are all collections of things and therefore should be lowercase.
This is only one example so I encourage you to self-edit one last time to make sure.
|
|
||
| ## Parameters | ||
|
|
||
| Parameters let you define the inputs a project must supply when it's created from the template. They're the mechanism for making a template flexible. Rather than hardcoding values that differ between teams or spaces, you expose them as parameters. |
There was a problem hiding this comment.
Should this read Parameters let you define the inputs a user must supply when they create a project from a template.
My reasoning is projects don't provide inputs, users do.
There was a problem hiding this comment.
Yep that reads much better, I was trying to make it clear that the values are provided within the project but the phrasing was off.
|
|
||
| Variables in a project template work the same way as project variables in a standard Octopus project. Any variable you define is available to the deployment and can be selected in steps. | ||
|
|
||
| Unlike parameters, projects can't override the variables set in a template. Use this for values that must be the same across every project, like accounts or credentials. If you want projects to supply their own value for something, expose it as a parameter instead. |
There was a problem hiding this comment.
This is another one where it might be easier to grasp the concept if we describe the action that the user is taking and the expected behaviour.
|
|
||
| ## Git repository structure | ||
|
|
||
| Octopus stores each project template as a folder in the Platform Hub Git repository. The folder name is a slug derived from the template name. Each folder contains four OCL files: |
There was a problem hiding this comment.
For OCL, should we add a link to the Configuration as Code docs?
MissedTheMark
left a comment
There was a problem hiding this comment.
Over-all, really good work! Couple of comments I'd like to see addressed before we merge this.
src/pages/docs/platform-hub/templates/project-templates/best-practices.md
Outdated
Show resolved
Hide resolved
|
|
||
| ### Write release notes when publishing a new version | ||
|
|
||
| Each published version can include release notes. Describe what changed, whether any parameters were added or removed, and what consumers need to do when updating. |
There was a problem hiding this comment.
I don't think we actually show release notes to the consumer anywhere? At least not on the 'update to version' part of project settings.
There was a problem hiding this comment.
Yeah they aren't shown anywhere, I think it's still good to include as a best practice for when we do display them.
src/pages/docs/platform-hub/templates/project-templates/index.md
Outdated
Show resolved
Hide resolved
src/pages/docs/platform-hub/templates/project-templates/index.md
Outdated
Show resolved
Hide resolved
src/pages/docs/platform-hub/templates/project-templates/installation-guide.md
Outdated
Show resolved
Hide resolved
src/pages/docs/platform-hub/templates/project-templates/troubleshooting.md
Show resolved
Hide resolved
src/pages/docs/platform-hub/templates/project-templates/troubleshooting.md
Show resolved
Hide resolved
src/pages/docs/platform-hub/templates/project-templates/using-project-templates.md
Show resolved
Hide resolved
| ## Future direction | ||
|
|
||
| We're still shaping what project templates can do, and there are a few areas we're actively thinking about. If any of these sound useful to you, we'd love to hear about it. [Share your feedback](https://oc.to/feedback). | ||
|
|
||
| ### Placeholders | ||
|
|
||
| Placeholders would let producers give consumers some flexibility to add their own steps to a templated project's deployment process. Rather than a fully fixed process, producers could mark specific points where consumers are permitted to insert their own steps. | ||
|
|
||
| ### Runbooks and triggers | ||
|
|
||
| We're planning to support runbooks and triggers defined in the project template, so templated projects inherit them alongside the deployment process. This would let producers standardize operational runbooks and scheduled triggers across all projects created from the template. Projects would still be able to create and manage their own runbooks and triggers. |
There was a problem hiding this comment.
I'd run this by Ships, I don't know if she's wanting to talk about these yet. I'd be particularly concerned about the placeholders stuff, given that it's a "we might look at it sometime" kind of thing.
|  | ||
| ::: | ||
|
|
||
| 1. Click **Create Project**. You'll be taken to the **Template values** page. |
There was a problem hiding this comment.
| 1. Click **Create Project**. You'll be taken to the **Template values** page. | |
| Click **Create Project**. You'll be taken to the **Template values** page. |
octo-ryanhall
left a comment
There was a problem hiding this comment.
@IsaacCalligeros95 I have added a few minor suggestions. Feel free to pick and choose what makes sense.
Thanks Ryan, really appreciate the feedback. Taking a look now |
Adds Project Templates docs. since there's a significant overlap with Process Templates I've separated out some common pages and re-worked the page heirachy here.
Questions:
MAS-2353