PowderworksCode · zmaril · Aug 22, 2026 · Aug 22, 2026 · Aug 22, 2026 · Aug 22, 2026
diff --git a/site/.gitignore b/site/.gitignore
@@ -1,27 +1,4 @@
-# deps
-/node_modules
-
-# generated content
-.source
-
-# test & build
-/coverage
-/.next/
-/out/
-/build
-*.tsbuildinfo
-
-# misc
-.DS_Store
-*.pem
-/.pnp
-.pnp.js
-npm-debug.log*
-yarn-debug.log*
-yarn-error.log*
-
-# others
-.env*.local
-.vercel
-next-env.d.ts
+node_modules/
+out/
 .wrangler/
+.DS_Store
diff --git a/site/README.md b/site/README.md
diff --git a/site/biome.base.json b/site/biome.base.json
diff --git a/site/biome.json b/site/biome.json
diff --git a/site/bun.lock b/site/bun.lock
diff --git a/site/content/about.md b/site/content/about.md
@@ -0,0 +1,28 @@
+---
+title: About
+description: What Straitjacket is, who builds it, and why it exists.
+order: 9
+---
+
+Straitjacket is a fast, deterministic scanner that flags the weird code and
+text LLMs produce: emoji glyphs in source files, hardcoded colors that should
+be theme tokens, sprawling thousand-line files, logic indented past the depth a
+reader can hold, and deferred-work markers like TODO left behind in comments.
+It is one static Rust binary with no runtime dependencies, so it drops into any
+repository's CI regardless of language or stack.
+
+Every rule runs on the text of a file — the same binary works across every
+language and stack, no toolchain required. The trade is that findings are
+pattern-level: Straitjacket tells you what is in the source, not what it means.
+The reasoning behind the rule set is written down in
+[the project philosophy](/project/philosophy/).
+
+Straitjacket is built by
+[Powderworks](https://powderworks.dev), an independent workshop of open-source
+developer tools maintained by Zack Maril. The code is MIT-licensed and lives on
+[GitHub](https://github.com/PowderworksCode/straitjacket), where releases,
+checksums, and the full commit history are public.
+
+If you want to shape what it catches — a new smell, a false positive you should
+not have to live with — the [contributing guide](/project/contributing/) is
+the way in.
diff --git a/site/content/docs/about/index.mdx b/site/content/docs/about/index.mdx
diff --git a/site/content/docs/about/meta.json b/site/content/docs/about/meta.json
diff --git a/site/content/docs/guides/index.mdx b/site/content/docs/guides/index.mdx
diff --git a/site/content/docs/guides/meta.json b/site/content/docs/guides/meta.json
diff --git a/site/content/docs/index.mdx b/site/content/docs/index.mdx
diff --git a/site/content/docs/meta.json b/site/content/docs/meta.json
diff --git a/site/content/docs/reference/index.mdx b/site/content/docs/reference/index.mdx
diff --git a/site/content/docs/reference/meta.json b/site/content/docs/reference/meta.json