Update for the renamed google group

archetypes/pattern/_index.adoc

@@ -13,7 +13,7 @@ industries:
 links:
   install:
   arch:
-  help: https://groups.google.com/g/hybrid-cloud-patterns
+  help: https://groups.google.com/g/validatedpatterns
   bugs:
 # The following parameters are only used for validated patterns. Do not uncomment them unless your pattern is validated.
 # validated:

content/learn/maintained.adoc

@@ -20,7 +20,7 @@ The Maintained tier is intended to provide consumers with additional "sales" col
 [id="nominating-a-community-pattern-to-become-validated"]
 == Nominating a Tested Pattern to become Maintained
 
-If there is a Tested pattern that you believe would be a good candidate for promotion to Maintained, you can make that case by emailing hybrid-cloud-patterns@googlegroups.com
+If there is a Tested pattern that you believe would be a good candidate for promotion to Maintained, you can make that case by emailing validatedpatterns@googlegroups.com
 
 Please be aware that each Maintained pattern represents an ongoing maintenance, support, and testing effort.  Finite team capacity means that it is simply not possible for the team to take on this responsibility for all Validated Patterns.  
 

content/learn/tested.adoc

@@ -19,7 +19,7 @@ The Tested tier is intended to provide consumers with additional collateral and
 [id="nominating-a-community-pattern-to-become-Tested"]
 == Nominating a Sandbox Pattern for Promotion to Tested
 
-If there is a Sandbox pattern that you believe would be a good candidate for promotion to tested, you can make that case by emailing hybrid-cloud-patterns@googlegroups.com
+If there is a Sandbox pattern that you believe would be a good candidate for promotion to tested, you can make that case by emailing validatedpatterns@googlegroups.com
 
 Please be aware that each Tested pattern represents an ongoing maintenance, support, and testing effort.  Finite team capacity means that it is simply not possible for the team to take on this responsibility for all Validated Patterns.  
 
@@ -45,8 +45,8 @@ Qualification is a Validated Patterns TOC decision with input from the pattern o
 
 . Tested Patterns *MUST* have their implementation reviewed by the patterns team to ensure that it is sufficiently flexible to function across a variety of platforms, customer environments, and any relevant verticals.
 . Tested Patterns *MUST* include a standardized architecture drawing, created with (or at least conforming to) the PAC tooling
-. Tested Patterns *MUST* include a script for others to follow when demonstrating how the pattern addresses a business problem
-. Tested Patterns *MUST* include a test plan covering all features or attributes being highlighted by the demonstration script.  Negative flow tests (such as resiliency or data retention in the presence of network outages) are limited to scenarios covered by the demonstration script.
+. Tested Patterns *MUST* include a written guide for others to follow when demonstrating how the pattern addresses a business problem
+. Tested Patterns *MUST* include a test plan covering all features or attributes being highlighted by the demonstration guide.  Negative flow tests (such as resiliency or data retention in the presence of network outages) are also limited to scenarios covered by the demonstration guide.
 +
 The test plan *MUST* define how to validate if the pattern has been successfully deployed and is functionally operational.
 Example: https://docs.google.com/document/d/12KQhdzjVIsxRURTnWAckiEMB3_96oWBjtlTXi1q73cg/view[Validating an Industrial Edge Deployment]

content/patterns/ansible-edge-gitops/_index.md

@@ -15,7 +15,7 @@ aliases: /ansible-edge-gitops/
 pattern_logo: ansible-edge.png
 links:
   install: getting-started
-  help: https://groups.google.com/g/hybrid-cloud-patterns
+  help: https://groups.google.com/g/validatedpatterns
   bugs: https://github.com/hybrid-cloud-patterns/ansible-edge-gitops/issues
 ci: aegitops
 ---

content/patterns/ansible-edge-gitops/ansible-automation-platform.md

@@ -189,5 +189,5 @@ This does the work of provisioning the kiosk, which configures kiosk mode, and a
 
 # Next Steps
 
