From a54eaa5eda04dd9ff6726ba5013a85ec402a6521 Mon Sep 17 00:00:00 2001 From: Wayne Starr Date: Mon, 15 May 2023 09:57:41 -0500 Subject: [PATCH] Fixup docs sidebar order --- adr/0014-oci-publish.md | 2 +- docs-website/docusaurus.config.js | 2 +- docs/0-zarf-overview.md | 2 +- docs/1-getting-started/index.md | 4 ++-- docs/2-the-zarf-cli/1-cli-common-uses.md | 6 +++--- docs/3-create-a-zarf-package/1-zarf-packages.md | 2 +- docs/3-create-a-zarf-package/3-zarf-init-package.md | 2 +- docs/3-create-a-zarf-package/index.md | 2 +- docs/4-deploy-a-zarf-package/index.md | 6 +++--- .../0-creating-a-zarf-package.md | 0 .../1-initializing-a-k8s-cluster.md | 0 .../2-deploying-zarf-packages.md | 0 .../3-deploy-a-retro-arcade.md | 0 .../{6-zarf-tutorials => 5-zarf-tutorials}/4-add-logging.md | 0 .../5-creating-a-k8s-cluster-with-zarf.md | 0 docs/{6-zarf-tutorials => 5-zarf-tutorials}/6-big-bang.md | 0 .../7-publish-and-deploy.md | 0 .../8-custom-init-packages.md | 0 docs/{6-zarf-tutorials => 5-zarf-tutorials}/_category_.json | 0 docs/{6-zarf-tutorials => 5-zarf-tutorials}/index.md | 0 examples/big-bang/README.md | 2 +- examples/dos-games/README.md | 2 +- examples/git-data/README.md | 2 +- examples/postgres-operator/README.md | 2 +- examples/tiny-kafka/README.md | 2 +- examples/wordpress/README.md | 2 +- 26 files changed, 20 insertions(+), 20 deletions(-) rename docs/{6-zarf-tutorials => 5-zarf-tutorials}/0-creating-a-zarf-package.md (100%) rename docs/{6-zarf-tutorials => 5-zarf-tutorials}/1-initializing-a-k8s-cluster.md (100%) rename docs/{6-zarf-tutorials => 5-zarf-tutorials}/2-deploying-zarf-packages.md (100%) rename docs/{6-zarf-tutorials => 5-zarf-tutorials}/3-deploy-a-retro-arcade.md (100%) rename docs/{6-zarf-tutorials => 5-zarf-tutorials}/4-add-logging.md (100%) rename docs/{6-zarf-tutorials => 5-zarf-tutorials}/5-creating-a-k8s-cluster-with-zarf.md (100%) rename docs/{6-zarf-tutorials => 5-zarf-tutorials}/6-big-bang.md (100%) rename docs/{6-zarf-tutorials => 5-zarf-tutorials}/7-publish-and-deploy.md (100%) rename docs/{6-zarf-tutorials => 5-zarf-tutorials}/8-custom-init-packages.md (100%) rename docs/{6-zarf-tutorials => 5-zarf-tutorials}/_category_.json (100%) rename docs/{6-zarf-tutorials => 5-zarf-tutorials}/index.md (100%) diff --git a/adr/0014-oci-publish.md b/adr/0014-oci-publish.md index aa5dcf8fa9..7989c12996 100644 --- a/adr/0014-oci-publish.md +++ b/adr/0014-oci-publish.md @@ -47,7 +47,7 @@ zarf-package-adr-arm64.tar.zst With this new structure in place, we can now publish Zarf packages as OCI artifacts. Under the hood this implements the `oras` Go library using Docker's authentication system. For interacting with these packages, the `oci://` package path prefix has been added (ex. `zarf package publish oci://...`). -For an example of this in action, please see the corresponding [tutorial](../docs/6-zarf-tutorials/7-publish-and-deploy.md). +For an example of this in action, please see the corresponding [tutorial](../docs/5-zarf-tutorials/7-publish-and-deploy.md). ## Consequences diff --git a/docs-website/docusaurus.config.js b/docs-website/docusaurus.config.js index fb25c9893f..6446696c31 100644 --- a/docs-website/docusaurus.config.js +++ b/docs-website/docusaurus.config.js @@ -47,7 +47,7 @@ const config = { const sidebarItems = await defaultSidebarItemsGenerator(args) if (args.item.dirName === 'docs') { // This hack places the examples tree at the 7th position in the sidebar - sidebarItems.splice(7, 0, { + sidebarItems.splice(6, 0, { type: 'category', label: 'Package Examples', link: { diff --git a/docs/0-zarf-overview.md b/docs/0-zarf-overview.md index 889fd1c2b9..ce0db897ad 100644 --- a/docs/0-zarf-overview.md +++ b/docs/0-zarf-overview.md @@ -85,7 +85,7 @@ Zarf can pull from various places like Docker Hub, Iron Bank, GitHub, and local This part of the process requires access to the internet. The `zarf` binary is presented with a `zarf.yaml`, it then begins downloading, packing, and compressing the software that you requested. It then outputs a single, ready-to-move distributable called "a package". -For additional information, see the [Creating a package](./6-zarf-tutorials/0-creating-a-zarf-package.md) section. +For additional information, see the [Creating a package](./5-zarf-tutorials/0-creating-a-zarf-package.md) section. ### (2) Ship the Package to the System Location diff --git a/docs/1-getting-started/index.md b/docs/1-getting-started/index.md index ae951f7c92..7bba3bfc9b 100644 --- a/docs/1-getting-started/index.md +++ b/docs/1-getting-started/index.md @@ -79,7 +79,7 @@ If you are online on the machine with cluster access you can also run `zarf init :::note -You can build your own custom 'init' package too if you'd like. For this you should check out the [Creating a Custom 'init' Package Tutorial](../6-zarf-tutorials/8-custom-init-packages.md). +You can build your own custom 'init' package too if you'd like. For this you should check out the [Creating a Custom 'init' Package Tutorial](../5-zarf-tutorials/8-custom-init-packages.md). ::: @@ -89,7 +89,7 @@ You can build your own custom 'init' package too if you'd like. For this you sho Depending on how familiar you are with Kubernetes, DevOps, and Zarf, let's find what set of information would be most useful to you. -- If you want to become more familiar with Zarf and it's features, see the [Tutorials](../6-zarf-tutorials/index.md) page. +- If you want to become more familiar with Zarf and it's features, see the [Tutorials](../5-zarf-tutorials/index.md) page. - More information about the Zarf CLI is available on the [Zarf CLI](../2-the-zarf-cli/index.md) page, or by browsing through the help descriptions of all the commands available through `zarf --help`. diff --git a/docs/2-the-zarf-cli/1-cli-common-uses.md b/docs/2-the-zarf-cli/1-cli-common-uses.md index e92aa2712a..3d345a7cb0 100644 --- a/docs/2-the-zarf-cli/1-cli-common-uses.md +++ b/docs/2-the-zarf-cli/1-cli-common-uses.md @@ -6,7 +6,7 @@ Zarf is a tool that optimizes the delivery of applications and capabilities into To create a Zarf Package, you must execute the [`zarf package create`](./100-cli-commands/zarf_package_create.md) command, which generates a tarball archive that includes all the required dependencies and instructions to deploy the capabilities onto another machine. The `zarf package create` command uses a [`zarf.yaml` configuration file](../3-create-a-zarf-package/4-zarf-schema.md) that describes the package's components and performs all necessary actions, such as downloading container images and git repositories, to build the final package. -Additional information on Zarf Packages can be found on the [Understanding Zarf Packages](../3-create-a-zarf-package/1-zarf-packages.md) page along with the [Creating a Zarf Package Tutorial](../6-zarf-tutorials/0-creating-a-zarf-package.md). +Additional information on Zarf Packages can be found on the [Understanding Zarf Packages](../3-create-a-zarf-package/1-zarf-packages.md) page along with the [Creating a Zarf Package Tutorial](../5-zarf-tutorials/0-creating-a-zarf-package.md). ## Initializing a Cluster: `zarf init` @@ -19,7 +19,7 @@ For Windows and macOS environments, a cluster must already exist before initiali For Linux environments, Zarf itself can create and update a local K3s cluster, in addition to using any other local or remote Kubernetes cluster. The init package used by `zarf init` contains all the resources necessary to create a local [K3s](https://k3s.io/) cluster on your machine. This package may be located in your current working directory, the directory where the Zarf CLI binary is located, or downloaded from GitHub releases during command execution. -Further details on the initialization process can be found on the [init package](../3-create-a-zarf-package/3-zarf-init-package.md) page along with the [Initializing a K8s Cluster Tutorial](../6-zarf-tutorials/1-initializing-a-k8s-cluster.md). +Further details on the initialization process can be found on the [init package](../3-create-a-zarf-package/3-zarf-init-package.md) page along with the [Initializing a K8s Cluster Tutorial](../5-zarf-tutorials/1-initializing-a-k8s-cluster.md). :::note Depending on the permissions of your user, if you are installing K3s with `zarf init`, you may need to run it as a privileged user. This can be done by either: @@ -35,4 +35,4 @@ Depending on the permissions of your user, if you are installing K3s with `zarf The [`zarf package deploy`](./100-cli-commands/zarf_package_deploy.md) command deploys the packaged capabilities into the target environment. The package can be deployed on any cluster, even those without an external internet connection, since it includes all of its external resources. The external resources are pushed into the cluster to services Zarf either deployed itself or that it was told about on `init`, such as the init package's Gitea Git server or a pre-existing Harbor image registry. Then, the application is deployed according to the instructions in the zarf.yaml file, such as deploying a helm chart, deploying raw K8s manifests, or executing a series of shell commands. Generally, it is presumed that the `zarf init` command has already been executed on the target machine. However, there are a few exceptional cases where this assumption does not apply, such as [YOLO Mode](../8-faq.md#what-is-yolo-mode-and-why-would-i-use-it). -Additional information about Zarf Packages can found on the [Understanding Zarf Packages](../3-create-a-zarf-package/1-zarf-packages.md) page along with the [Deploying a Local Zarf Package Tutorial](../6-zarf-tutorials//2-deploying-zarf-packages.md). +Additional information about Zarf Packages can found on the [Understanding Zarf Packages](../3-create-a-zarf-package/1-zarf-packages.md) page along with the [Deploying a Local Zarf Package Tutorial](../5-zarf-tutorials//2-deploying-zarf-packages.md). diff --git a/docs/3-create-a-zarf-package/1-zarf-packages.md b/docs/3-create-a-zarf-package/1-zarf-packages.md index 1466f29527..ecc279f610 100644 --- a/docs/3-create-a-zarf-package/1-zarf-packages.md +++ b/docs/3-create-a-zarf-package/1-zarf-packages.md @@ -65,7 +65,7 @@ The following list outlines the dependencies for creating a Zarf Package: When executed, the `zarf package create` command locates the `zarf.yaml` file in the current directory and constructs the package from that file. The command utilizes internet or intranet resources to retrieve all the required assets and stores them in a temporary directory. After the required resources have been obtained, Zarf generates a tarball of the temporary directory and performs necessary cleanup actions. You can learn more about this flow on the [package create lifecycle](./5-package-create-lifecycle.md) page. -The process of defining and creating a package is also elaborated on in detail in the [Creating a Zarf Package Tutorial](../6-zarf-tutorials/0-creating-a-zarf-package.md). +The process of defining and creating a package is also elaborated on in detail in the [Creating a Zarf Package Tutorial](../5-zarf-tutorials/0-creating-a-zarf-package.md). ## Inspecting a Created Package diff --git a/docs/3-create-a-zarf-package/3-zarf-init-package.md b/docs/3-create-a-zarf-package/3-zarf-init-package.md index 55b5ce2f38..fddcf2b412 100644 --- a/docs/3-create-a-zarf-package/3-zarf-init-package.md +++ b/docs/3-create-a-zarf-package/3-zarf-init-package.md @@ -2,7 +2,7 @@ The 'init' package is a special Zarf Package (denoted by `kind: ZarfInitConfig` in its `zarf.yaml`) that initializes a cluster with the requisite air gap services when running `zarf init`. This allows future Zarf Packages to store any required resources (i.e. container images and git repositories) so that they can be retrieved later. -The default 'init' package that Zarf ships is defined in the `zarf.yaml` that lives at the [root of the Zarf repository](https://github.com/defenseunicorns/zarf/blob/main/zarf.yaml), and is constructed from composed components that provide a foundation for customization. If you would like to change the behavior of the 'init' package you can do so by modifying this `zarf.yaml` or any of the composed components that it references and running `zarf package create` at the root of the repository. You can learn more about creating a custom init package in the [Creating a Custom 'init' Package Tutorial](../6-zarf-tutorials/8-custom-init-packages.md). +The default 'init' package that Zarf ships is defined in the `zarf.yaml` that lives at the [root of the Zarf repository](https://github.com/defenseunicorns/zarf/blob/main/zarf.yaml), and is constructed from composed components that provide a foundation for customization. If you would like to change the behavior of the 'init' package you can do so by modifying this `zarf.yaml` or any of the composed components that it references and running `zarf package create` at the root of the repository. You can learn more about creating a custom init package in the [Creating a Custom 'init' Package Tutorial](../5-zarf-tutorials/8-custom-init-packages.md). Upon deployment, the init package creates a `zarf` namespace within your K8s cluster and deploys pods, services, and secrets to that namespace based on the components selected for deployment. diff --git a/docs/3-create-a-zarf-package/index.md b/docs/3-create-a-zarf-package/index.md index f89a309240..21bc292bef 100644 --- a/docs/3-create-a-zarf-package/index.md +++ b/docs/3-create-a-zarf-package/index.md @@ -14,7 +14,7 @@ To learn more about creating a Zarf package, you can check out the following res - [Understanding Zarf Components](./2-zarf-components.md): A breakdown of the primary structure that makes up a Zarf Package. - [Zarf Schema Documentation](./4-zarf-schema.md): Documentation that covers the configuration available in a Zarf Package definition. - [The Package Create Lifecycle](./5-package-create-lifecycle.md): An overview of the lifecycle of `zarf package create`. -- [Creating a Zarf Package Tutorial](../6-zarf-tutorials/0-creating-a-zarf-package.md): A tutorial covering how to take an application and create a package for it. +- [Creating a Zarf Package Tutorial](../5-zarf-tutorials/0-creating-a-zarf-package.md): A tutorial covering how to take an application and create a package for it. ## Typical Creation Workflow: diff --git a/docs/4-deploy-a-zarf-package/index.md b/docs/4-deploy-a-zarf-package/index.md index 909bbeb989..f67fe2375c 100644 --- a/docs/4-deploy-a-zarf-package/index.md +++ b/docs/4-deploy-a-zarf-package/index.md @@ -6,7 +6,7 @@ Once the Zarf package has arrived in your target environment, run the `zarf pack :::tip -For a comprehensive tutorial of deploying a Zarf Package, see the [Deploying Zarf Packages tutorial](../6-zarf-tutorials/2-deploying-zarf-packages.md). +For a comprehensive tutorial of deploying a Zarf Package, see the [Deploying Zarf Packages tutorial](../5-zarf-tutorials/2-deploying-zarf-packages.md). ::: @@ -24,7 +24,7 @@ Zarf normally expects to operate against a Kubernetes cluster that has been [Zar - **YOLO Mode** - Yaml-OnLy Online mode allows for a faster deployment without requiring the `zarf init` command to be run beforehand. It can be useful for testing or for environments that manage their own registries and Git servers completely outside of Zarf. Given this mode does not use the [Zarf Agent](../8-faq.md#what-is-the-zarf-agent) any resources specified will need to be manually modified for the environment. -- **Cluster-less** - Zarf normally interacts with clusters and kubernetes resources, but it is possible to have Zarf perform actions before a cluster exists (including [deploying the cluster itself](../6-zarf-tutorials/5-creating-a-k8s-cluster-with-zarf.md)). These packages generally have more dependencies on the host or environment that they run within. +- **Cluster-less** - Zarf normally interacts with clusters and kubernetes resources, but it is possible to have Zarf perform actions before a cluster exists (including [deploying the cluster itself](../5-zarf-tutorials/5-creating-a-k8s-cluster-with-zarf.md)). These packages generally have more dependencies on the host or environment that they run within. ## Additional Resources @@ -33,7 +33,7 @@ To learn more about deploying a Zarf package, you can check out the following re - [Getting Started with Zarf](../1-getting-started/index.md): A step-by-step guide to installing Zarf and a description of the problems it seeks to solve. - [Zarf CLI Documentation](../2-the-zarf-cli/index.md): A comprehensive guide to using the Zarf command-line interface. - [The Package Deploy Lifecycle](./1-package-deploy-lifecycle.md): An overview of the lifecycle of `zarf package deploy`. -- [Deploying a Zarf Package Tutorial](../6-zarf-tutorials/3-deploy-a-retro-arcade.md): A tutorial covering how to deploy a package onto an initialized cluster. +- [Deploying a Zarf Package Tutorial](../5-zarf-tutorials/3-deploy-a-retro-arcade.md): A tutorial covering how to deploy a package onto an initialized cluster. - [The Zarf Init Package](../3-create-a-zarf-package/3-zarf-init-package.md): Learn about the 'init' package that is used to store resources for zarf packages. ## Typical Deployment Workflow: diff --git a/docs/6-zarf-tutorials/0-creating-a-zarf-package.md b/docs/5-zarf-tutorials/0-creating-a-zarf-package.md similarity index 100% rename from docs/6-zarf-tutorials/0-creating-a-zarf-package.md rename to docs/5-zarf-tutorials/0-creating-a-zarf-package.md diff --git a/docs/6-zarf-tutorials/1-initializing-a-k8s-cluster.md b/docs/5-zarf-tutorials/1-initializing-a-k8s-cluster.md similarity index 100% rename from docs/6-zarf-tutorials/1-initializing-a-k8s-cluster.md rename to docs/5-zarf-tutorials/1-initializing-a-k8s-cluster.md diff --git a/docs/6-zarf-tutorials/2-deploying-zarf-packages.md b/docs/5-zarf-tutorials/2-deploying-zarf-packages.md similarity index 100% rename from docs/6-zarf-tutorials/2-deploying-zarf-packages.md rename to docs/5-zarf-tutorials/2-deploying-zarf-packages.md diff --git a/docs/6-zarf-tutorials/3-deploy-a-retro-arcade.md b/docs/5-zarf-tutorials/3-deploy-a-retro-arcade.md similarity index 100% rename from docs/6-zarf-tutorials/3-deploy-a-retro-arcade.md rename to docs/5-zarf-tutorials/3-deploy-a-retro-arcade.md diff --git a/docs/6-zarf-tutorials/4-add-logging.md b/docs/5-zarf-tutorials/4-add-logging.md similarity index 100% rename from docs/6-zarf-tutorials/4-add-logging.md rename to docs/5-zarf-tutorials/4-add-logging.md diff --git a/docs/6-zarf-tutorials/5-creating-a-k8s-cluster-with-zarf.md b/docs/5-zarf-tutorials/5-creating-a-k8s-cluster-with-zarf.md similarity index 100% rename from docs/6-zarf-tutorials/5-creating-a-k8s-cluster-with-zarf.md rename to docs/5-zarf-tutorials/5-creating-a-k8s-cluster-with-zarf.md diff --git a/docs/6-zarf-tutorials/6-big-bang.md b/docs/5-zarf-tutorials/6-big-bang.md similarity index 100% rename from docs/6-zarf-tutorials/6-big-bang.md rename to docs/5-zarf-tutorials/6-big-bang.md diff --git a/docs/6-zarf-tutorials/7-publish-and-deploy.md b/docs/5-zarf-tutorials/7-publish-and-deploy.md similarity index 100% rename from docs/6-zarf-tutorials/7-publish-and-deploy.md rename to docs/5-zarf-tutorials/7-publish-and-deploy.md diff --git a/docs/6-zarf-tutorials/8-custom-init-packages.md b/docs/5-zarf-tutorials/8-custom-init-packages.md similarity index 100% rename from docs/6-zarf-tutorials/8-custom-init-packages.md rename to docs/5-zarf-tutorials/8-custom-init-packages.md diff --git a/docs/6-zarf-tutorials/_category_.json b/docs/5-zarf-tutorials/_category_.json similarity index 100% rename from docs/6-zarf-tutorials/_category_.json rename to docs/5-zarf-tutorials/_category_.json diff --git a/docs/6-zarf-tutorials/index.md b/docs/5-zarf-tutorials/index.md similarity index 100% rename from docs/6-zarf-tutorials/index.md rename to docs/5-zarf-tutorials/index.md diff --git a/examples/big-bang/README.md b/examples/big-bang/README.md index 8ae07a81dd..64ecd4560e 100644 --- a/examples/big-bang/README.md +++ b/examples/big-bang/README.md @@ -24,4 +24,4 @@ The `bigbang` noun sits within the `extensions` specification of Zarf and provid - `skipFlux` - Whether to skip deploying flux; Defaults to false - `valuesFiles` - The list of values files to pass to Big Bang; these will be merged together -To see a tutorial for the creation and deployment of this package see the [Big Bang Tutorial](../../docs/6-zarf-tutorials/6-big-bang.md). +To see a tutorial for the creation and deployment of this package see the [Big Bang Tutorial](../../docs/5-zarf-tutorials/6-big-bang.md). diff --git a/examples/dos-games/README.md b/examples/dos-games/README.md index 9d42139205..0085feeecd 100644 --- a/examples/dos-games/README.md +++ b/examples/dos-games/README.md @@ -1,6 +1,6 @@ # DOS Games in the Cluster! -This example provides the basis for Zarf's [Retro Arcade](../../docs/6-zarf-tutorials/3-deploy-a-retro-arcade.md) tutorial. It deploys a Dos Games arcade into the cluster and provides an easy way to connect and play games. +This example provides the basis for Zarf's [Retro Arcade](../../docs/5-zarf-tutorials/3-deploy-a-retro-arcade.md) tutorial. It deploys a Dos Games arcade into the cluster and provides an easy way to connect and play games. :::note diff --git a/examples/git-data/README.md b/examples/git-data/README.md index 761d37849f..f1c5158ef8 100644 --- a/examples/git-data/README.md +++ b/examples/git-data/README.md @@ -36,7 +36,7 @@ Full clones are used in this example with the `stefanprodan/podinfo` repository ## Example Usage -This example assumes you have already initialized a Zarf cluster. If that is not the case, refer to the [Initializing the Cluster Tutorial](../../docs/6-zarf-tutorials/1-initializing-a-k8s-cluster.md). Be sure when initializing the Zarf cluster to deploy the `git` component, or be ready to specify an external `git` repository. +This example assumes you have already initialized a Zarf cluster. If that is not the case, refer to the [Initializing the Cluster Tutorial](../../docs/5-zarf-tutorials/1-initializing-a-k8s-cluster.md). Be sure when initializing the Zarf cluster to deploy the `git` component, or be ready to specify an external `git` repository. ### Create the Zarf Package diff --git a/examples/postgres-operator/README.md b/examples/postgres-operator/README.md index c779ac82b3..0c82b95880 100644 --- a/examples/postgres-operator/README.md +++ b/examples/postgres-operator/README.md @@ -24,7 +24,7 @@ This example uses Zalando's Postgres operator as after looking at several altern 4. Build the package using `zarf package create examples/postgres-operator` -5. Create a Zarf cluster as described in the [Initializing a Cluster Tutorial](../../docs/6-zarf-tutorials/1-initializing-a-k8s-cluster.md/) +5. Create a Zarf cluster as described in the [Initializing a Cluster Tutorial](../../docs/5-zarf-tutorials/1-initializing-a-k8s-cluster.md/) ## Instructions diff --git a/examples/tiny-kafka/README.md b/examples/tiny-kafka/README.md index 455bbe97b1..8e5aa1da71 100644 --- a/examples/tiny-kafka/README.md +++ b/examples/tiny-kafka/README.md @@ -20,7 +20,7 @@ Before the magic can happen you have to do a few things: 1. Build the package using `zarf package create examples/tiny-kafka` -1. Create a Zarf cluster as described in the [Initializing a Cluster Tutorial](../../docs/6-zarf-tutorials/1-initializing-a-k8s-cluster.md/) +1. Create a Zarf cluster as described in the [Initializing a Cluster Tutorial](../../docs/5-zarf-tutorials/1-initializing-a-k8s-cluster.md/) ## Instructions diff --git a/examples/wordpress/README.md b/examples/wordpress/README.md index fdc2bbade0..4c2f2fbbb5 100644 --- a/examples/wordpress/README.md +++ b/examples/wordpress/README.md @@ -1,6 +1,6 @@ # WordPress -This example demonstrates how to use Zarf to deploy a WordPress blog into a cluster. It is used as a part of the [Creating a Zarf Package](../../docs/6-zarf-tutorials/0-creating-a-zarf-package.md) and [Deploying a Zarf Package](../../docs/6-zarf-tutorials/2-deploying-zarf-packages.md) tutorials. +This example demonstrates how to use Zarf to deploy a WordPress blog into a cluster. It is used as a part of the [Creating a Zarf Package](../../docs/5-zarf-tutorials/0-creating-a-zarf-package.md) and [Deploying a Zarf Package](../../docs/5-zarf-tutorials/2-deploying-zarf-packages.md) tutorials. :::info