diff --git a/source/cloud-native-platform/new-component/github-repo.html.md.erb b/source/cloud-native-platform/new-component/github-repo.html.md.erb
index f8df72fb..d1ef3f90 100644
--- a/source/cloud-native-platform/new-component/github-repo.html.md.erb
+++ b/source/cloud-native-platform/new-component/github-repo.html.md.erb
@@ -12,7 +12,7 @@ Any developer added to [hmcts org](https://github.com/hmcts) is able to create a
 
 1. Naming convention for repository is `{product}-{component}`. For product-level (shared) infrastructure, the name should be `{product}-shared-infrastructure`. [More info](/cloud-native-platform/new-component/infrastructure-as-code.html#product-and-component-level-infrastructure)
 2. If you are creating a NodeJS front end or Java backend component, you may want to use a template. These templates provide all the boiler plate code needed for a new app.
-    - [spring-boot-template](https://github.com/hmcts/spring-boot-template)
+    - [spring-boot-template](https://github.com/hmcts/spring-boot-template) or [service-hmcts-springboot-template](https://github.com/hmcts/service-hmcts-springboot-template)
     - [expressjs-template](https://github.com/hmcts/expressjs-template)
     - Alternatively you can simply create a blank directory. If so, we recommend you draw inspiration from an existing working repository.
 3. Repository should be public. [Gov UK guidance](https://www.gov.uk/service-manual/technology/making-source-code-open-and-reusable)