-## [Help & Feedback](https://groups.google.com/g/hybrid-cloud-patterns)
+## [Help & Feedback](https://groups.google.com/g/validatedpatterns)
 ## [Report Bugs](https://github.com/hybrid-cloud-patterns/ansible-edge-gitops/issues)

content/patterns/ansible-edge-gitops/getting-started.md

@@ -232,5 +232,5 @@ As part of this pattern HashiCorp Vault has been installed. Refer to the section
 
 # Next Steps
 
-## [Help & Feedback](https://groups.google.com/g/hybrid-cloud-patterns)
+## [Help & Feedback](https://groups.google.com/g/validatedpatterns)
 ## [Report Bugs](https://github.com/hybrid-cloud-patterns/ansible-edge-gitops/issues)

content/patterns/ansible-edge-gitops/ideas-for-customization.md

@@ -264,5 +264,5 @@ The reason this pattern ships with a script as it does instead of invoking the r
 
 # Next Steps
 
-## [Help & Feedback](https://groups.google.com/g/hybrid-cloud-patterns)
+## [Help & Feedback](https://groups.google.com/g/validatedpatterns)
 ## [Report Bugs](https://github.com/hybrid-cloud-patterns/ansible-edge-gitops/issues)

content/patterns/ansible-edge-gitops/installation-details.md

