website(README): add content-check command (#2889)

website/README.md

@@ -77,6 +77,16 @@ The significant keys in the YAML frontmatter are:
 
 > ⚠️ If there is a need for a `/api/*` url on this website, the url will be changed to `/api-docs/*`, as the `api` folder is reserved by next.js.
 
+### Validating Content
+
+Content changes are automatically validated against a set of rules as part of the pull request process. If you want to run these checks locally to validate your content before comitting your changes, you can run the following command:
+
+```
+npm run content-check
+```
+
+If the validation fails, actionable error messages will be displayed to help you address detected issues.
+
 ### Creating New Pages
 
 There is currently a small bug with new page creation - if you create a new page and link it up via subnav data while the server is running, it will report an error saying the page was not found. This can be resolved by restarting the server.

website/package.json

@@ -8,7 +8,8 @@
     "npm": ">=7.0.0"
   },
   "devDependencies": {
-    "@hashicorp/platform-cli": "^2.5.1",
+    "@hashicorp/platform-cli": "^2.6.0",
+    "@hashicorp/platform-content-conformance": "^0.0.7",
     "husky": "4.3.8",
     "next": "^12.3.1",
     "prettier": "2.2.1"
@@ -23,6 +24,7 @@
     "format": "next-hashicorp format",
     "generate:readme": "next-hashicorp markdown-blocks README.md",
     "lint": "next-hashicorp lint",
-    "start": "./scripts/website-start.sh"
+    "start": "./scripts/website-start.sh",
+    "content-check": "hc-content --config base-docs"
   }
 }