Remove Legacy Docs

README.md

@@ -10,8 +10,6 @@ This repo houses the assets used to build the Flux project's landing page at <ht
 > ---------------- | ------------------------------------------| -------------
 > Flux             | <https://fluxcd.io/flux>                  | <https://github.com/fluxcd/website>
 > Flagger          | <https://fluxcd.io/flagger>               | <https://github.com/fluxcd/website>
-> Flux (legacy)    | <https://fluxcd.io/legacy/flux>           | <https://github.com/fluxcd/website>
-> Helm Operator    | <https://fluxcd.io/legacy/helm-operator/> | <https://github.com/fluxcd/website>
 
 ## How to modify this website
 

content/en/flux/migration/flux-v1-automation-migration.md

@@ -666,7 +666,7 @@ spec:
 ```
 
 This works straight-forwardly for Deployment manifests, but when it comes to `HelmRelease`
-manifests, it [gets complicated][helm-auto], and it doesn't work at all for many kinds of resources.
+manifests, doesn't work at all for many kinds of resources.
 
 For Flux v2, you mark the field you want to be updated directly, with the namespaced name of the
 image policy to apply. This is the example Deployment, marked up for Flux v2:
@@ -743,13 +743,11 @@ from ["Migrating each manifest to Flux v2"](#migrating-each-manifest-to-flux-v2)
 
 [image-update-tute]: /flux/guides/image-update/
 [imagepolicy-ref]: /flux/components/image/imagepolicies/
-[helm-auto]: /legacy/flux/references/helm-operator-integration/#automated-image-detection
 [image-update-tute-custom]: /flux/guides/image-update/#configure-image-update-for-custom-resources
 [flux-v1-migration]: /flux/migration/flux-v1-migration/
 [install-cli]: /flux/get-started/#install-the-flux-cli
 [flux-bootstrap]: /flux/installation/_index.md#bootstrap
 [github-pat]: https://docs.github.com/en/github/authenticating-to-github/creating-a-personal-access-token
-[auto-object-ref]: /flux/components/image/imageupdateautomations/
 [image-update-tute-creds]: /flux/guides/image-update/#configure-image-scanning
 [image-update-tute-clouds]: /flux/guides/image-update/#imagerepository-cloud-providers-authentication
 [image-tags-guide]: /flux/guides/sortable-image-tags/

content/en/flux/migration/helm-operator-migration.md

@@ -849,7 +849,7 @@ If you are not a Flux v1 user or want to fully migrate to Flux v2, the [Kustomiz
 
 ### I am still running Helm v2, what is the right upgrade path for me?
 
-Migrate your Helm v2 releases to v3 using [the Helm Operator's migration feature](/legacy/helm-operator/helmrelease-guide/release-configuration/#migrating-from-helm-v2-to-v3), or make use of the [`helm-2to3`](https://github.com/helm/helm-2to3) plugin directly, before continuing following the [migration steps](#steps).
+Migrate your Helm v2 releases to v3 using the Helm Operator's migration feature, or make use of the [`helm-2to3`](https://github.com/helm/helm-2to3) plugin directly, before continuing following the [migration steps](#steps).
 
 ### Is the Helm Controller ready for production?