@@ -129,5 +129,5 @@ More details of the specifics of how AAP is configured are available [here](/ans
 
 # Next Steps
 
-## [Help & Feedback](https://groups.google.com/g/hybrid-cloud-patterns)
+## [Help & Feedback](https://groups.google.com/g/validatedpatterns)
 ## [Report Bugs](https://github.com/hybrid-cloud-patterns/ansible-edge-gitops/issues)

content/patterns/ansible-edge-gitops/openshift-virtualization.md

@@ -353,5 +353,5 @@ The [rhel8-kiosk-with-svc](https://github.com/hybrid-cloud-patterns/ansible-edge
 
 # Next Steps
 
-## [Help & Feedback](https://groups.google.com/g/hybrid-cloud-patterns)
+## [Help & Feedback](https://groups.google.com/g/validatedpatterns)
 ## [Report Bugs](https://github.com/hybrid-cloud-patterns/ansible-edge-gitops/issues)

content/patterns/devsecops/_index.md

@@ -15,7 +15,7 @@ aliases: /devsecops/
 # pattern_logo: devsecops.png
 links:
   install: getting-started
-  help: https://groups.google.com/g/hybrid-cloud-patterns
+  help: https://groups.google.com/g/validatedpatterns
   bugs: https://github.com/hybrid-cloud-patterns/multicluster-devsecops/issues
 ci: devsecops
 ---

content/patterns/devsecops/getting-started.md

@@ -263,7 +263,7 @@ Advanced Cluster Security needs to be integrated with Quay Enterprise registry.
 
 # Next Steps
 
-[Help & Feedback](https://groups.google.com/g/hybrid-cloud-patterns){: .btn .fs-5 .mb-4 .mb-md-0 .mr-2 }
+[Help & Feedback](https://groups.google.com/g/validatedpatterns){: .btn .fs-5 .mb-4 .mb-md-0 .mr-2 }
 [Report Bugs](https://github.com/hybrid-cloud-patterns/multicluster-devsecops/issues){: .btn .btn-red .fs-5 .mb-4 .mb-md-0 .mr-2 }
 
 Once the hub has been setup correctly and confirmed to be working, you can:

content/patterns/emerging-disease-detection/_index.adoc

@@ -15,7 +15,7 @@ aliases: /emerging-disease-detection/
 links:
   install: getting-started
   arch: https://www.redhat.com/architect/portfolio/architecturedetail?ppid=6
-  help: https://groups.google.com/g/hybrid-cloud-patterns
+  help: https://groups.google.com/g/validatedpatterns
   bugs: https://github.com/validatedpatterns/emerging-disease-detection/issues
 ci: edd
 ---

content/patterns/emerging-disease-detection/getting-started.adoc

@@ -225,5 +225,5 @@ TO-DO: Describe how to examine the various parts of the Sepsis application
 
 = Next Steps
 
-link:https://groups.google.com/g/hybrid-cloud-patterns[Help & Feedback]
+link:https://groups.google.com/g/validatedpatterns[Help & Feedback]
 link:https://github.com/validatedpatterns/emerging-disease-detection/issues[Report Bugs]

content/patterns/industrial-edge/_index.md

@@ -16,7 +16,7 @@ pattern_logo: industrial-edge.png
 links:
   install: getting-started
   arch: https://www.redhat.com/architect/portfolio/architecturedetail?ppid=26
-  help: https://groups.google.com/g/hybrid-cloud-patterns
+  help: https://groups.google.com/g/validatedpatterns
   bugs: https://github.com/hybrid-cloud-patterns/industrial-edge/issues
 ci: manuela
 ---

content/patterns/industrial-edge/getting-started.md

@@ -227,7 +227,7 @@ For installation tooling dependencies, see [Patterns quick start]({{< ref "/cont
 
 ## Next Steps
 
-[Help & Feedback](https://groups.google.com/g/hybrid-cloud-patterns){: .btn .fs-5 .mb-4 .mb-md-0 .mr-2 }
+[Help & Feedback](https://groups.google.com/g/validatedpatterns){: .btn .fs-5 .mb-4 .mb-md-0 .mr-2 }
 [Report Bugs](https://github.com/hybrid-cloud-patterns/industrial-edge/issues){: .btn .btn-red .fs-5 .mb-4 .mb-md-0 .mr-2 }
 
 Once the data center has been setup correctly and confirmed to be working, you can:

content/patterns/industrial-edge/ideas-for-customization.md

@@ -61,5 +61,5 @@ The idea is that this pattern can be used for other use cases keeping the main c
 
 What ideas for customization do you have? Can you use this pattern for other use cases?  Let us know through our feedback link below.
 
-[Help & Feedback](https://groups.google.com/g/hybrid-cloud-patterns){: .btn .fs-5 .mb-4 .mb-md-0 .mr-2 }
+[Help & Feedback](https://groups.google.com/g/validatedpatterns){: .btn .fs-5 .mb-4 .mb-md-0 .mr-2 }
 [Report Bugs](https://github.com/hybrid-cloud-patterns/ansible-edge-gitops/issues){: .btn .btn-red .fs-5 .mb-4 .mb-md-0 .mr-2 }

content/patterns/medical-diagnosis/_index.adoc

@@ -14,7 +14,7 @@ pattern_logo: medical-diagnosis.png
 links:
   install: getting-started
   arch: https://www.redhat.com/architect/portfolio/architecturedetail?ppid=6
-  help: https://groups.google.com/g/hybrid-cloud-patterns
+  help: https://groups.google.com/g/validatedpatterns
   bugs: https://github.com/hybrid-cloud-patterns/medical-diagnosis/issues
 ci: medicaldiag
 ---

content/patterns/multicloud-gitops-Portworx/_index.md

@@ -13,7 +13,7 @@ aliases: /multicloud-gitops-Portworx/
 pattern_logo: multicloud-gitops-Portworx.png
 links:
   install: getting-started
-  help: https://groups.google.com/g/hybrid-cloud-patterns
+  help: https://groups.google.com/g/validatedpatterns
   bugs: https://github.com/hybrid-cloud-patterns/medical-diagnosis/issues
 # ci: mcgitopspxe
 ---

content/patterns/multicloud-gitops-Portworx/getting-started.md

@@ -106,5 +106,5 @@ After the management hub is set up and works correctly, attach one or more manag
 For instructions on deploying the edge, refer to [Managed Cluster Sites](https://validatedpatterns.io/patterns/multicloud-gitops-portworx/managed-cluster/).
 
 >Contribute to this pattern:
-{{% button text="Help & Feedback" url="https://groups.google.com/g/hybrid-cloud-patterns" %}}
+{{% button text="Help & Feedback" url="https://groups.google.com/g/validatedpatterns" %}}
 {{% button text="Report Bugs" url="https://github.com/portworx/rh-multicloud-gitops-pxe/issues" color-class="btn-red" %}}

content/patterns/multicloud-gitops-Portworx/ideas-for-customization.md

@@ -25,5 +25,5 @@ Another idea, after splitting the charts, could be to implement a small Rest API
 In the end the possibilities to tweak this pattern are endless. Do let us know if you have an awesome idea that you'd like to add
 
 >Contribute to this pattern:
-[Help & Feedback](https://groups.google.com/g/hybrid-cloud-patterns){: .btn .fs-5 .mb-4 .mb-md-0 .mr-2 }
+[Help & Feedback](https://groups.google.com/g/validatedpatterns){: .btn .fs-5 .mb-4 .mb-md-0 .mr-2 }
 [Report Bugs](https://github.com/hybrid-cloud-patterns/multicloud-gitops/issues){: .btn .btn-red .fs-5 .mb-4 .mb-md-0 .mr-2 }

content/patterns/multicloud-gitops/_index.adoc

@@ -13,7 +13,7 @@ pattern_logo: multicloud-gitops.png
 links:
   install: mcg-getting-started
   arch: https://www.redhat.com/architect/portfolio/detail/8-hybrid-multicloud-management-with-gitops
-  help: https://groups.google.com/g/hybrid-cloud-patterns
+  help: https://groups.google.com/g/validatedpatterns
   bugs: https://github.com/hybrid-cloud-patterns/multicloud-gitops/issues
 ci: mcgitops
 ---

content/patterns/retail/_index.md

@@ -14,7 +14,7 @@ aliases: /retail/
 # pattern_logo: retail.png
 links:
   install: getting-started
-  help: https://groups.google.com/g/hybrid-cloud-patterns
+  help: https://groups.google.com/g/validatedpatterns
   bugs: https://github.com/hybrid-cloud-patterns/retail/issues
 # uncomment once this exists
 # ci: retail

content/patterns/retail/getting-started.md

@@ -164,5 +164,5 @@ Clicking on the respective Kafdrop links will go to a Kafdrop instance that allo
 
 ## Next Steps
 
-[Help & Feedback](https://groups.google.com/g/hybrid-cloud-patterns){: .btn .fs-5 .mb-4 .mb-md-0 .mr-2 }
+[Help & Feedback](https://groups.google.com/g/validatedpatterns){: .btn .fs-5 .mb-4 .mb-md-0 .mr-2 }
 [Report Bugs](https://github.com/hybrid-cloud-patterns/retail/issues){: .btn .btn-red .fs-5 .mb-4 .mb-md-0 .mr-2 }

layouts/partials/footer.html

@@ -45,7 +45,7 @@
                         -->
                             <li>
                                 <i class="prefooter-icon fas fa-envelope"></i>
-                                <a href="https://groups.google.com/g/hybrid-cloud-patterns" class="footer-link" target="top" aria-label="Join the Validated Patterns mailing list">Mailing list</a>
+                                <a href="https://groups.google.com/g/validatedpatterns" class="footer-link" target="top" aria-label="Join the Validated Patterns mailing list">Mailing list</a>
                             </li>
                         </ul>
                     </nav>

modules/contributing.adoc

@@ -8,7 +8,7 @@
 
 There are a few different ways you can contribute to Hybrid Cloud Patterns documentation:
 
-* Email the Hybrid Cloud Patterns team at mailto:hybrid-cloud-patterns@googlegroups.com[hybrid-cloud-patterns@googlegroups.com].
+* Email the Hybrid Cloud Patterns team at mailto:validatedpatterns@googlegroups.com[validatedpatterns@googlegroups.com].
 * Create a link:https://github.com/hybrid-cloud-patterns/docs/issues[GitHub] or link:https://issues.redhat.com/projects/MBP/issues[Jira issue] .
 //to-do: Add link to the contribution workflow when we have a proper one. You might need to create a new file
 * Submit a pull request (PR). To create a PR, create a local clone of your own fork of the link:https://github.com/hybrid-cloud-patterns/docs[Hybrid Cloud Patterns docs repository], make your changes, and submit a PR. This option is best if you have substantial changes.