Remove porch docs after migration (#296)

Porch docs moved to https://docs.porch.nephio.org/

---------

Signed-off-by: Fiachra Corcoran <fiachra.corcoran@est.tech>

Author: efiacor

content/en/docs/apis/porch/_index.md

@@ -2,6 +2,9 @@
 title: "Package Orchestration API Specifications"
 type: docs
 weight: 5
-description: Reference for the Nephio Porch APIs
+description: Reference for the Porch APIs
 ---
-{{< iframe src="https://doc.crds.dev/github.com/nephio-project/porch@v4.0.0" sub="https://doc.crds.dev/github.com/nephio-project/porch@v4.0.0">}}
+For detailed API and CRD specifications, please refer to:
+
+- [Porch Aggregated API type definitions](https://docs.porch.nephio.org/docs/7_cli_api/api-ref/)
+- [Porch CRD Reference](https://docs.porch.nephio.org/docs/7_cli_api/crd-ref/)

content/en/docs/glossary-abbreviations.md

@@ -45,7 +45,7 @@ services, applications, etc.) which:
 * abstracts configuration file structure and storage from operations that act upon the configuration data; clients
   manipulating configuration data don’t need to directly interact with storage (git, container images)
 
-Source of definition and more information about Configuration as Data can be found in the [kpt documentation]({{% relref "/docs/porch/config-as-data.md" %}}).
+Source of definition and more information about Configuration as Data can be found in the [kpt documentation](https://kpt.dev/book/02-concepts/#configuration-as-data-key-principles).
 
 ## Controller
 This term comes from Kubernetes where

content/en/docs/guides/install-guides/install-on-byoc.md

@@ -21,7 +21,7 @@ your environment and choices.
  - *kubectl* [installed ](https://kubernetes.io/docs/tasks/tools/install-kubectl-linux/)on your workstation
  - *kpt* [installed](https://kpt.dev/installation/kpt-cli) on your workstation
    (version v1.0.0-beta.43 or later)
- - *porchctl* [installed]({{% relref "/docs/porch/user-guides/porchctl-cli-guide.md" %}}) on your workstation
+ - *porchctl* [installed](https://docs.porch.nephio.org/docs/3_getting_started/installing-porchctl/) on your workstation
  - Sudo-less *docker*, *Podman*, or *nerdctl*. If using *Podman* or *nerdctl*,
    you must set the
 [`KPT_FN_RUNTIME`](https://kpt.dev/reference/cli/fn/render/?id=environment-variables)

content/en/docs/guides/install-guides/install-on-multiple-vm.md

@@ -19,7 +19,7 @@ weight: 7
   * Kubernetes version 1.26+
   * *kubectl* [installed ](https://kubernetes.io/docs/tasks/tools/install-kubectl-linux/)
 * *kpt* [installed](https://kpt.dev/installation/kpt-cli) (version v1.0.0-beta.43 or later)
-* *porchctl* [installed]({{% relref "/docs/porch/user-guides/porchctl-cli-guide.md" %}}) on your workstation
+* *porchctl* [installed](https://docs.porch.nephio.org/docs/3_getting_started/installing-porchctl/) on your workstation
 
 ## Installation of the management cluster
 

content/en/docs/guides/user-guides/usecase-user-guides/exercise-3-fluxcd-wl.md

@@ -64,7 +64,7 @@ oai-core-packages           git    Package   false        True    https://github
 
 Once *Ready*, we can utilize blueprint packages from these upstream repositories.
 
-In this example, we will use the [Porch package variant controller]({{% relref "/docs/porch/package-variant.md#core-concepts" %}}) 
+In this example, we will use the [Porch package variant controller](https://docs.porch.nephio.org/docs/5_architecture_and_components/relevant_old_docs/package-variant/#core-concepts) 
 to deploy the new Workload Cluster.
 
 This fully automates the onboarding process, including the auto approval and publishing of the new package.

content/en/docs/guides/user-guides/usecase-user-guides/exercise-5-argocd-wl.md

@@ -161,7 +161,7 @@ oai-core-packages           git    Package   false        True    https://github
 
 Once *Ready*, we can utilize blueprint packages from these upstream repositories.
 
-In this example, we will use the [Porch package variant controller]({{% relref "/docs/porch/package-variant.md#core-concepts" %}}) 
+In this example, we will use the [Porch package variant controller](https://docs.porch.nephio.org/docs/5_architecture_and_components/relevant_old_docs/package-variant/#core-concepts) 
 to deploy the new Workload Cluster.
 
 This fully automates the onboarding process, including the auto approval and publishing of the new package.