mbaldessari · Nov 11, 2026 · Nov 10, 2026
diff --git a/content/contribute/extending-a-pattern.adoc b/content/contribute/extending-a-pattern.adoc
@@ -27,7 +27,7 @@ In the example below AMQ Streams (Kafka) is chosen as a product to add to a patt
 
 == Before starting, fork and clone first
 
-. Visit the github page for the pattern that you wish to extend. E.g. https://github.com/hybrid-cloud-patterns/multicloud-gitops[multicloud-gitops]. Select "`Fork`" in the top right corner.
+. Visit the github page for the pattern that you wish to extend. E.g. https://github.com/validatedpatterns/multicloud-gitops[multicloud-gitops]. Select "`Fork`" in the top right corner.
 . On the create a new fork page. You can choose what owner repository you want and the name of the fork. Most times you will fork into your personal repo and leave the name the same. When you have made the appropriate changes press the "Create fork" button.
 . You will need to clone from the new fork onto you laptop/desktop so that you can do the extension work effectively. So on the new fork's main page elect the green "`Code`" button and copy the git repo's ssh address.
 . In an appropriate directory on your laptop (e.g. `~/git`) use `git clone` on the command line using the ssh address copied above. Then create a branch to extend the pattern. For example if you are extending the `multicloud-gitops` pattern and adding kafka, you will need to clone your fork of multicloud-gitops and create a branch to add Kafka:

diff --git a/content/contribute/maintained.adoc b/content/contribute/maintained.adoc
@@ -20,7 +20,7 @@ A pattern categorized under the {maintained} tier implies that the pattern was k
 [id="nominating-a-pattern-for-maintained-tier"]
 == Nominating a pattern for the {maintained} tier
 
-If your pattern qualifies or meets the criteria for {maintained} tier, submit your nomination to mailto:validatedpatterns@googlegroups.com[validatedpatterns@googlegroups.com].
+If your pattern qualifies or meets the criteria for {maintained} tier, https://groups.google.com/g/validatedpatterns/about[join the validatedpatterns group] and submit your nomination to mailto:validatedpatterns@googlegroups.com[validatedpatterns@googlegroups.com].
 
 [NOTE]
 ====

diff --git a/content/contribute/pattern-metadata-documentation-sync.adoc b/content/contribute/pattern-metadata-documentation-sync.adoc
@@ -122,6 +122,6 @@ The workflow validates `repo_url`, flattens the metadata, and opens a pull reque
 
 . Review and merge the resulting pull request in `validatedpatterns/docs`.
 
-Contact mailto:validatedpatterns@googlegroups.com[validatedpatterns@googlegroups.com] if you need help configuring repository secrets for metadata sync.
+https://groups.google.com/g/validatedpatterns/about[Join the validatedpatterns group] and contact mailto:validatedpatterns@googlegroups.com[validatedpatterns@googlegroups.com] if you need help configuring repository secrets for metadata sync.
 
 For sync failures, see link:/contribute/pattern-metadata-validation/#metadata-sync-workflow-fails-on-repo-url[Metadata sync workflow fails on repo URL] in Validation and troubleshooting.
diff --git a/content/contribute/support-policies.adoc b/content/contribute/support-policies.adoc
@@ -39,7 +39,7 @@ To ensure we can best help you please provide the following information:
 * Any changes that were made prior to the failure
 * Expected Outcome: What you thought should have happened
 
-If you are unsure if your issue is product or pattern related, please reach out to the community using https://groups.google.com/g/validatedpatterns or by emailing validatedpatterns@googlegroups.com 
+If you are unsure if your issue is product or pattern related, https://groups.google.com/g/validatedpatterns/about[join the validatedpatterns group] and reach out to the community by posting in the group or emailing mailto:validatedpatterns@googlegroups.com[validatedpatterns@googlegroups.com]. 
 
 Any pattern-based security issues, such as hard coded secrets, found should be reported to: validated-patterns-team@redhat.com  You can expect a response **within 5 business days**
 

diff --git a/content/contribute/tested.adoc b/content/contribute/tested.adoc
@@ -20,7 +20,7 @@ The {tested} tier provides you with additional collateral and reassurance that t
 [id="nominating-a-pattern-for-tested-tier"]
 == Nominating a pattern for the {tested} tier
 
-If your pattern qualifies or meets the criteria for {tested} tier, submit your nomination to mailto:validatedpatterns@googlegroups.com[validatedpatterns@googlegroups.com].
+If your pattern qualifies or meets the criteria for {tested} tier, https://groups.google.com/g/validatedpatterns/about[join the validatedpatterns group] and submit your nomination to mailto:validatedpatterns@googlegroups.com[validatedpatterns@googlegroups.com].
 
 [NOTE]
 ====

diff --git a/modules/contributing.adoc b/modules/contributing.adoc
@@ -8,15 +8,15 @@
 
 There are a few different ways you can contribute to Validated Patterns documentation:
 
-* Email the Validated Patterns team at mailto:hybrid-cloud-patterns@googlegroups.com[hybrid-cloud-patterns@googlegroups.com].
+*  https://groups.google.com/g/validatedpatterns/about[Join the validatedpatterns group] and email the Validated Patterns team at mailto:validatedpatterns@googlegroups.com[validatedpatterns@googlegroups.com].
 * Create a link:https://github.com/validatedpatterns/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/validatedpatterns/docs[Validated Patterns docs repository], make your changes, and submit a PR. This option is best if you have substantial changes.
 //to-do:For more details on creating a PR see <topic_link_to_contribution_workflow>.
 
 == Contribution workflow
 
-When you submit a PR, the https://github.com/orgs/hybrid-cloud-patterns/teams/docs[Validated Patterns Docs team] reviews the PR and arranges further reviews by Quality Engineering (QE), subject matter experts (SMEs), and others, as required. If the PR requires changes, updates, or corrections, the reviewers add comments in the PR. The documentation team merges the PR after you have implemented all feedback, and you have squashed all commits.
+When you submit a PR, the https://github.com/orgs/validatedpatterns/teams/docs[Validated Patterns Docs team] reviews the PR and arranges further reviews by Quality Engineering (QE), subject matter experts (SMEs), and others, as required. If the PR requires changes, updates, or corrections, the reviewers add comments in the PR. The documentation team merges the PR after you have implemented all feedback, and you have squashed all commits.
 
 
 == Repository organization