Migrate Deploy Fleet on Hetzner Cloud (#13021)

This is the last of three PRs to migrate the deployment guides into the
docs.

Changes:

- Moved content from `/articles/deploying-fleet-on-hetzner-cloud.md` to
`/docs/deploy-on-hetzner-cloud.md`.
- Removed `/articles/deploy-fleet-on-hetzner-cloud.md`.
- Moved images from the guide to `/docs/images` and renamed.
- Deleted redundant images and article cover image.
- Set up a redirect `/deploy/deploying-fleet-on-hetzner-cloud` =>
`/docs/deploy/deploy-on-hetzner-cloud`.
- Set up a redirect `/deploy` => `/docs/deploy` to redirect "Deployment
guides" in the main nav to the docs.
- Updated display names (in the docs nav) for existing deployment guides
in the docs to match the naming convention (E.g., "Deploy Fleet on
CentOS" => "CentOS")
- Removed the deployment guides article category from the blog.

# Checklist for submitter

- [ ] Manual QA for all new/changed functionality

---------

Co-authored-by: Eric <eashaw@sailsjs.com>
Co-authored-by: Rachael Shaw <r@rachael.wtf>

docs/Deploy/Deploy-Fleet-on-AWS-ECS.md

@@ -1,4 +1,4 @@
-## Deploying Fleet on AWS ECS
+## Deploy Fleet on AWS ECS
 
 Terraform reference architecture can be found [here](https://github.com/fleetdm/fleet/tree/main/infrastructure/dogfood/terraform/aws)
 
@@ -22,7 +22,7 @@ Migrations in ECS can be achieved (and is recommended) by running [dedicated ECS
 
 Alternatively you can bake the prepare command into the same task definition see [here for a discussion](https://github.com/fleetdm/fleet/pull/1761#discussion_r697599457), but this not recommended for production environments.
 
-<meta name="title" value="Deploy Fleet on AWS ECS">
+<meta name="title" value="AWS ECS">
 <meta name="pageOrderInSection" value="400">
 <meta name="description" value="Information for deploying Fleet on AWS ECS.">
 <meta name="navSection" value="Deployment guides">

docs/Deploy/Deploy-Fleet-on-CentOS.md

@@ -1,4 +1,4 @@
-## Deploying Fleet on CentOS
+## Deploy Fleet on CentOS
 
 In this guide, we're going to install Fleet and all of its application dependencies on a CentOS 7.1 server. Once we have Fleet up and running, we're going to install osquery on that same CentOS 7.1 host and enroll it in Fleet. This should give you a good understanding of both how to install Fleet as well as how to install and configure osquery such that it can communicate with Fleet.
 
@@ -210,7 +210,7 @@ sudo /usr/bin/osqueryd \
 
 If you go back to [https://localhost:8080/hosts/manage](https://localhost:8080/hosts/manage), you should have a host successfully enrolled in Fleet!
 
-<meta name="title" value="Deploy Fleet on CentOS">
+<meta name="title" value="CentOS">
 <meta name="pageOrderInSection" value="600">
 <meta name="description" value="A guide to deploy Fleet on CentOS.">
 <meta name="navSection" value="Deployment guides">

docs/Deploy/Deploy-Fleet-on-Kubernetes.md

@@ -1,4 +1,4 @@
-## Deploying Fleet on Kubernetes
+## Deploy Fleet on Kubernetes
 
 In this guide, we will focus on deploying Fleet only on a Kubernetes cluster. Kubernetes is a container orchestration tool that was open sourced by Google in 2014.
 
@@ -242,7 +242,7 @@ In this output, you should see an "EXTERNAL-IP" column. If this column says `<pe
 
 Once you have the public IP address for the load balancer, create an A record in your DNS server of choice. You should now be able to browse to your Fleet server from the internet!
 
-<meta name="title" value="Deploy Fleet on Kubernetes">
+<meta name="title" value="Kubernetes">
 <meta name="pageOrderInSection" value="800">
 <meta name="description" value="A guide to deploy Fleet on Kubernetes.">
 <meta name="navSection" value="Deployment guides">

docs/Deploy/deploy-on-hetzner-cloud.md

@@ -1,12 +1,6 @@
-# Deploy Fleet on Hetzner Cloud with cloud-init and Docker
+# Deploy Fleet on Hetzner Cloud
 
-![Fleet + Hetzner](../website/assets/images/articles/deploying-fleet-on-hetzner-1600x900@2x.jpg)
-
-[Hetzner](https://hetzner.com) is a great price-performance provider for “root” (dedicated) and Virtual Private Servers (VPS) with high performance and generous bandwidth.
-
-While other providers may charge large amounts for computing and storage, Hetzner is cost-effective _and_ scalable, with great managed options (such as [Nextcloud](https://www.hetzner.com/storage/storage-share)).
-
-Let’s explore how you might deploy Fleet on [Hetzner Cloud](https://hetzner.com/cloud) as quickly as possible so you can use Fleet to orchestrate osquery on your endpoints.
+Learn how to deploy Fleet on Hetzner Cloud using cloud-init and Docker. [Hetzner](https://hetzner.com) is a great price-performance provider for “root” (dedicated) and Virtual Private Servers (VPS), offering high performance and generous bandwidth.
 
 ## The 2 minute setup
 
@@ -350,7 +344,7 @@ To follow this guide, you’ll need:
 
 First, purchase a machine (for example, a [Hetzner Cloud](https://hetzner.com/cloud) instance):
 
-![Hetzner cloud purchase machine screen](../website/assets/images/articles/deploy-fleet-on-hetzner-cloud-1-932x388%402x.png)
+![Hetzner cloud purchase machine screen](../docs/images/deploy-on-hetzner-cloud-1-932x388@2x.png)
 _Hetzner cloud purchase machine screen_
 
 After purchasing, you should know the IP address of your machine (and make sure you set up things like SSH [securely](https://community.hetzner.com/tutorials/securing-ssh)!)
@@ -707,9 +701,7 @@ Now that you’re ready to use Fleet and have a host installed. Here's some next
 - Import Fleet's [standard query library](https://fleetdm.com/docs/using-fleet/standard-query-library) to start asking questions about your hosts.
 - To run a more secure setup, consider creating a dedicated `fleet` user with Docker's support for user [namespaces](https://docs.docker.com/engine/security/userns-remap/). 
 
-<meta name="category" value="deploy">
-<meta name="authorGitHubUsername" value="ksatter">
-<meta name="authorFullName" value="Kathy Satterlee">
-<meta name="publishedOn" value="2022-06-27">
-<meta name="articleTitle" value="Deploy Fleet on Hetzner Cloud with cloud-init and Docker">
-<meta name="articleImageUrl" value="../website/assets/images/articles/deploying-fleet-on-hetzner-1600x900@2x.jpg">
+<meta name="title" value="Hetzner Cloud">
+<meta name="pageOrderInSection" value="700">
+<meta name="description" value="Learn how to deploy Fleet on Hetzner Cloud.">
+<meta name="navSection" value="Deployment guides">

website/assets/js/pages/articles/articles.page.js

@@ -47,10 +47,6 @@ parasails.registerPage('articles', {
           this.articleCategory = 'Announcements';
           this.categoryDescription = 'The latest news from Fleet.';
           break;
-        case 'deploy':
-          this.articleCategory = 'Deployment guides';
-          this.categoryDescription = 'Learn more about how to deploy Fleet.';
-          break;
         case 'podcasts':
           this.articleCategory = 'Podcasts';
           this.categoryDescription = 'Listen to the Future of Device Management podcast';

website/config/routes.js

@@ -456,6 +456,8 @@ module.exports.routes = {
   },
   'GET /docs/contributing/orbit-development-and-release-strategy': '/docs/contributing/fleetd-development-and-release-strategy',
   'GET /docs/contributing/run-locally-built-orbit': '/docs/contributing/run-locally-built-fleetd',
+  'GET /deploy/deploy-fleet-on-hetzner-cloud': '/docs/deploy/deploy-on-hetzner-cloud',
+  'GET /deploy': '/docs/deploy',
   'GET /deploy/deploying-fleet-on-aws-with-terraform': '/docs/deploy/deploy-on-aws-with-terraform',
   'GET /docs/deploy/server-installation': '/docs/deploy/introduction',
   'GET /handbook/company/ceo': '/handbook/ceo',

website/views/pages/articles/articles.ejs

@@ -4,7 +4,6 @@
       <div purpose="categories-and-search" class="d-flex flex-lg-row flex-column justify-content-lg-between justify-content-md-center justify-content-start" v-if="isArticlesLandingPage">
         <div purpose="categories" class="d-flex flex-md-row flex-column justify-content-start">
           <div purpose="category-filter" :class="[ filter === 'all' ? 'selected' : '']" @click="filterBy('all')">All</div>
-          <div purpose="category-filter" :class="[ filter === 'deploy' ? 'selected' : '']" @click="filterBy('deploy')">Deploy</div>
           <div purpose="category-filter" :class="[ filter === 'engineering' ? 'selected' : '']" @click="filterBy('engineering')">Engineering</div>
           <div purpose="category-filter" :class="[ filter === 'security' ? 'selected' : '']" @click="filterBy('security')">Security</div>
           <div purpose="category-filter" :class="[ filter === 'announcements' ? 'selected' : '']" @click="filterBy('announcements')">Announcements</div>