Add Gruntwork Way! (#2852)

* Add Gruntwork Way!

Take the contents of https://github.com/gruntwork-io/way and add it to the main docs site.

* Bold first section names

* Remove old repo reference

* Apply suggestions from CodeRabbit

All typo fixes.

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>

* Update cspell config

* Rename folders, fix relative links

* Make a few polish improvements to catalog, runbooks, and components

* Add husky to enforce spellcheck as a pre-commit hook.

* Intentional spelling error to test pre-commit hook

* Attempt to fix Husky config

* Remove husky; fix spellcheck

Hit my time limit for getting it working.

* Trivial wording tweak

---------

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>

Author: josh-padnick

cspell.json

@@ -1,17 +1,151 @@
 {
-    "dictionaries": [
-        "custom-dictionary"
-    ],
-    // Tell CSpell about your dictionary
-    "dictionaryDefinitions": [
-        {
-            // The name of the dictionary is used to look it up.
-            "name": "custom-dictionary",
-            // Path to the custom word file. Relative to this `cspell.json` file.
-            "path": "./custom-dictionary.txt",
-            // Some editor extensions will use `addWords` for adding words to your
-            // personal dictionary.
-            "addWords": true
-        }
-    ]
-}
+  "version": "0.2",
+  "language": "en",
+  "words": [
+    "Gruntwork",
+    "gruntwork",
+    "GitOps",
+    "Docusaurus",
+    "runbooks",
+    "terraform",
+    "terragrunt",
+    "Terragrunt",
+    "kubernetes",
+    "kubectl",
+    "autoscaling",
+    "monorepo",
+    "microservices",
+    "infra",
+    "DevOps",
+    "OpenTofu",
+    "opentofu",
+    "Tofu",
+    "prebuilt",
+    "repo",
+    "repos",
+    "serverless",
+    "cloudformation",
+    "elasticache",
+    "cicd",
+    "gitignore",
+    "cursorrules",
+    "npmignore",
+    "lockfile",
+    "lockfiles",
+    "docstrings",
+    "codebase",
+    "codebases",
+    "runbook",
+    "dockerfile",
+    "dockerfiles",
+    "orchestrator",
+    "orchestrators",
+    "customizable",
+    "composability",
+    "scalability",
+    "observability",
+    "linter",
+    "linters",
+    "linting",
+    "Yousif",
+    "Oreoluwa",
+    "Agunbiade",
+    "Yevgeniy",
+    "Brikman",
+    "Rahul",
+    "Vohra",
+    "Nana",
+    "Pulumi",
+    "pulumi",
+    "Rego",
+    "Sonatype",
+    "Pgvector",
+    "karpenter",
+    "Karpenter",
+    "MTTR",
+    "MTTP",
+    "inhouse",
+    "SOURCER",
+    "mydomain",
+    "terratest",
+    "Terratest",
+    "terratests",
+    "tailscale",
+    "sdlc",
+    "acmecorp",
+    "envcommon",
+    "tada",
+    "codeowners",
+    "jsonencode",
+    "chdir",
+    "rulesets",
+    "controltower",
+    "awscli",
+    "passwordless",
+    "coolapp",
+    "acmeco",
+    "grunty",
+    "yamldecode",
+    "mgmt",
+    "tfstate",
+    "baselining",
+    "baselined",
+    "clickops",
+    "terrascan",
+    "steampipe",
+    "infracost",
+    "kubergrunt",
+    "terraformrc",
+    "tfvars",
+    "fargate",
+    "keypair",
+    "mimecast",
+    "slugified",
+    "dlist",
+    "DEPENDENCYID",
+    "subfolders",
+    "terrapatch",
+    "Terrapatch",
+    "KodeKloud",
+    "preconfigured",
+    "projectprefix",
+    "GOVCLOUD",
+    "rollouts",
+    "myvars",
+    "myfile",
+    "minamijoyo",
+    "tfupdate",
+    "hcledit",
+    "infrachanges",
+    "Entra",
+    "GLMU",
+    "myprodsa",
+    "azuread",
+    "mysa",
+    "deinterlaced",
+    "rolename",
+    "ACCOUNTNAME"
+  ],
+  "ignoreWords": [],
+  "ignorePaths": [
+    "node_modules",
+    "build",
+    "dist",
+    ".git",
+    "*.lockb",
+    "bun.lockb",
+    "yarn.lock",
+    "package-lock.json",
+    ".cspell.json",
+    "tsconfig.json",
+    "*.min.js",
+    "*.map"
+  ],
+  "ignoreRegExpList": [
+    "/https?:\\/\\/[^\\s]+/g",
+    "/```[\\s\\S]*?```/g"
+  ],
+  "allowCompoundWords": true,
+  "dictionaries": ["typescript", "node", "npm", "bash", "markdown"],
+  "enableFiletypes": ["markdown", "mdx", "typescript", "javascript", "json"]
+}

