From 3cfc68c57cf24b71abfaba8cf6f0dd33a5939f33 Mon Sep 17 00:00:00 2001
From: mise en hache <137650446+mehhhhhhhhhhhhhhh@users.noreply.github.com>
Date: Wed, 14 Aug 2024 12:08:18 +0100
Subject: [PATCH] Eliminate broken link warnings (except those from docs in the
 main repo) (#322)

* Lint existing blog posts

Signed-off-by: Tom Spurling <tom@tspurling.co.uk>

* Use full URLs for /slack/ links

This causes them to be treated as external links rather than internal
links, so they open in a new tab and don't produce spurious
"broken link" warnings.

Signed-off-by: Tom Spurling <tom@tspurling.co.uk>

* Fix a couple of broken blog links

Signed-off-by: Tom Spurling <tom@tspurling.co.uk>

* Fix broken calendar link in blog post

Another static file with a trailing slash added by Docusaurus -- just
use a full URL to prevent this happening too.

Signed-off-by: Tom Spurling <tom@tspurling.co.uk>

---------

Signed-off-by: Tom Spurling <tom@tspurling.co.uk>
Co-authored-by: Tom Spurling <tom@tspurling.co.uk>
---
 .../2023-10-10-opentofus-new-office-hours.mdx |   2 +-
 ...12-19-opentofu-release-candidate-is-out.md | 190 +++++++++---------
 ...3-18-help-us-test-opentofu-1-7-0-alpha1.md |   3 +-
 blog/2024-04-18-opentofu-1-7-0-beta1.md       |   8 +-
 blog/2024-04-30-opentofu-1-7-0.md             |   8 +-
 ...6-24-help-us-test-opentofu-1-8-0-alpha1.md |  10 +-
 blog/2024-07-09-opentofu-1-8-0-beta-1.md      |  11 +-
 blog/2024-07-29-opentofu-1-8-0.md             |  10 +-
 docusaurus.config.ts                          |   2 +-
 src/components/Footer/index.tsx               |   2 +-
 10 files changed, 121 insertions(+), 125 deletions(-)

diff --git a/blog/2023-10-10-opentofus-new-office-hours.mdx b/blog/2023-10-10-opentofus-new-office-hours.mdx
index c6d79df8..926fec55 100644
--- a/blog/2023-10-10-opentofus-new-office-hours.mdx
+++ b/blog/2023-10-10-opentofus-new-office-hours.mdx
@@ -21,7 +21,7 @@ c_3f2dd3c1fe0ef4e93ef3fc456ca2dd219a2e8fd85f6b40750af16c3df370bf93@group.calenda
 import Button from "@site/src/components/Button";
 
 <Button
-  href="/OpenTofu-Events-Calendar.ics"
+  href="https://opentofu.org/OpenTofu-Events-Calendar.ics"
   variant="secondary"
   className="inline-flex"
   target="_blank"
diff --git a/blog/2023-12-19-opentofu-release-candidate-is-out.md b/blog/2023-12-19-opentofu-release-candidate-is-out.md
index ad91c12c..c2169021 100644
--- a/blog/2023-12-19-opentofu-release-candidate-is-out.md
+++ b/blog/2023-12-19-opentofu-release-candidate-is-out.md
@@ -1,96 +1,94 @@
----
-title: OpenTofu Release Candidate Is Out, GA Set for Jan 10th
-slug: opentofu-release-candidate-is-out
-image: /img/blog/opentofu-release-candidate-is-out.png
-authors:
-  - name: Roni Frantchi
-    title: OpenTofu Core Team, Director of R&D at env0
-    url: https://github.com/roni-frantchi
-    image_url: https://github.com/roni-frantchi.png
----
-
-[OpenTofu v1.6.0-rc1](https://github.com/opentofu/opentofu/releases/tag/v1.6.0-rc1), the final stage before the first stable release, is out today. It follows the quick succession of its [alpha](https://github.com/opentofu/opentofu/releases/tag/v1.6.0-alpha1) and [beta](https://github.com/opentofu/opentofu/releases/tag/v1.6.0-beta1) versions, on the road to an expected General Availability release on January 10, 2024, right after the holidays.
-
-This release includes bug fixes, stability improvements, and updates to documentation. Importantly, this version highlights the stability of our new [public registry](https://github.com/opentofu/opentofu/issues/741), which debuted with the v1.6.0-beta1 release three weeks ago, and has been extensively tested by us and the early adopters from the OpenTofu community.
-
-## From Idea to Release Candidate in 4 Months
-
-The OpenTofu journey has been a whirlwind, spanning from a proposition to a release candidate in just four months. 
-
-This is a major milestone for us, but also a bittersweet moment. Looking back on the beginning of our journey, there was hope that HashiCorp [would hear our appeal](https://opentofu.org/manifesto), reverse its decision and restore balance to the ecosystem.
-
-Yet, here we are … and everything that transpired after those initial weeks of surprise, hope, and disappointment can only be characterized as a case study of collaboration. Peers, community, and competitors all united to work together to preserve an open-source option for Infrastructure-as-Code.
-
-To recap, here are the major milestones so far:
-
-![An animated graphic visualizing the history of OpenTofu. August 10, 2023: Terraform shifts to Business Source License. August 15: OpenTF manifesto goes live. August 25: OpenTF is announced. August 31: Manifesto surges to 30k GitHub stars. September 5: OpenTF repo goes public. September 20: OpenTF joins the Linux Foundation as OpenTofu. October 4: Alpha released. November 29: Beta released. December 20: Stable release candidate. January 10, 2024: General availability.](/img/blog/opentofu-release-candidate-is-out-history.svg)
-
-As of December 18th, OpenTofu had surpassed [31,000 downloads](https://tooomm.github.io/github-release-stats/?username=opentofu&repository=opentofu), had 60 committers, and had seen over 1,000 pull requests and issues. The project’s main repository has also amassed over 16,450 GitHub stars on top of the 36,200+ GitHub stars for the [manifesto](https://github.com/opentofu/manifesto).
-
-Now, with that out of the way, let’s talk shop.
-
-## The Registry Challenge
-
-From the moment the [OpenTF fork was announced](https://opentofu.org/blog/the-opentofu-fork-is-now-available/), it was evident that a new public registry would be needed—an open-source substitute for the Terraform one, which is no longer accessible for non-Terraform projects following the [TOS changes](https://www.techtarget.com/searchitoperations/news/366555192/Terraform-Registry-TOS-change-stokes-open-source-ire).
-
-Similar to its predecessor in function, this new registry would have to be a highly available package resolution service for all providers and modules used by OpenTofu. Additionally, it had to meet other specific criteria, including:
-
-- The registry had to be as self-sufficient as possible and require as little maintenance as possible.
-- Anticipating increasing demand, it needed to be built for high availability and perform well at scale.
-- It should smoothly transition from HashiCorp's registry, following the 'drop-in replacement' approach.
-- Whatever we went with, it had to be open-source.
-
-## Brewing Together
-
-[Homebrew](https://brew.sh/) is the de facto standard package manager on macOS – just as [APK](https://docs.alpinelinux.org/user-handbook/0.1a/Working/apk.html) or [RPM](https://en.wikipedia.org/wiki/RPM_Package_Manager) is to Linux or [Chocolatey/Winget](https://chocolatey.org/) is to Windows. Its simple nature, open-source package database at its core, and efficiency for packaging applications inspired something similar that would be ideal for our needs, while its popularity served as evidence of its scalability.
-
-As we were discussing this, Homebrew lead [Mike McQuaid](https://github.com/MikeMcQuaid), who has been working on that project for more than 14 years, took notice of our conversation and joined the fray, contributing helpful insights about the repository structure:
-
-[![A screenshot of Mike McQuaid’s comments, contributing to the discussion about using Homebrew as a model for OpenTofu’s public registry.](/img/blog/opentofu-release-candidate-is-out-mike-mcquaid.png)](https://github.com/opentofu/opentofu/issues/741#issuecomment-1777544250)
-
-For me, this experience highlighted the importance of the Open Source concept and reminded me that without its inherently collaborative nature, engagements like that would be few and far between.
-
-This instinctive and uninhibited camaraderie is what Open Source is all about.
-
-## Implementation
-
-Amongst other things, Mike’s advice for us was to fragment the repo, to improve performance:
-
-> “We went through a ‘sharding’ process recently so that we have formulae/casks in our largest repositories split into subdirectories…The ‘git’ performance is dramatically better in this format.”
-
-Following up on it, we built the registry (https://registry.opentofu.org) as a collection of alphabetized subdirectories broken down by namespace. These were hydrated with information from all providers and modules currently available on GitHub, each with its own JSON file with metadata and other specifics.
-
-Importantly, using static files and hosting them on a Cloudflare R2 public bucket also lets us take full advantage of its CDN capabilities, ensuring performance and high availability with over 94% cache hit rates (on that note, huge THANKS to CloudFlare for sponsoring this project!).
-
-![A screenshot of the Cloudflare dashboard showing 30-day numbers: 7.21k unique visitors, 518k total requests, 92.13% cached, 15 GB total data served and 14 GB data cached.](/img/blog/opentofu-release-candidate-is-out-stats.png)
-
-Outside of our own tests, the four most requested files were:
-
-- `/.well-known/terraform.json`
-- `/v1/providers/hashicorp/null/versions`
-- `/v1/providers/hashicorp/template/versions`
-- `/v1/providers/hashicorp/aws/versions`
-
-With the registry live, we set up a [GitHub Action](https://github.com/opentofu/registry/actions/workflows/bump-versions.yml) to scan for updates to indexed resources. We also introduced an [IssueOps process](https://github.com/opentofu/registry/commit/74bfbcf9435433c70c9f923a36aa9d0b16ec2f5a) for adding new providers. With it in place, new submissions would be auto-processed and auto-validated when they go into the registry, with Issues providing context and transparency. 
-
-![A screenshot of the form allowing the addition of a new provider to the OpenTofu registry. The form fields are the provider name and DCO checkbox.](/img/blog/opentofu-release-candidate-is-out-issueops.png)
-
-We’re currently exploring a dedicated UI for package and documentation browsing. 
-
-## Next Stop: Jan 10th
-
-With the holidays in full swing, we decided to roll out a release candidate first and schedule the GA for January 10th. Meanwhile, you can already start testing OpenTofu by simply following the [directions provided here](https://opentofu.org/docs/intro/install/). It is a drop-in replacement so Terraform users will feel right at home, which is the whole idea.
-
-If you are interested in contributing to the project, please check out these [contribution guidelines](https://github.com/opentofu/opentofu/blob/main/CONTRIBUTING.md), and don’t forget to join our [Slack community](/slack/).
-
-Happy holidays!
-
-### P.S.
-
-While concluding the work on this post, and the upcoming release, we learned that Mitchell Hashimoto, HashiCorp’s legendary co-founder, [announced that he will leave the company](https://www.hashicorp.com/blog/mitchell-reflects-as-he-departs-hashicorp) after 11 years.
-
-Mitchell’s work on projects such as Vagrant, Consul, Vault, and of course Terraform is a source of inspiration for us and many others within the Open Source community.
-
-The entire OpenTofu team extends its heartfelt gratitude to Mitchell for all of his numerous contributions, as we eagerly anticipate learning about the next steps in his already remarkable journey.
-
-
+---
+title: OpenTofu Release Candidate Is Out, GA Set for Jan 10th
+slug: opentofu-release-candidate-is-out
+image: /img/blog/opentofu-release-candidate-is-out.png
+authors:
+  - name: Roni Frantchi
+    title: OpenTofu Core Team, Director of R&D at env0
+    url: https://github.com/roni-frantchi
+    image_url: https://github.com/roni-frantchi.png
+---
+
+[OpenTofu v1.6.0-rc1](https://github.com/opentofu/opentofu/releases/tag/v1.6.0-rc1), the final stage before the first stable release, is out today. It follows the quick succession of its [alpha](https://github.com/opentofu/opentofu/releases/tag/v1.6.0-alpha1) and [beta](https://github.com/opentofu/opentofu/releases/tag/v1.6.0-beta1) versions, on the road to an expected General Availability release on January 10, 2024, right after the holidays.
+
+This release includes bug fixes, stability improvements, and updates to documentation. Importantly, this version highlights the stability of our new [public registry](https://github.com/opentofu/opentofu/issues/741), which debuted with the v1.6.0-beta1 release three weeks ago, and has been extensively tested by us and the early adopters from the OpenTofu community.
+
+## From Idea to Release Candidate in 4 Months
+
+The OpenTofu journey has been a whirlwind, spanning from a proposition to a release candidate in just four months.
+
+This is a major milestone for us, but also a bittersweet moment. Looking back on the beginning of our journey, there was hope that HashiCorp [would hear our appeal](https://opentofu.org/manifesto), reverse its decision and restore balance to the ecosystem.
+
+Yet, here we are … and everything that transpired after those initial weeks of surprise, hope, and disappointment can only be characterized as a case study of collaboration. Peers, community, and competitors all united to work together to preserve an open-source option for Infrastructure-as-Code.
+
+To recap, here are the major milestones so far:
+
+![An animated graphic visualizing the history of OpenTofu. August 10, 2023: Terraform shifts to Business Source License. August 15: OpenTF manifesto goes live. August 25: OpenTF is announced. August 31: Manifesto surges to 30k GitHub stars. September 5: OpenTF repo goes public. September 20: OpenTF joins the Linux Foundation as OpenTofu. October 4: Alpha released. November 29: Beta released. December 20: Stable release candidate. January 10, 2024: General availability.](/img/blog/opentofu-release-candidate-is-out-history.svg)
+
+As of December 18th, OpenTofu had surpassed [31,000 downloads](https://tooomm.github.io/github-release-stats/?username=opentofu&repository=opentofu), had 60 committers, and had seen over 1,000 pull requests and issues. The project’s main repository has also amassed over 16,450 GitHub stars on top of the 36,200+ GitHub stars for the [manifesto](https://github.com/opentofu/manifesto).
+
+Now, with that out of the way, let’s talk shop.
+
+## The Registry Challenge
+
+From the moment the [OpenTF fork was announced](https://opentofu.org/blog/the-opentofu-fork-is-now-available/), it was evident that a new public registry would be needed—an open-source substitute for the Terraform one, which is no longer accessible for non-Terraform projects following the [TOS changes](https://www.techtarget.com/searchitoperations/news/366555192/Terraform-Registry-TOS-change-stokes-open-source-ire).
+
+Similar to its predecessor in function, this new registry would have to be a highly available package resolution service for all providers and modules used by OpenTofu. Additionally, it had to meet other specific criteria, including:
+
+- The registry had to be as self-sufficient as possible and require as little maintenance as possible.
+- Anticipating increasing demand, it needed to be built for high availability and perform well at scale.
+- It should smoothly transition from HashiCorp's registry, following the 'drop-in replacement' approach.
+- Whatever we went with, it had to be open-source.
+
+## Brewing Together
+
+[Homebrew](https://brew.sh/) is the de facto standard package manager on macOS – just as [APK](https://docs.alpinelinux.org/user-handbook/0.1a/Working/apk.html) or [RPM](https://en.wikipedia.org/wiki/RPM_Package_Manager) is to Linux or [Chocolatey/Winget](https://chocolatey.org/) is to Windows. Its simple nature, open-source package database at its core, and efficiency for packaging applications inspired something similar that would be ideal for our needs, while its popularity served as evidence of its scalability.
+
+As we were discussing this, Homebrew lead [Mike McQuaid](https://github.com/MikeMcQuaid), who has been working on that project for more than 14 years, took notice of our conversation and joined the fray, contributing helpful insights about the repository structure:
+
+[![A screenshot of Mike McQuaid’s comments, contributing to the discussion about using Homebrew as a model for OpenTofu’s public registry.](/img/blog/opentofu-release-candidate-is-out-mike-mcquaid.png)](https://github.com/opentofu/opentofu/issues/741#issuecomment-1777544250)
+
+For me, this experience highlighted the importance of the Open Source concept and reminded me that without its inherently collaborative nature, engagements like that would be few and far between.
+
+This instinctive and uninhibited camaraderie is what Open Source is all about.
+
+## Implementation
+
+Amongst other things, Mike’s advice for us was to fragment the repo, to improve performance:
+
+> “We went through a ‘sharding’ process recently so that we have formulae/casks in our largest repositories split into subdirectories…The ‘git’ performance is dramatically better in this format.”
+
+Following up on it, we built the registry (https://registry.opentofu.org) as a collection of alphabetized subdirectories broken down by namespace. These were hydrated with information from all providers and modules currently available on GitHub, each with its own JSON file with metadata and other specifics.
+
+Importantly, using static files and hosting them on a Cloudflare R2 public bucket also lets us take full advantage of its CDN capabilities, ensuring performance and high availability with over 94% cache hit rates (on that note, huge THANKS to CloudFlare for sponsoring this project!).
+
+![A screenshot of the Cloudflare dashboard showing 30-day numbers: 7.21k unique visitors, 518k total requests, 92.13% cached, 15 GB total data served and 14 GB data cached.](/img/blog/opentofu-release-candidate-is-out-stats.png)
+
+Outside of our own tests, the four most requested files were:
+
+- `/.well-known/terraform.json`
+- `/v1/providers/hashicorp/null/versions`
+- `/v1/providers/hashicorp/template/versions`
+- `/v1/providers/hashicorp/aws/versions`
+
+With the registry live, we set up a [GitHub Action](https://github.com/opentofu/registry/actions/workflows/bump-versions.yml) to scan for updates to indexed resources. We also introduced an [IssueOps process](https://github.com/opentofu/registry/commit/74bfbcf9435433c70c9f923a36aa9d0b16ec2f5a) for adding new providers. With it in place, new submissions would be auto-processed and auto-validated when they go into the registry, with Issues providing context and transparency.
+
+![A screenshot of the form allowing the addition of a new provider to the OpenTofu registry. The form fields are the provider name and DCO checkbox.](/img/blog/opentofu-release-candidate-is-out-issueops.png)
+
+We’re currently exploring a dedicated UI for package and documentation browsing.
+
+## Next Stop: Jan 10th
+
+With the holidays in full swing, we decided to roll out a release candidate first and schedule the GA for January 10th. Meanwhile, you can already start testing OpenTofu by simply following the [directions provided here](https://opentofu.org/docs/intro/install/). It is a drop-in replacement so Terraform users will feel right at home, which is the whole idea.
+
+If you are interested in contributing to the project, please check out these [contribution guidelines](https://github.com/opentofu/opentofu/blob/main/CONTRIBUTING.md), and don’t forget to join our [Slack community](https://opentofu.org/slack/).
+
+Happy holidays!
+
+### P.S.
+
+While concluding the work on this post, and the upcoming release, we learned that Mitchell Hashimoto, HashiCorp’s legendary co-founder, [announced that he will leave the company](https://www.hashicorp.com/blog/mitchell-reflects-as-he-departs-hashicorp) after 11 years.
+
+Mitchell’s work on projects such as Vagrant, Consul, Vault, and of course Terraform is a source of inspiration for us and many others within the Open Source community.
+
+The entire OpenTofu team extends its heartfelt gratitude to Mitchell for all of his numerous contributions, as we eagerly anticipate learning about the next steps in his already remarkable journey.
diff --git a/blog/2024-03-18-help-us-test-opentofu-1-7-0-alpha1.md b/blog/2024-03-18-help-us-test-opentofu-1-7-0-alpha1.md
index d6fdbd54..c9ccefed 100644
--- a/blog/2024-03-18-help-us-test-opentofu-1-7-0-alpha1.md
+++ b/blog/2024-03-18-help-us-test-opentofu-1-7-0-alpha1.md
@@ -16,13 +16,12 @@ Do not test this release on a production project! It is not a stable release!
 
 :::
 
-
 ## Downloading the alpha release
 
 The alpha release is available exclusively from the [GitHub Releases page](https://github.com/opentofu/opentofu/releases/tag/v1.7.0-alpha1). Please select the appropriate file for your platform. Here are some quick links:
 
 | Platform/Device                                                                 | Download link                                                                                                                                       |
-|---------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|
+| ------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
 | **Desktop Windows computer**<br />(64-bit)                                      | [tofu_1.7.0-alpha1_windows_amd64.zip](https://github.com/opentofu/opentofu/releases/download/v1.7.0-alpha1/tofu_1.7.0-alpha1_windows_amd64.zip)     |
 | **MacOS**<br />(Macbook M1 or higher; ARM64)                                    | [tofu_1.7.0-alpha1_darwin_arm64.tar.gz](https://github.com/opentofu/opentofu/releases/download/v1.7.0-alpha1/tofu_1.7.0-alpha1_darwin_arm64.tar.gz) |
 | **MacOS**<br />(Macbook pre-M1 or lower; AMD64)                                 | [tofu_1.7.0-alpha1_darwin_amd64.tar.gz](https://github.com/opentofu/opentofu/releases/download/v1.7.0-alpha1/tofu_1.7.0-alpha1_darwin_amd64.tar.gz) |
diff --git a/blog/2024-04-18-opentofu-1-7-0-beta1.md b/blog/2024-04-18-opentofu-1-7-0-beta1.md
index 6e82c61d..e3d7e324 100644
--- a/blog/2024-04-18-opentofu-1-7-0-beta1.md
+++ b/blog/2024-04-18-opentofu-1-7-0-beta1.md
@@ -19,7 +19,7 @@ Do not test this release on a production project! It is not a stable release!
 The beta release is available exclusively from the [GitHub Releases page](https://github.com/opentofu/opentofu/releases/tag/v1.7.0-beta1). Please select the appropriate file for your platform. Here are some quick links:
 
 | Platform/Device                                                                 | Download link                                                                                                                                    |
-|---------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|
+| ------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
 | **Desktop Windows computer**<br />(64-bit)                                      | [tofu_1.7.0-beta1_windows_amd64.zip](https://github.com/opentofu/opentofu/releases/download/v1.7.0-beta1/tofu_1.7.0-beta1_windows_amd64.zip)     |
 | **MacOS**<br />(Macbook M1 or higher; ARM64)                                    | [tofu_1.7.0-beta1_darwin_arm64.tar.gz](https://github.com/opentofu/opentofu/releases/download/v1.7.0-beta1/tofu_1.7.0-beta1_darwin_arm64.tar.gz) |
 | **MacOS**<br />(Macbook pre-M1 or lower; AMD64)                                 | [tofu_1.7.0-beta1_darwin_amd64.tar.gz](https://github.com/opentofu/opentofu/releases/download/v1.7.0-beta1/tofu_1.7.0-beta1_darwin_amd64.tar.gz) |
@@ -55,7 +55,7 @@ output "test" {
 
 :::tip
 
-If you are interested in a detailed breakdown of this functionality and some of the new unique features OpenTofu brings in this area, [join our live stream on April 24](https://www.youtube.com/watch?v=6OXBv0MYalY). 
+If you are interested in a detailed breakdown of this functionality and some of the new unique features OpenTofu brings in this area, [join our live stream on April 24](https://www.youtube.com/watch?v=6OXBv0MYalY).
 
 :::
 
@@ -80,7 +80,7 @@ output "id" {
 }
 ```
 
-In this new version you can now also declaratively import resources in a loop: 
+In this new version you can now also declaratively import resources in a loop:
 
 ```hcl
 variable "server_ids" {
@@ -131,7 +131,7 @@ terraform {
 
     state {
       method = method.aes_gcm.my_method
-      
+
       ## Remove the fallback block after migration:
       fallback{
         method = method.unencrypted.migration
diff --git a/blog/2024-04-30-opentofu-1-7-0.md b/blog/2024-04-30-opentofu-1-7-0.md
index 9018bb41..fa533d4b 100644
--- a/blog/2024-04-30-opentofu-1-7-0.md
+++ b/blog/2024-04-30-opentofu-1-7-0.md
@@ -1,13 +1,13 @@
 ---
-title: "OpenTofu 1.7.0 is out with State Encryption, Dynamic Provider-Defined Functions, and more" 
+title: "OpenTofu 1.7.0 is out with State Encryption, Dynamic Provider-Defined Functions, and more"
 slug: opentofu-1-7-0
 description: OpenTofu 1.7.0 is now available with full state encryption, dynamic provider-defined functions, the removed and loopable import blocks, new migration guides, and much more.
 image: /img/blog/opentofu-1-7-0.png
 ---
 
-In the last few months [since our first stable release](/blog/opentofu-is-going-ga/) the OpenTofu community and the core team have worked hand in hand to bring functionality to OpenTofu that has been requested for years.  We are proud to announce the immediate availability of [OpenTofu 1.7.0](https://github.com/opentofu/opentofu/releases/tag/v1.7.0), bringing you the following highlights:
+In the last few months [since our first stable release](/blog/opentofu-is-going-ga/) the OpenTofu community and the core team have worked hand in hand to bring functionality to OpenTofu that has been requested for years. We are proud to announce the immediate availability of [OpenTofu 1.7.0](https://github.com/opentofu/opentofu/releases/tag/v1.7.0), bringing you the following highlights:
 
-- [**End-to-end state encryption**](/docs/v1.7/intro/whats-new/#state-encryption) protects your state file from prying eyes, no matter what storage backend you use. You can provide your encryption passphrase securely using environment variables, or use a key management system such as AWS KMS, GCP KMS, or OpenBao. *This feature has been developed in collaboration with Stephan Bartels (Interhyp) and Alex Scheel from the OpenTofu community, whom we would like to thank for their work on this feature.*
+- [**End-to-end state encryption**](/docs/v1.7/intro/whats-new/#state-encryption) protects your state file from prying eyes, no matter what storage backend you use. You can provide your encryption passphrase securely using environment variables, or use a key management system such as AWS KMS, GCP KMS, or OpenBao. _This feature has been developed in collaboration with Stephan Bartels (Interhyp) and Alex Scheel from the OpenTofu community, whom we would like to thank for their work on this feature._
 - [**Dynamic provider-defined functions**](/docs/v1.7/intro/whats-new/#provider-defined-functions) let a provider not only provide resources, but also native functions you can use in your OpenTofu code. What's more, we added an OpenTofu-only feature to let providers dynamically define custom functions based on your configuration. This enhancement allows you to fully integrate other programming languages as [shown in our live stream](https://www.youtube.com/watch?v=6OXBv0MYalY). You can try out this functionality with our experimental [Lua](https://github.com/opentofu/terraform-provider-lua) and [Go](https://github.com/opentofu/terraform-provider-go) providers.
 - [**The removed block**](/docs/intro/whats-new/#removed-block) lets you mark OpenTofu-created resources for removal from the state file, but still keep the infrastructure you created.
 - [**Loopable import blocks**](/docs/intro/whats-new/#loopable-import-blocks) let you bulk-import resources declaratively in your OpenTofu code, helping with large-scale migrations.
@@ -43,4 +43,4 @@ OpenTofu is first and foremost a community-driven project. We are looking forwar
 
 While much of OpenTofu 1.8 is still in planning, we are currently finalizing a proposal for a feature that lets you [use variables as module sources, backend configuration, and more](https://github.com/opentofu/opentofu/issues/1042). Early evaluation of variables has been requested in over 30 issues so far and is one of the most-requested features in OpenTofu.
 
-If you have a feature you would like to see in OpenTofu, please don't hesitate to [open an issue](https://github.com/opentofu/opentofu/issues/new/choose) or [reach out to us on Slack](/slack/).
\ No newline at end of file
+If you have a feature you would like to see in OpenTofu, please don't hesitate to [open an issue](https://github.com/opentofu/opentofu/issues/new/choose) or [reach out to us on Slack](https://opentofu.org/slack/).
diff --git a/blog/2024-06-24-help-us-test-opentofu-1-8-0-alpha1.md b/blog/2024-06-24-help-us-test-opentofu-1-8-0-alpha1.md
index 5921ac88..0a3be17c 100644
--- a/blog/2024-06-24-help-us-test-opentofu-1-8-0-alpha1.md
+++ b/blog/2024-06-24-help-us-test-opentofu-1-8-0-alpha1.md
@@ -4,9 +4,9 @@ slug: help-us-test-opentofu-1-8-0-alpha1
 image: /img/blog/help-us-test-opentofu-1-8-0-alpha1.png
 ---
 
-Hey there, OpenTofu community! Since the last OpenTofu release we've been hard at work bringing you a much-needed improvement to the .tf language: the ability to **use variables in backends, module sources, and the encryption configuration** (*early variable/locals evaluation*). This is currently the [top-voted issue on the OpenTofu GitHub](https://github.com/opentofu/opentofu/issues/1496) and has, in various forms, been requested for years with OpenTofu's predecessor.
+Hey there, OpenTofu community! Since the last OpenTofu release we've been hard at work bringing you a much-needed improvement to the .tf language: the ability to **use variables in backends, module sources, and the encryption configuration** (_early variable/locals evaluation_). This is currently the [top-voted issue on the OpenTofu GitHub](https://github.com/opentofu/opentofu/issues/1496) and has, in various forms, been requested for years with OpenTofu's predecessor.
 
-Additionally, we are bringing you a feature that lets you use new OpenTofu features while still keeping compatibility with Terraform as well as the ability to override resources and data sources in `tofu test`. The release also includes a host of smaller improvements and bugfixes to various parts of OpenTofu [listed in the changelog](https://github.com/opentofu/opentofu/blob/main/CHANGELOG.md). 
+Additionally, we are bringing you a feature that lets you use new OpenTofu features while still keeping compatibility with Terraform as well as the ability to override resources and data sources in `tofu test`. The release also includes a host of smaller improvements and bugfixes to various parts of OpenTofu [listed in the changelog](https://github.com/opentofu/opentofu/blob/main/CHANGELOG.md).
 
 Now we'd like to ask you for help: we have done everything we could to make sure that the new alpha release doesn't break anything, and we need your help to get this release tested. If you have a **non-production** setup that you would be willing to test any of the new features on, please give it a try and give us [feedback using a GitHub issue](https://github.com/opentofu/opentofu/issues/new/choose), even if it's just telling us that everything went well.
 
@@ -18,13 +18,12 @@ Do not test this release on a production project! It is not a stable release!
 
 :::
 
-
 ## Downloading the alpha release
 
 The alpha release is available exclusively from the [GitHub Releases page](https://github.com/opentofu/opentofu/releases/tag/v1.8.0-alpha1). Please select the appropriate file for your platform. Here are some quick links:
 
 | Platform/Device                                                                 | Download link                                                                                                                                       |
-|---------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|
+| ------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
 | **Desktop Windows computer**<br />(64-bit)                                      | [tofu_1.8.0-alpha1_windows_amd64.zip](https://github.com/opentofu/opentofu/releases/download/v1.8.0-alpha1/tofu_1.8.0-alpha1_windows_amd64.zip)     |
 | **MacOS**<br />(Macbook M1 or higher; ARM64)                                    | [tofu_1.8.0-alpha1_darwin_arm64.tar.gz](https://github.com/opentofu/opentofu/releases/download/v1.8.0-alpha1/tofu_1.8.0-alpha1_darwin_arm64.tar.gz) |
 | **MacOS**<br />(Macbook pre-M1; AMD64)                                          | [tofu_1.8.0-alpha1_darwin_amd64.tar.gz](https://github.com/opentofu/opentofu/releases/download/v1.8.0-alpha1/tofu_1.8.0-alpha1_darwin_amd64.tar.gz) |
@@ -37,7 +36,7 @@ For the releases above, please unpack the archive and you should find the `tofu`
 
 This feature lets you use variables and locals for **backends**, **module sources** and **encryption configuration** as long as they are not dependent on resources, data sources or module outputs. This works even if a local is referencing a variable, for example. This is only the first in a series of improvements that will make the .tf code more flexible with more improvements coming in future releases.
 
-The `tofu init` command will now consume your `.tfvars` file and let you specify variables using the `-var` and `-var-file` options. Please note that this alpha release will *not* prompt you for missing variables, which is a feature we will add later. Note, that `tofu init` will fail if it is missing variables needed for static evaluation.
+The `tofu init` command will now consume your `.tfvars` file and let you specify variables using the `-var` and `-var-file` options. Please note that this alpha release will _not_ prompt you for missing variables, which is a feature we will add later. Note, that `tofu init` will fail if it is missing variables needed for static evaluation.
 
 For example, if you wanted to use the same configuration for your S3 backend and your AWS provider, you can now do this:
 
@@ -173,4 +172,3 @@ While this will not fully test the entire provisioning, it will highlight errors
 ## Providing feedback
 
 Thank you for taking the time to test this preview release. If you have any feedback, please use [a GitHub issue](https://github.com/opentofu/opentofu/issues/new/choose) or chat with us on the [OpenTofu Slack](https://opentofu.org/slack/).
-
diff --git a/blog/2024-07-09-opentofu-1-8-0-beta-1.md b/blog/2024-07-09-opentofu-1-8-0-beta-1.md
index a0d8348b..f92c69b4 100644
--- a/blog/2024-07-09-opentofu-1-8-0-beta-1.md
+++ b/blog/2024-07-09-opentofu-1-8-0-beta-1.md
@@ -27,7 +27,7 @@ On 2024/07/11, 1.8.0-beta2 was released to address issues present in 1.8.0-beta1
 The beta release is available exclusively from the [GitHub Releases page](https://github.com/opentofu/opentofu/releases/tag/v1.8.0-beta2). Please select the appropriate file for your platform. Here are some quick links:
 
 | Platform/Device                                                                 | Download link                                                                                                                                    |
-|---------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|
+| ------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
 | **Desktop Windows computer**<br />(64-bit)                                      | [tofu_1.8.0-beta2_windows_amd64.zip](https://github.com/opentofu/opentofu/releases/download/v1.8.0-beta2/tofu_1.8.0-beta2_windows_amd64.zip)     |
 | **MacOS**<br />(Macbook M1 or higher; ARM64)                                    | [tofu_1.8.0-beta2_darwin_arm64.tar.gz](https://github.com/opentofu/opentofu/releases/download/v1.8.0-beta2/tofu_1.8.0-beta2_darwin_arm64.tar.gz) |
 | **MacOS**<br />(Macbook pre-M1; AMD64)                                          | [tofu_1.8.0-beta2_darwin_amd64.tar.gz](https://github.com/opentofu/opentofu/releases/download/v1.8.0-beta2/tofu_1.8.0-beta2_darwin_amd64.tar.gz) |
@@ -61,6 +61,7 @@ resource "aws_instance" "web" {
 ```
 
 Instead of querying the AMI ID and spinning up the instance, we can write test code as follows:
+
 ```hcl
 // This block will prevent OpenTofu from configuring aws provider.
 // All provider's resources and data sources will be mocked.
@@ -150,7 +151,7 @@ While this will not fully test the entire provisioning, it will highlight errors
 
 Introduced in OpenTofu 1.8.0-alpha1, this feature lets you use variables and locals for **backends**, **module sources** and **encryption configuration** as long as they are not dependent on resources, data sources or module outputs. This works even if a local is referencing a variable, for example. This is only the first in a series of improvements that will make the .tf code more flexible with more improvements coming in future releases.
 
-The `tofu init` command will now consume your `.tfvars` file and let you specify variables using the `-var` and `-var-file` options. Please note that this alpha release will *not* prompt you for missing variables, which is a feature we will add later. Note, that `tofu init` will fail if it is missing variables needed for static evaluation.
+The `tofu init` command will now consume your `.tfvars` file and let you specify variables using the `-var` and `-var-file` options. Please note that this alpha release will _not_ prompt you for missing variables, which is a feature we will add later. Note, that `tofu init` will fail if it is missing variables needed for static evaluation.
 
 For example, if you wanted to use the same configuration for your S3 backend and your AWS provider, you can now do this:
 
@@ -224,6 +225,7 @@ Since we are now adding features to OpenTofu that are not present in Terraform,
 ### Static Variable Planing
 
 Static variables are now handled correctly when embedded in plan files. This was [reported as a bug](https://github.com/opentofu/opentofu/issues/1768) found in 1.8.0-alpha1.
+
 ```bash
 tofu plan -out=tofu.tfstate -var="param=value"
 # Variables are correctly read from the given plan and should not be specified via CLI
@@ -238,10 +240,10 @@ Also included in the beta is [improvements in error messages produced by misconf
 ```
 ╷
 │ Error: Insufficient features blocks
-│ 
+│
 │   on <empty> line 0:
 │   (source code not available)
-│ 
+│
 │ At least 1 "features" blocks are required.
 ╵
 ```
@@ -251,4 +253,3 @@ This error message will now include information about which provider is encounte
 ## Providing feedback
 
 Thank you for taking the time to test this preview release. If you have any feedback, please use [a GitHub issue](https://github.com/opentofu/opentofu/issues/new/choose) or chat with us on the [OpenTofu Slack](https://opentofu.org/slack/).
-
diff --git a/blog/2024-07-29-opentofu-1-8-0.md b/blog/2024-07-29-opentofu-1-8-0.md
index 66440914..ac4e55de 100644
--- a/blog/2024-07-29-opentofu-1-8-0.md
+++ b/blog/2024-07-29-opentofu-1-8-0.md
@@ -1,21 +1,21 @@
 ---
-title: OpenTofu 1.8.0 is out with Early Evaluation, Provider Mocking, and a Coder-Friendly Future 
+title: OpenTofu 1.8.0 is out with Early Evaluation, Provider Mocking, and a Coder-Friendly Future
 slug: opentofu-1-8-0
 description: OpenTofu 1.8.0 is now available with early variable/locals evaluation, provider mocking for tests, and a future that makes every-day Tofu code a lot simpler.
 image: /img/blog/opentofu-1.8.0.png
 ---
 
-Since the [1.7 release](/blog/opentofu-1.7.0), the OpenTofu community and core team have been hard at work on much-requested features, making `.tf` code easier to write, reducing unnecessary boilerplate, improving performance, and more. We are happy to announce the [immediate availability of OpenTofu 1.8](https://github.com/opentofu/opentofu/releases/tag/v1.8.0) with the following main features:
+Since the [1.7 release](/blog/opentofu-1-7-0), the OpenTofu community and core team have been hard at work on much-requested features, making `.tf` code easier to write, reducing unnecessary boilerplate, improving performance, and more. We are happy to announce the [immediate availability of OpenTofu 1.8](https://github.com/opentofu/opentofu/releases/tag/v1.8.0) with the following main features:
 
 - [You can now use variables and locals in places](/docs/intro/whats-new/#early-variablelocals-evaluation) that were not previously available, such as module sources, backend configuration and state encryption. Being able to assign variables more dynamically will eliminate code duplication and boilerplate code, making projects easier to maintain. However, we are not stopping there: future releases will see [dynamic provider configuration assignments](https://github.com/opentofu/opentofu/issues/300) and more.
 - Since Terraform doesn't support these new language features, [OpenTofu now supports the `.tofu` file extension](/docs/intro/whats-new/#override-files-for-opentofu-keeping-compatibility). When a file with the `.tofu` extension is present, OpenTofu will ignore the identically named `.tf` file. Using this new file extension, module authors can use the new features of OpenTofu and still keep older code around for compatibility.
-- You can now use [provider mocking](/docs/intro/whats-new/#provider-mocking-in-tofu-test) as well as [resource overrides]( /docs/intro/whats-new/#resource-overrides-in-tofu-test) with `tofu test`. This allows for more flexible testing similar to traditional software testing methods.
+- You can now use [provider mocking](/docs/intro/whats-new/#provider-mocking-in-tofu-test) as well as [resource overrides](/docs/intro/whats-new/#resource-overrides-in-tofu-test) with `tofu test`. This allows for more flexible testing similar to traditional software testing methods.
 
 You can find the full list of improvements and changes on the [What's new in OpenTofu 1.8?](/docs/intro/whats-new/) page.
 
 ## Growth continues: ~30% increase in registry traffic
 
-While we don't believe in tracking our users and OpenTofu does not have phone-home telemetry, we can observe a trajectory based on registry usage. In our [last release post](/blog/opentofu-1.7.0) 3 months ago we recorded a peak of roughly 1.4 million daily requests to the registry. We are happy to report that this number has increased by roughly 30% to almost 1.8 million peak daily requests.
+While we don't believe in tracking our users and OpenTofu does not have phone-home telemetry, we can observe a trajectory based on registry usage. In our [last release post](/blog/opentofu-1-7-0) 3 months ago we recorded a peak of roughly 1.4 million daily requests to the registry. We are happy to report that this number has increased by roughly 30% to almost 1.8 million peak daily requests.
 
 ![A graph showing the OpenTofu registry requests per day.](/img/blog/opentofu-registry-july-2024.svg)
 
@@ -47,7 +47,7 @@ Please give these libraries a go (pun totally intended) and let us know what fun
 
 ## The future: more dynamic functionality, even more community-focussed development
 
-Ever since we created our [top-ranking issues](https://github.com/opentofu/opentofu/issues/1496) list, new votes from the community started pouring in, giving us a strong signal on where you want us to take OpenTofu. By a large margin, the top-requested issue was one we partly solved in this release by introducing early evaluation for variables and locals. However, this is only the first step. As you helped us test the early alpha and beta of this release, one of the most commonly asked questions was: *“When can I use early evaluation to dynamically configure providers?”*
+Ever since we created our [top-ranking issues](https://github.com/opentofu/opentofu/issues/1496) list, new votes from the community started pouring in, giving us a strong signal on where you want us to take OpenTofu. By a large margin, the top-requested issue was one we partly solved in this release by introducing early evaluation for variables and locals. However, this is only the first step. As you helped us test the early alpha and beta of this release, one of the most commonly asked questions was: _“When can I use early evaluation to dynamically configure providers?”_
 
 The top-voted enhancement reflects a similar sentiment. In 1.9 and beyond, we aim to bring you dynamic provider assignments and more early-evaluation features, which let you cut down on the unnecessary code repetition even further. If you are interested in this topic, give the [corresponding RFC a read](https://github.com/opentofu/opentofu/blob/main/rfc/20240513-static-evaluation-providers.md).
 
diff --git a/docusaurus.config.ts b/docusaurus.config.ts
index 1da0e83a..d6c1e484 100644
--- a/docusaurus.config.ts
+++ b/docusaurus.config.ts
@@ -330,7 +330,7 @@ const config: Config = {
         },
         {
           type: "custom-social-icon-link-navbar-item",
-          href: "/slack",
+          href: "https://opentofu.org/slack/",
           position: "right",
           name: "slack",
           label: "Join us on Slack",
diff --git a/src/components/Footer/index.tsx b/src/components/Footer/index.tsx
index c7c8ce57..3e2a9085 100644
--- a/src/components/Footer/index.tsx
+++ b/src/components/Footer/index.tsx
@@ -66,7 +66,7 @@ export default function Footer({ links }: FooterProps) {
           />
           <SocialIconLink
             name="slack"
-            href="/slack"
+            href="https://opentofu.org/slack/"
             label="Join us on Slack"
             hiddenLabel
           />