Update email address (#4254)

ui/components/Footer.tsx

@@ -46,8 +46,8 @@ function Footer({ className }: Props) {
       <LeftFoot>
         <Text noWrap>Need help? Contact us at</Text>
         <Spacer padding="xxs" />
-        <Link newTab href="mailto:sales@weaveworks.org">
-          sales@weaveworks.org
+        <Link newTab href="mailto:info@weaveworks.org">
+          info@weaveworks.org
         </Link>
       </LeftFoot>
       <RightFoot>

ui/components/__tests__/__snapshots__/Footer.test.tsx.snap

@@ -116,15 +116,15 @@ exports[`Footer snapshots default 1`] = `
     />
     <a
       class="c5 Link"
-      href="mailto:sales@weaveworks.org"
+      href="mailto:info@weaveworks.org"
       rel="noreferrer"
       target="_blank"
     >
       <span
         class="c6"
         color="primary"
       >
-        sales@weaveworks.org
+        info@weaveworks.org
       </span>
     </a>
   </div>
@@ -315,15 +315,15 @@ exports[`Footer snapshots no api version 1`] = `
     />
     <a
       class="c5 Link"
-      href="mailto:sales@weaveworks.org"
+      href="mailto:info@weaveworks.org"
       rel="noreferrer"
       target="_blank"
     >
       <span
         class="c6"
         color="primary"
       >
-        sales@weaveworks.org
+        info@weaveworks.org
       </span>
     </a>
   </div>

website/docs/enterprise/getting-started/install-enterprise-azure.mdx

@@ -35,7 +35,7 @@ If you are planning to manage or connect CAPI clusters to the WE service make su
 
 ## 2. Apply the Entitlements Secret
 
-Contact sales@weaveworks.org for a valid entitlements secret. This will come in the form of a file “entitlements.yaml”. Apply it to the cluster:
+Contact info@weaveworks.org for a valid entitlements secret. This will come in the form of a file “entitlements.yaml”. Apply it to the cluster:
 
 ```
 kubectl apply -f entitlements.yaml

website/docs/enterprise/getting-started/install-enterprise-cli.mdx

@@ -120,7 +120,7 @@ For SSH, `private key path` & `private key password`. For HTTPS, `username` and
 
 Weave GitOps Enterprise Entitlement is your obtained license to use our product. The Entitlements file is a Kubernetes secret that contains your licence.
 `Bootstrapping` checks that the secret exists on the management cluster, and that it is valid will check if it has valid content and the entitlement is not expired.
-To get the entitlement secret please contact *sales@weaveworks.org*, then apply it on your management cluster with the name `weave-gitops-enterprise-credentials` under `flux-system` namespace.
+To get the entitlement secret please contact *info@weaveworks.org*, then apply it on your management cluster with the name `weave-gitops-enterprise-credentials` under `flux-system` namespace.
 
 #### Configure Git Access
 

website/docs/enterprise/getting-started/install-enterprise.mdx

@@ -15,7 +15,7 @@ import oauthAzureDevOpsSuccess from '/img/oauth-azure-devops-success.png';
 # Install Weave GitOps Enterprise<TierLabel tiers="Enterprise" />
 
 :::info
-To purchase an entitlement to Weave GitOps Enterprise, please contact [sales@weaveworks.org](mailto:sales@weaveworks.org).
+To purchase an entitlement to Weave GitOps Enterprise, please contact [info@weaveworks.org](mailto:info@weaveworks.org).
 :::
 
 Follow the instructions on this page to:
@@ -115,7 +115,7 @@ At this point your Flux management cluster should be running. Take a look at the
 
 ### Apply Your Entitlements Secret to Your Cluster
 
-As noted above, you receive your entitlements secret by contacting sales@weaveworks.org. Use this command to apply it to the cluster:
+As noted above, you receive your entitlements secret by contacting info@weaveworks.org. Use this command to apply it to the cluster:
 
 ```bash
 kubectl apply -f entitlements.yaml

website/docs/enterprise/getting-started/intro-enterprise.mdx

@@ -8,7 +8,7 @@ import Link from "@docusaurus/Link";
 # Weave GitOps Enterprise <TierLabel tiers="Enterprise" />
 
 :::tip Ready for more GitOps?
-To purchase an entitlement to Weave GitOps Enterprise, please contact [sales@weaveworks.org](mailto:sales@weaveworks.org).
+To purchase an entitlement to Weave GitOps Enterprise, please contact [info@weaveworks.org](mailto:info@weaveworks.org).
 :::
 
 Weave GitOps Enterprise provides ops teams with an easy way to assess the

website/docs/intro-weave-gitops.mdx

@@ -27,7 +27,7 @@ This user guide provides content that will help you to install and get started w
 
 :::tip
 Want to learn more about how [Weave GitOps Enterprise](./enterprise/getting-started/intro-enterprise.mdx) can help your team?
-Get in touch with sales@weaveworks.org to discuss your needs.
+Get in touch with info@weaveworks.org to discuss your needs.
 :::
 
 Weave GitOps works on any Chromium-based browser (Chrome, Opera, Microsoft Edge), Safari, and Firefox. We only support the latest and prior two versions of these browsers.

website/docs/open-source/getting-started/ui-OSS.mdx

@@ -9,7 +9,7 @@ pagination_next: open-source/getting-started/deploy-OSS
 The Weave GitOps user interface enables you to manage and view all of your applications in one place. This documentation gives you an overview of the Weave GitOps Open Source UI.
 
 :::tip
-To check out Weave GitOps Enterprise's UI, which provides an even richer user experience, please contact sales@weaveworks.org.
+To check out Weave GitOps Enterprise's UI, which provides an even richer user experience, please contact info@weaveworks.org.
 :::
 
 ## Overview

website/docusaurus.config.js

@@ -126,7 +126,7 @@ module.exports = {
           items: [
             {
               label: "Contact Us",
-              href: "mailto:sales@weaveworks.org",
+              href: "mailto:info@weaveworks.org",
             },
           ],
         },

website/src/pages/help-and-support/index.md

@@ -16,7 +16,7 @@ The Flux project has a fantastic community to help support your GitOps journey,
 
 Weaveworks provides [Weave GitOps Enterprise](https://www.weave.works/product/gitops-enterprise/), a continuous operations product that makes it easy to deploy and manage Kubernetes clusters and applications at scale in any environment. The single management console automates trusted application delivery and secure infrastructure operations on premise, in the cloud and at the edge.
 
-To discuss your support needs, please contact us at [sales@weaveworks.org](mailto:sales@weaveworks.org).
+To discuss your support needs, please contact us at [info@weaveworks.org](mailto:info@weaveworks.org).
 
 ## Recommended resources
 

website/versioned_docs/version-0.16.0/help-and-support.md

@@ -16,7 +16,7 @@ The Flux project has a fantastic community to help support your GitOps journey,
 
 Weaveworks provides [Weave GitOps Enterprise](https://www.weave.works/product/gitops-enterprise/), a continuous operations product that makes it easy to deploy and manage Kubernetes clusters and applications at scale in any environment. The single management console automates trusted application delivery and secure infrastructure operations on premise, in the cloud and at the edge.
 
-To discuss your support needs, please contact us at [sales@weaveworks.org](mailto:sales@weaveworks.org).
+To discuss your support needs, please contact us at [info@weaveworks.org](mailto:info@weaveworks.org).
 
 ## Recommended resources
 

website/versioned_docs/version-0.16.0/installation/weave-gitops-enterprise/index.mdx

@@ -17,7 +17,7 @@ Kubernetes version and number of nodes and provides details about the GitOps ope
 on those clusters, such as Git repositories and recent commits. Additionally, it
 aggregates Prometheus alerts to assist with troubleshooting.
 
-To purchase entitlement to Weave GitOps Enterprise please contact [sales@weaveworks.org](mailto:sales@weaveworks.org)
+To purchase entitlement to Weave GitOps Enterprise please contact [info@weaveworks.org](mailto:info@weaveworks.org)
 
 :::note 
 There is no need to install Weave GitOps (OSS) before installing Weave GitOps Enterprise
@@ -200,7 +200,7 @@ clusterctl init --infrastructure aws
 
 ### 3. Apply the entitlements secret
 
-Contact sales@weaveworks.org for a valid entitlements secret. Then apply it to the cluster:
+Contact info@weaveworks.org for a valid entitlements secret. Then apply it to the cluster:
 
 ```bash
 kubectl apply -f entitlements.yaml

website/versioned_docs/version-0.16.0/intro.md

@@ -73,4 +73,4 @@ aggregates Prometheus alerts to assist with troubleshooting.
 
 ### How to purchase
 
-Get in touch with sales@weaveworks.org to discuss your needs.
+Get in touch with info@weaveworks.org to discuss your needs.

website/versioned_docs/version-0.16.0/pipelines/pipeline-templates.mdx

@@ -21,7 +21,7 @@ We will cover the creation of:
 
 Secrets, required for authentication and authorization between leaf and management clusters as well as to Git, are out of scope for this document and would need to be handled by your secret management solution of choice.
 
-For advice on Secrets Management, you can refer to the Flux guide [here](https://fluxcd.io/flux/security/secrets-management/) or contact [Weaveworks](mailto:sales@weaveworks.org) for assistance.
+For advice on Secrets Management, you can refer to the Flux guide [here](https://fluxcd.io/flux/security/secrets-management/) or contact [Weaveworks](mailto:info@weaveworks.org) for assistance.
 
 Templates can include a single resource or multiple resources depending on your use case, for example - you may want to only create the Pipeline custom resource to associate existing HelmReleases, or you could create the HelmReleases, notification controller resources, and Pipeline all in a single template. They are highly customizable to suit your teams' needs.
 

website/versioned_docs/version-0.17.0/installation/weave-gitops-enterprise/index.mdx

@@ -12,7 +12,7 @@ import CurlCodeBlock from "../../_components/CurlCodeBlock";
 ## Installing Weave GitOps Enterprise<TierLabel tiers="Enterprise" />
 
 :::info
-To purchase entitlement to Weave GitOps Enterprise Edition please contact [sales@weaveworks.org](mailto:sales@weaveworks.org)
+To purchase entitlement to Weave GitOps Enterprise Edition please contact [info@weaveworks.org](mailto:info@weaveworks.org)
 
 For more information about Weave GitOps Enterprise Edition, see the [Enterprise feature page](../../intro-ee.mdx).
 :::
@@ -198,7 +198,7 @@ clusterctl init --infrastructure aws
 
 ### 3. Apply the entitlements secret
 
-Contact sales@weaveworks.org for a valid entitlements secret. Then apply it to the cluster:
+Contact info@weaveworks.org for a valid entitlements secret. Then apply it to the cluster:
 
 ```bash
 kubectl apply -f entitlements.yaml

website/versioned_docs/version-0.17.0/intro-ee.mdx

@@ -8,7 +8,7 @@ import Link from "@docusaurus/Link";
 # Weave GitOps Enterprise Edition <TierLabel tiers="Enterprise" />
 
 :::tip Ready for more GitOps?
-To purchase entitlement to Weave GitOps Enterprise Edition please contact [sales@weaveworks.org](mailto:sales@weaveworks.org)
+To purchase entitlement to Weave GitOps Enterprise Edition please contact [info@weaveworks.org](mailto:info@weaveworks.org)
 :::
 
 WGEE provides ops teams with an easy way to assess the

website/versioned_docs/version-0.17.0/intro.mdx

@@ -73,7 +73,7 @@ aggregates Prometheus alerts to assist with troubleshooting.
 - :infinity: **CD Pipelines**
 
 :::tip Want to learn more about how <Link to="../intro-ee">Weave GitOps Enterprise Edition</Link> can help your team?
-Get in touch with sales@weaveworks.org to discuss your needs.
+Get in touch with info@weaveworks.org to discuss your needs.
 :::
 
 ## Why adopt GitOps?

website/versioned_docs/version-0.17.0/pipelines/pipeline-templates.mdx

@@ -21,7 +21,7 @@ We will cover the creation of:
 
 Secrets, required for authentication and authorization between leaf and management clusters as well as to Git, are out of scope for this document and would need to be handled by your secret management solution of choice.
 
-For advice on Secrets Management, you can refer to the Flux guide [here](https://fluxcd.io/flux/security/secrets-management/) or contact [Weaveworks](mailto:sales@weaveworks.org) for assistance.
+For advice on Secrets Management, you can refer to the Flux guide [here](https://fluxcd.io/flux/security/secrets-management/) or contact [Weaveworks](mailto:info@weaveworks.org) for assistance.
 
 Templates can include a single resource or multiple resources depending on your use case, for example - you may want to only create the Pipeline custom resource to associate existing HelmReleases, or you could create the HelmReleases, notification controller resources, and Pipeline all in a single template. They are highly customizable to suit your teams' needs.
 

website/versioned_docs/version-0.18.0/installation/weave-gitops-enterprise/index.mdx

@@ -13,7 +13,7 @@ import oauthBitbucket from '/img/oauth-bitbucket.png';
 ## Installing Weave GitOps Enterprise<TierLabel tiers="Enterprise" />
 
 :::info
-To purchase entitlement to Weave GitOps Enterprise Edition please contact [sales@weaveworks.org](mailto:sales@weaveworks.org)
+To purchase entitlement to Weave GitOps Enterprise Edition please contact [info@weaveworks.org](mailto:info@weaveworks.org)
 
 For more information about Weave GitOps Enterprise Edition, see the [Enterprise feature page](../../intro-ee.mdx).
 :::
@@ -199,7 +199,7 @@ clusterctl init --infrastructure aws
 
 ### 3. Apply the entitlements secret
 
-Contact sales@weaveworks.org for a valid entitlements secret. Then apply it to the cluster:
+Contact info@weaveworks.org for a valid entitlements secret. Then apply it to the cluster:
 
 ```bash
 kubectl apply -f entitlements.yaml

website/versioned_docs/version-0.18.0/intro-ee.mdx

@@ -8,7 +8,7 @@ import Link from "@docusaurus/Link";
 # Weave GitOps Enterprise Edition <TierLabel tiers="Enterprise" />
 
 :::tip Ready for more GitOps?
-To purchase entitlement to Weave GitOps Enterprise Edition please contact [sales@weaveworks.org](mailto:sales@weaveworks.org)
+To purchase entitlement to Weave GitOps Enterprise Edition please contact [info@weaveworks.org](mailto:info@weaveworks.org)
 :::
 
 WGEE provides ops teams with an easy way to assess the

website/versioned_docs/version-0.18.0/intro.mdx

@@ -73,7 +73,7 @@ aggregates Prometheus alerts to assist with troubleshooting.
 - :infinity: **CD Pipelines**
 
 :::tip Want to learn more about how <Link to="../intro-ee">Weave GitOps Enterprise Edition</Link> can help your team?
-Get in touch with sales@weaveworks.org to discuss your needs.
+Get in touch with info@weaveworks.org to discuss your needs.
 :::
 
 ## Why adopt GitOps?

website/versioned_docs/version-0.18.0/pipelines/pipeline-templates.mdx

@@ -21,7 +21,7 @@ We will cover the creation of:
 
 Secrets, required for authentication and authorization between leaf and management clusters as well as to Git, are out of scope for this document and would need to be handled by your secret management solution of choice.
 
-For advice on Secrets Management, you can refer to the Flux guide [here](https://fluxcd.io/flux/security/secrets-management/) or contact [Weaveworks](mailto:sales@weaveworks.org) for assistance.
+For advice on Secrets Management, you can refer to the Flux guide [here](https://fluxcd.io/flux/security/secrets-management/) or contact [Weaveworks](mailto:info@weaveworks.org) for assistance.
 
 Templates can include a single resource or multiple resources depending on your use case, for example - you may want to only create the Pipeline custom resource to associate existing HelmReleases, or you could create the HelmReleases, notification controller resources, and Pipeline all in a single template. They are highly customizable to suit your teams' needs.
 

website/versioned_docs/version-0.19.0/installation/weave-gitops-enterprise/index.mdx

@@ -13,7 +13,7 @@ import oauthBitbucket from '/img/oauth-bitbucket.png';
 ## Installing Weave GitOps Enterprise<TierLabel tiers="Enterprise" />
 
 :::info
-To purchase entitlement to Weave GitOps Enterprise Edition please contact [sales@weaveworks.org](mailto:sales@weaveworks.org)
+To purchase entitlement to Weave GitOps Enterprise Edition please contact [info@weaveworks.org](mailto:info@weaveworks.org)
 
 For more information about Weave GitOps Enterprise Edition, see the [Enterprise feature page](../../intro-ee.mdx).
 :::
@@ -199,7 +199,7 @@ clusterctl init --infrastructure aws
 
 ### 3. Apply the entitlements secret
 
-Contact sales@weaveworks.org for a valid entitlements secret. Then apply it to the cluster:
+Contact info@weaveworks.org for a valid entitlements secret. Then apply it to the cluster:
 
 ```bash
 kubectl apply -f entitlements.yaml

website/versioned_docs/version-0.19.0/intro-ee.mdx

@@ -8,7 +8,7 @@ import Link from "@docusaurus/Link";
 # Weave GitOps Enterprise Edition <TierLabel tiers="Enterprise" />
 
 :::tip Ready for more GitOps?
-To purchase entitlement to Weave GitOps Enterprise Edition please contact [sales@weaveworks.org](mailto:sales@weaveworks.org)
+To purchase entitlement to Weave GitOps Enterprise Edition please contact [info@weaveworks.org](mailto:info@weaveworks.org)
 :::
 
 WGEE provides ops teams with an easy way to assess the

website/versioned_docs/version-0.19.0/intro.mdx

@@ -73,7 +73,7 @@ aggregates Prometheus alerts to assist with troubleshooting.
 - :infinity: **CD Pipelines**
 
 :::tip Want to learn more about how <Link to="../intro-ee">Weave GitOps Enterprise Edition</Link> can help your team?
-Get in touch with sales@weaveworks.org to discuss your needs.
+Get in touch with info@weaveworks.org to discuss your needs.
 :::
 
 ## Why adopt GitOps?

website/versioned_docs/version-0.19.0/pipelines/pipeline-templates.mdx

@@ -22,7 +22,7 @@ We will cover the creation of:
 
 Secrets, required for authentication and authorization between leaf and management clusters as well as to Git, are out of scope for this document and would need to be handled by your secret management solution of choice.
 
-For advice on Secrets Management, you can refer to the Flux guide [here](https://fluxcd.io/flux/security/secrets-management/) or contact [Weaveworks](mailto:sales@weaveworks.org) for assistance.
+For advice on Secrets Management, you can refer to the Flux guide [here](https://fluxcd.io/flux/security/secrets-management/) or contact [Weaveworks](mailto:info@weaveworks.org) for assistance.
 
 Templates can include a single resource or multiple resources depending on your use case, for example - you may want to only create the Pipeline custom resource to associate existing HelmReleases, or you could create the HelmReleases, notification controller resources, and Pipeline all in a single template. They are highly customizable to suit your teams' needs.
 

website/versioned_docs/version-0.20.0/installation/weave-gitops-enterprise/index.mdx

@@ -13,7 +13,7 @@ import oauthBitbucket from '/img/oauth-bitbucket.png';
 ## Installing Weave GitOps Enterprise<TierLabel tiers="Enterprise" />
 
 :::info
-To purchase entitlement to Weave GitOps Enterprise Edition please contact [sales@weaveworks.org](mailto:sales@weaveworks.org)
+To purchase entitlement to Weave GitOps Enterprise Edition please contact [info@weaveworks.org](mailto:info@weaveworks.org)
 
 For more information about Weave GitOps Enterprise Edition, see the [Enterprise feature page](../../intro-ee.mdx).
 :::
@@ -199,7 +199,7 @@ clusterctl init --infrastructure aws
 
 ### 3. Apply the entitlements secret
 
-Contact sales@weaveworks.org for a valid entitlements secret. Then apply it to the cluster:
+Contact info@weaveworks.org for a valid entitlements secret. Then apply it to the cluster:
 
 ```bash
 kubectl apply -f entitlements.yaml

website/versioned_docs/version-0.20.0/intro-ee.mdx

@@ -8,7 +8,7 @@ import Link from "@docusaurus/Link";
 # Weave GitOps Enterprise Edition <TierLabel tiers="Enterprise" />
 
 :::tip Ready for more GitOps?
-To purchase entitlement to Weave GitOps Enterprise Edition please contact [sales@weaveworks.org](mailto:sales@weaveworks.org)
+To purchase entitlement to Weave GitOps Enterprise Edition please contact [info@weaveworks.org](mailto:info@weaveworks.org)
 :::
 
 WGEE provides ops teams with an easy way to assess the

website/versioned_docs/version-0.20.0/intro.mdx

@@ -73,7 +73,7 @@ aggregates Prometheus alerts to assist with troubleshooting.
 - :infinity: **CD Pipelines**
 
 :::tip Want to learn more about how <Link to="../intro-ee">Weave GitOps Enterprise Edition</Link> can help your team?
-Get in touch with sales@weaveworks.org to discuss your needs.
+Get in touch with info@weaveworks.org to discuss your needs.
 :::
 
 ## Why adopt GitOps?

website/versioned_docs/version-0.20.0/pipelines/pipeline-templates.mdx

@@ -22,7 +22,7 @@ We will cover the creation of:
 
 Secrets, required for authentication and authorization between leaf and management clusters as well as to Git, are out of scope for this document and would need to be handled by your secret management solution of choice.
 
-For advice on Secrets Management, you can refer to the Flux guide [here](https://fluxcd.io/flux/security/secrets-management/) or contact [Weaveworks](mailto:sales@weaveworks.org) for assistance.
+For advice on Secrets Management, you can refer to the Flux guide [here](https://fluxcd.io/flux/security/secrets-management/) or contact [Weaveworks](mailto:info@weaveworks.org) for assistance.
 
 Templates can include a single resource or multiple resources depending on your use case, for example - you may want to only create the Pipeline custom resource to associate existing HelmReleases, or you could create the HelmReleases, notification controller resources, and Pipeline all in a single template. They are highly customizable to suit your teams' needs.