#109 Moving user-facing documentation to MkDocs site

Author: gunnarmorling

.claude/settings.local.json

@@ -102,7 +102,8 @@
       "Bash(gh pr:*)",
       "Bash(gh api:*)",
       "Bash(/workspace/.docker-venv/bin/asciinema cat:*)",
-      "Bash(/workspace/.docker-venv/bin/asciinema rec:*)"
+      "Bash(/workspace/.docker-venv/bin/asciinema rec:*)",
+      "WebFetch(domain:morling.dev)"
     ]
   }
 }

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,6 @@
+## Checklist
+
+- [ ] Build via `./mvnw clean verify` passes
+- [ ] The commit message is prefixed with the issue key ("#123 Adding support for...")
+- [ ] Code changes are covered by tests
+- [ ] If this PR adds or changes user-facing behaviour, `docs/` has been updated

.github/workflows/docs-trigger.yml

@@ -0,0 +1,25 @@
+name: Trigger documentation publish
+
+on:
+  push:
+    tags: ['v*']
+
+jobs:
+  dispatch:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Fire repository_dispatch to site repo
+        env:
+          GH_TOKEN: ${{ secrets.DOCS_DISPATCH_TOKEN }}
+          VERSION: ${{ github.ref_name }}
+        run: |
+          gh api repos/hardwood-hq/hardwood-hq.github.io/dispatches \
+            --field event_type=publish-docs \
+            --field client_payload="$(cat <<EOF
+          {
+            "source_ref": "${{ github.sha }}",
+            "version": "${VERSION#v}"
+          }
+          EOF
+          )"

CLAUDE.md

@@ -29,6 +29,7 @@ Avoid object access and boxing as much as possible. Always prefer primitive acce
 Before writing new code, search for existing patterns in the same class/package that accomplish the same thing (e.g., the DRY principle). Extract repeated logic into helper methods within the same class rather than duplicating it. When a pattern appears multiple times, consider consolidating it into a single well-named method with overloads if needed.
 Be conservative with base class refactoring. Do not pull implementation details up into abstract base classes unless the logic is truly identical across all subclasses with no foreseeable divergence. Shared helpers are better than shared template methods when subclasses may need different control flow.
 Never use `var` syntax.
+GitHub Actions should always referenced by SHA.
 
 # Documentation