custom-dictionary.txt

@@ -0,0 +1,10 @@
+---
+sidebar_position: 10
+sidebar_class_name: way-top-level-item
+---
+
+# Authorship
+
+The Gruntwork Way was originally authored by [Josh Padnick](https://joshpadnick.com) with input from fellow Grunts Yousif Akbar, Lewis Christie, Oreoluwa Agunbiade, Brian Torres, [Yevgeniy Brikman](https://ybrikman.com) through his book [The Fundamentals of DevOps and Software Delivery](https://www.fundamentals-of-devops.com/), and especially Eben Eliason.
+
+It is intended to be a living, evolving knowledge set, so it is our hope that if you find something you believe can be improved that you will [open a Pull Request](/2.0/way/intro/share-your-feedback) suggesting it!

docs/2.0/way/authorship.md

@@ -0,0 +1,6 @@
+{
+  "label": "Introduction",
+  "position": 1,
+  "className": "way-top-level-item"
+}
+

docs/2.0/way/intro/_category_.json

@@ -0,0 +1,30 @@
+---
+title: How To Use This
+sidebar_position: 3
+---
+
+To get the most out of the Gruntwork Way, start by making sure you understand the big picture.
+
+## The Gruntwork Way Big Picture
+
+First, a **developer platform** is the product your platform team builds to balance three essential concerns: enabling developers to move fast ([velocity](/2.0/way/why/velocity)), meeting business needs like security, cost, and compliance ([governance](/2.0/way/why/governance)), and avoiding unsustainable technical debt ([maintainability](/2.0/way/why/maintainability)).
+
+To build a successful platform, you need to combine three types of building blocks: [patterns](/2.0/way/platform/patterns/overview) (pre-built solutions to common infrastructure problems), [platform components](/2.0/way/platform/components/overview) (the machinery for deploying and managing infrastructure), and [interfaces](/2.0/way/platform/interfaces/overview) (how developers interact with your platform).
+
+Finally, everything in this framework is based on the [guiding principles](/2.0/way/principles/overview) we've discovered through years of building and refining developer platforms.
+
+## Using the Gruntwork Way
+
+Once you understand these foundational concepts, there are two primary ways to use the Gruntwork Way.
+
+### Option 1: Read it comprehensively
+
+You can work through this framework from start to finish to build a complete mental model of developer platforms. This approach works well if you're just getting started or want to strengthen your overall understanding.
+
+### Option 2: Use it as a reference
+
+Alternatively, you can jump directly to the sections most relevant to your current challenges. This approach works well once you understand the fundamentals (which you just read above!) and need guidance on a specific aspect of your platform.
+
+## Next
+
+Alright, let's dive into the framework that helps you build platforms developers actually want to use!

docs/2.0/way/intro/how-to-use-this.md

@@ -0,0 +1,13 @@
+---
+title: Share your feedback
+sidebar_position: 4
+---
+
+- This framework is useful because it's opinionated.
+- Our opinions are based on nearly a decade of experience across hundreds of customers and thousand of customer conversations
+- But maybe your mileage varies, or maybe we got it wrong. If so, tell us!
+- To give feedback, go to https://github.com/gruntwork-io/docs and create a GitHub Issue or Pull Request. Alternatively click on the "Edit this page" link at the bottom of each page.
+
+### Next
+
+Alright, let's dive into the framework that helps you build platforms developers actually want to use!

docs/2.0/way/intro/share-your-feedback.md

@@ -0,0 +1,44 @@
+---
+title: Welcome!
+sidebar_position: 1
+---
+
+# Welcome!
+
+The **Gruntwork Way** is Gruntwork's official framework for how to build a world-class developer platform.
+
+## What's a developer platform?
+
+Nearly every company on the planet needs software, and when companies write their own software with more than a few developers, the same common needs arise:
+
+1. Enable developers to move fast ([velocity](/2.0/way/why/velocity))
+2. ...while meeting the other needs of the business like security, cost, and compliance ([governance](/2.0/way/why/governance))
+3. ...without accumulating an unsustainable level of debt ([maintainability](/2.0/way/why/maintainability))
+
+A **developer platform** is the product your platform team builds to balance these three concerns. It consists of three essential building blocks:
+
+- [Patterns](/2.0/way/platform/patterns/overview) - pre-built solutions to common infrastructure problems
+- [Platform components](/2.0/way/platform/components/overview) - the machinery for deploying and managing infrastructure
+- [Interfaces](/2.0/way/platform/interfaces/overview) - how developers interact with your platform.
+
+Together, these enable developers to move fast while meeting the needs of the business, and to do so in a way that incurs manageable levels of debt.
+
+## Why read this framework
+
+Making sense of developer platforms can be confusing. We've found bits and pieces of insights scattered across blog posts, vendor solutions, and industry talks, but none of these presents a holistic way to think about developer platforms.
+
+This framework will help you build comprehensive clarity.
+
+Ultimately, that clarity will empower you to build a successful developer platform.
+
+## Why trust Gruntwork
+
+We've spent years building expertise on how to deliver software effectively by serving as:
+
+* **Authors** - We've written leading books and guides, including [Terraform Up & Running](https://www.terraformupandrunning.com/), [Fundamentals of DevOps and Software Delivery](https://www.fundamentals-of-devops.com/?ref=blog-post-series), ,[The Startup CTO's Handbook](https://github.com/ZachGoldberg/Startup-CTO-Handbook), and [A Comprehensive Guide to Scaling Apps on AWS](https://joshpadnick.com/posts/a-comprehensive-guide-to-scaling-apps-on-aws-part-1/).
+* **Makers** - We've created leading open source DevOps tooling like [OpenTofu](https://opentofu.org/) (co-founder), [Terragrunt](https://terragrunt.gruntwork.io/), [Terratest](https://terratest.gruntwork.io/), [Runbooks](https://runbooks.gruntwork.io), [Boilerplate](https://github.com/gruntwork-io/boilerplate), and [Cloud Nuke](https://github.com/gruntwork-io/cloud-nuke).
+* **Experts** - As a vendor, we've equipped over 500 companies and thousands of engineers with AWS, DevOps, and Platform Engineering best practices.
+
+## Next
+
+Now let's learn more about who we wrote the Gruntwork Way for.

docs/2.0/way/intro/welcome.md

@@ -0,0 +1,34 @@
+---
+title: Who This Is For
+sidebar_position: 2
+---
+
+We wrote The Gruntwork Way for anyone trying to balance velocity, governance, and maintainability in their quest to better deliver software.
+
+## Roles
+
+In practice, we expect users in these roles will find this useful:
+
+- **Platform engineers** building or improving their developer platforms
+- **DevOps engineers** looking for best practices and patterns
+- **Engineering leaders** evaluating their developer platform and/or cloud strategy
+
+## Maturity levels
+
+As you build your developer platform, you will go through a series of maturity stages. 
+
+Actually, to be more precise, you will build maturity separately in your [patterns](/2.0/way/platform/patterns/overview), [platform components](/2.0/way/platform/components/overview), and [interfaces](/2.0/way/platform/interfaces/overview). Your collective maturity level for the "developer platform" is really just the collection of maturity levels for its component parts.
+
+In general, the component parts track these maturity levels:
+
+- **Ad hoc** - There is no standard, so your team does things manually with minimal automation.
+- **Building** - You've built something, but it's limited.
+- **Established** - This component does add value, but with lots of room for improvement.
+- **Mature** - This component performs its functions comprehensively and effectively.
+- **Self-improving** - This component has a systematic feedback loop that leads to ongoing improvements.
+
+The Gruntwork Way is especially useful for organizations with many building blocks in the **ad hoc,** **building,** or **established** stages.
+
+## Next
+
+Let's close out the introduction by giving you some pointers on how to use this framework!

docs/2.0/way/intro/who-this-is-for.md

@@ -0,0 +1,6 @@
+{
+  "label": "Building Your Platform",
+  "position": 4,
+  "className": "way-top-level-item"
+}
+

docs/2.0/way/platform/_category_.json

@@ -0,0 +1,4 @@
+{
+  "label": "Components",
+  "position": 3
+}