fix: rollback vite to 6.1.0 and pin nanoid for trust policy

docs(mentorship): add programme sunset callout to all pages (#32 )
## Summary The open Mentorship Programme is being closed. This PR adds a `:::caution[Programme Sunset]` aside to the top of every page under `src/content/docs/mentorship/` (and the nested `resources/` subdirectory) so anyone landing on these pages immediately understands the current state of the programme. The callout: - States that the open programme has been sunset and is no longer accepting new participants - Notes that the pages remain available as reference material - Describes the new private, invite-only personalised development programme - Clarifies that there is no application process - Directs interested readers to the Discord community as the route to being noticed for an invite ## Files changed - 11 main mentorship pages (`00-faq` through `10-graduation`) - 10 resource pages under `mentorship/resources/` - 21 files total, 168 insertions, 0 deletions ## Test plan - [x] `pnpm lint` passes (0 cspell issues across 176 files) - [x] `pnpm build` succeeds (177 pages built, no Starlight aside errors) - [x] Spot-checked rendered placement on `00-faq.md` and `resources/career-prep.md` - [ ] Visual confirmation in deployed preview ## Notes While working on this, I noticed one pre-existing em-dash in `mentorship/07-writing-code.md` (line 184, in the body content, not the callout). Out of scope for this PR but worth a future cleanup pass to bring those legacy docs in line with your tone guide. Reviewed-on: #32 Co-authored-by: Hikari <hikari@nhcarrigan.com> Co-committed-by: Hikari <hikari@nhcarrigan.com>
2026-06-30 20:15:26 +02:00 · 2026-05-26 11:20:55 -07:00 · 2026-03-03 17:54:53 -08:00 · 2026-03-02 16:26:38 -08:00 · 2026-03-02 15:44:17 -08:00 · 2026-03-02 13:18:01 -08:00
62 changed files with 90124 additions and 5371 deletions
@@ -12,8 +12,8 @@
    "bash"
  ],
  "ignoreRegExpList": [
-    "```[\\s\\S]*?```", // Ignores multi-line code blocks in Markdown
-    "`[^`\n]+`" // Ignores inline code blocks
+    "```[\\s\\S]*?```",
+    "`[^`\n]+`"
  ],
  "ignoreWords": [
    "nhcarrigan",
@@ -101,6 +101,7 @@
    "Nederlands",
    "Neurodivergence",
    "Nomena",
+    "NSFW",
    "Nymira",
    "OFAC",
    "Ollama",
@@ -8,22 +8,31 @@ on:
      - main

 jobs:
-  lint:
-    name: Lint and Test
+  ci:
+    name: CI
+    runs-on: ubuntu-latest

    steps:
      - name: Checkout Source Files
        uses: actions/checkout@v4

-      - name: Use Node.js v22
+      - name: Use Node.js v24
        uses: actions/setup-node@v4
        with:
-          node-version: 22
+          node-version: 24

      - name: Setup pnpm
        uses: pnpm/action-setup@v2
        with:
-          version: 9
+          version: 10
+
+      - name: Ensure Dependencies are Pinned
+        uses: naomi-lgbt/dependency-pin-check@main
+        with:
+          language: javascript
+          dev-dependencies: true
+          peer-dependencies: true
+          optional-dependencies: true

      - name: Install Dependencies
        run: pnpm install
@@ -35,4 +44,4 @@ jobs:
        run: pnpm run build

      - name: Run Tests
-        run: pnpm run test
+        run: pnpm run test
@@ -1,4 +1,4 @@
-name: Security Scan
+name: Security Scan and Upload

 on:
  push:
@@ -6,136 +6,172 @@ on:
  pull_request:
    branches: [ main ]
  schedule:
-    # Run weekly on Mondays at 00:00 UTC
    - cron: '0 0 * * 1'
  workflow_dispatch:
-  continue_on_error: true

 jobs:
-  security:
-    name: Security Audit
+  security-audit:
+    name: Security & DefectDojo Upload
    runs-on: ubuntu-latest
+    continue-on-error: true

    steps:
      - name: Checkout code
        uses: actions/checkout@v4

+      # --- AUTO-SETUP PROJECT ---
+      - name: Ensure DefectDojo Product Exists
+        env:
+          DD_URL: ${{ secrets.DD_URL }}
+          DD_TOKEN: ${{ secrets.DD_TOKEN }}
+          PRODUCT_NAME: ${{ github.repository }} 
+          PRODUCT_TYPE_ID: 1 
+        run: |
+          sudo apt-get install jq -y > /dev/null
+          
+          echo "Checking connection to $DD_URL..."
+          
+          # Check if product exists - capture HTTP code to debug connection issues
+          RESPONSE=$(curl --write-out "%{http_code}" --silent --output /tmp/response.json \
+            -H "Authorization: Token $DD_TOKEN" \
+            "$DD_URL/api/v2/products/?name=$PRODUCT_NAME")
+          
+          # If response is not 200, print error
+          if [ "$RESPONSE" != "200" ]; then
+            echo "::error::Failed to query DefectDojo. HTTP Code: $RESPONSE"
+            cat /tmp/response.json
+            exit 1
+          fi
+
+          COUNT=$(cat /tmp/response.json | jq -r '.count')
+          
+          if [ "$COUNT" = "0" ]; then
+            echo "Creating product '$PRODUCT_NAME'..."
+            curl -s -X POST "$DD_URL/api/v2/products/" \
+              -H "Authorization: Token $DD_TOKEN" \
+              -H "Content-Type: application/json" \
+              -d '{ "name": "'"$PRODUCT_NAME"'", "description": "Auto-created by Gitea Actions", "prod_type": '$PRODUCT_TYPE_ID' }'
+          else
+            echo "Product '$PRODUCT_NAME' already exists."
+          fi
+
+      # --- 1. TRIVY (Dependencies & Misconfig) ---
      - name: Install Trivy
        run: |
-          sudo apt-get update
          sudo apt-get install wget apt-transport-https gnupg lsb-release -y
-          wget -qO /tmp/trivy-key.asc https://aquasecurity.github.io/trivy-repo/deb/public.key
-          sudo apt-key add /tmp/trivy-key.asc
+          wget -qO - https://aquasecurity.github.io/trivy-repo/deb/public.key | sudo apt-key add -
          echo "deb https://aquasecurity.github.io/trivy-repo/deb $(lsb_release -sc) main" | sudo tee -a /etc/apt/sources.list.d/trivy.list
-          sudo apt-get update
-          sudo apt-get install trivy -y
+          sudo apt-get update && sudo apt-get install trivy -y

-      - name: Run Trivy comprehensive security scan
-        uses: aquasecurity/trivy-action@master
-        with:
-          scan-type: 'fs'
-          scan-ref: '.'
-          scanners: 'vuln,misconfig'
-          format: 'table'
-          output: 'trivy-results.txt'
-          severity: 'CRITICAL,HIGH,MEDIUM,LOW,UNKNOWN'
-          # Fail on any vulnerability found
-          exit-code: '1'
-          # Don't ignore unfixed vulnerabilities
-          ignore-unfixed: false
-          # Skip database update to speed up scans (uses cached DB)
-          skip-db-update: false
-          # Skip setup since we installed Trivy manually
-          skip-setup-trivy: true
-
-      - name: Display Trivy scan results
-        if: always()
+      - name: Run Trivy (FS Scan)
        run: |
-          if [ -f trivy-results.txt ]; then
-            echo "=== Trivy Security Scan Results ==="
-            cat trivy-results.txt
-          else
-            echo "No Trivy scan results found"
+          trivy fs . --scanners vuln,misconfig --format json --output trivy-results.json --exit-code 0
+
+      - name: Upload Trivy to DefectDojo
+        env:
+          DD_URL: ${{ secrets.DD_URL }}
+          DD_TOKEN: ${{ secrets.DD_TOKEN }}
+        run: |
+          echo "Uploading Trivy results..."
+          # Generate today's date in YYYY-MM-DD format
+          TODAY=$(date +%Y-%m-%d)
+          
+          HTTP_CODE=$(curl --write-out "%{http_code}" --output response.txt --silent -X POST "$DD_URL/api/v2/import-scan/" \
+            -H "Authorization: Token $DD_TOKEN" \
+            -F "active=true" \
+            -F "verified=true" \
+            -F "scan_type=Trivy Scan" \
+            -F "engagement_name=CI/CD Pipeline" \
+            -F "product_name=${{ github.repository }}" \
+            -F "scan_date=$TODAY" \
+            -F "auto_create_context=true" \
+            -F "file=@trivy-results.json")
+          
+          if [[ "$HTTP_CODE" != "200" && "$HTTP_CODE" != "201" ]]; then
+            echo "::error::Upload Failed with HTTP $HTTP_CODE"
+            echo "--- SERVER RESPONSE ---"
+            cat response.txt
+            echo "-----------------------"
            exit 1
+          else
+            echo "Upload Success!"
          fi

+      # --- 2. GITLEAKS (Secrets) ---
      - name: Install Gitleaks
        run: |
-          wget -O /tmp/gitleaks.tar.gz https://github.com/gitleaks/gitleaks/releases/download/v8.30.0/gitleaks_8.30.0_linux_x64.tar.gz
-          tar -xzf /tmp/gitleaks.tar.gz -C /tmp
-          sudo mv /tmp/gitleaks /usr/local/bin/
-          sudo chmod +x /usr/local/bin/gitleaks
-          gitleaks version
+          wget -qO gitleaks.tar.gz https://github.com/gitleaks/gitleaks/releases/download/v8.18.0/gitleaks_8.18.0_linux_x64.tar.gz
+          tar -xzf gitleaks.tar.gz
+          sudo mv gitleaks /usr/local/bin/ && chmod +x /usr/local/bin/gitleaks

-      # We remove the Trivy cache to avoid false positives
-      - name: Run Gitleaks secret scan
-        run: |
-          rm -rf .cache/trivy
-          gitleaks detect --source . --report-path gitleaks-results.json --report-format json --no-git
+      - name: Run Gitleaks
+        run: gitleaks detect --source . -v --report-path gitleaks-results.json --report-format json --no-git || true

-      - name: Display Gitleaks scan results
-        if: always()
+      - name: Upload Gitleaks to DefectDojo
+        env:
+          DD_URL: ${{ secrets.DD_URL }}
+          DD_TOKEN: ${{ secrets.DD_TOKEN }}
        run: |
-          if [ -f gitleaks-results.json ]; then
-            echo "=== Gitleaks Secret Scan Results ==="
-            cat gitleaks-results.json
+          echo "Uploading Gitleaks results..."  
+          TODAY=$(date +%Y-%m-%d)
+
+          HTTP_CODE=$(curl --write-out "%{http_code}" --output response.txt --silent -X POST "$DD_URL/api/v2/import-scan/" \
+            -H "Authorization: Token $DD_TOKEN" \
+            -F "active=true" \
+            -F "verified=true" \
+            -F "scan_type=Gitleaks Scan" \
+            -F "engagement_name=CI/CD Pipeline" \
+            -F "product_name=${{ github.repository }}" \
+            -F "scan_date=$TODAY" \
+            -F "auto_create_context=true" \
+            -F "file=@gitleaks-results.json")
+
+          if [[ "$HTTP_CODE" != "200" && "$HTTP_CODE" != "201" ]]; then
+             echo "::error::Upload Failed with HTTP $HTTP_CODE"
+             echo "--- SERVER RESPONSE ---"
+             cat response.txt
+             echo "-----------------------"
+             exit 1
          else
-            echo "No secrets detected by Gitleaks"
-            exit 1
+             echo "Upload Success!"
          fi

-      - name: Install Semgrep
+      # --- 3. SEMGREP (SAST) ---
+      - name: Install Semgrep (via pipx)
        run: |
-          sudo apt-get install pipx
-          pipx ensurepath
-          export PATH="$HOME/.local/bin:$PATH"
+          sudo apt-get install pipx -y
          pipx install semgrep
-          semgrep --version
+          # Add pipx binary path to GITHUB_PATH so next steps can see 'semgrep'
+          echo "$HOME/.local/bin" >> $GITHUB_PATH

-      - name: Run Semgrep static analysis
-        run: |
-          export PATH="$HOME/.local/bin:$PATH"
-          semgrep --config p/security-audit \
-            --config p/owasp-top-ten \
-            --config p/ci \
-            --config p/r2c-security-audit \
-            --config p/cwe-top-25 \
-            --output semgrep-results.txt \
-            .
+      - name: Run Semgrep
+        run: semgrep scan --config=p/security-audit --config=p/owasp-top-ten --json --output semgrep-results.json . || true

-      - name: Display Semgrep scan results
-        if: always()
+      - name: Upload Semgrep to DefectDojo
+        env:
+          DD_URL: ${{ secrets.DD_URL }}
+          DD_TOKEN: ${{ secrets.DD_TOKEN }}
        run: |
-          if [ -f semgrep-results.txt ]; then
-            echo "=== Semgrep Static Analysis Results ==="
-            cat semgrep-results.txt
+          echo "Uploading Semgrep results..."
+          TODAY=$(date +%Y-%m-%d)
+          
+          HTTP_CODE=$(curl --write-out "%{http_code}" --output response.txt --silent -X POST "$DD_URL/api/v2/import-scan/" \
+            -H "Authorization: Token $DD_TOKEN" \
+            -F "active=true" \
+            -F "verified=true" \
+            -F "scan_type=Semgrep JSON Report" \
+            -F "engagement_name=CI/CD Pipeline" \
+            -F "product_name=${{ github.repository }}" \
+            -F "scan_date=$TODAY" \
+            -F "auto_create_context=true" \
+            -F "file=@semgrep-results.json")
+
+          if [[ "$HTTP_CODE" != "200" && "$HTTP_CODE" != "201" ]]; then
+             echo "::error::Upload Failed with HTTP $HTTP_CODE"
+             echo "--- SERVER RESPONSE ---"
+             cat response.txt
+             echo "-----------------------"
+             exit 1
          else
-            echo "No Semgrep scan results found"
-            exit 1
-          fi
-
-      - name: Install Go
-        uses: actions/setup-go@v6
-        with:
-          go-version: 'stable' # Latest stable version
-
-      - name: Install OSV Scanner
-        run: |
-          export PATH="$HOME/go/bin:$PATH"
-          go install github.com/google/osv-scanner/v2/cmd/osv-scanner@latest
-
-      - name: Run OSV Scanner
-        run: |
-          export PATH="$HOME/go/bin:$PATH"
-          osv-scanner scan source --format table --output osv-results.txt -r .
-
-      - name: Display OSV Scanner scan results
-        if: always()
-        run: |
-          if [ -f osv-results.txt ]; then
-            echo "=== OSV Scanner Results ==="
-            cat osv-results.txt
-          else
-            echo "No OSV Scanner scan results found"
-            exit 1
+             echo "Upload Success!"
          fi
@@ -1,47 +1,29 @@
-# Astro Starter Kit: Minimal
+# docs

-```sh
-npm create astro@latest -- --template minimal
-```
+Documentation for NHCarrigan projects.

-[![Open in StackBlitz](https://developer.stackblitz.com/img/open_in_stackblitz.svg)](https://stackblitz.com/github/withastro/astro/tree/latest/examples/minimal)
-[![Open with CodeSandbox](https://assets.codesandbox.io/github/button-edit-lime.svg)](https://codesandbox.io/p/sandbox/github/withastro/astro/tree/latest/examples/minimal)
-[![Open in GitHub Codespaces](https://github.com/codespaces/badge.svg)](https://codespaces.new/withastro/astro?devcontainer_path=.devcontainer/minimal/devcontainer.json)
+## Live Version

-> 🧑‍🚀 **Seasoned astronaut?** Delete this file. Have fun!
+This page is currently deployed. [View the live website.](https://docs.nhcarrigan.com)

-## 🚀 Project Structure
+## Feedback and Bugs

-Inside of your Astro project, you'll see the following folders and files:
+If you have feedback or a bug report, please [log a ticket on our forum](https://support.nhcarrigan.com).

-```text
-/
-├── public/
-├── src/
-│   └── pages/
-│       └── index.astro
-└── package.json
-```
+## Contributing

-Astro looks for `.astro` or `.md` files in the `src/pages/` directory. Each page is exposed as a route based on its file name.
+If you would like to contribute to the project, you may create a Pull Request containing your proposed changes and we will review it as soon as we are able! Please review our [contributing guidelines](CONTRIBUTING.md) first.

-There's nothing special about `src/components/`, but that's where we like to put any Astro/React/Vue/Svelte/Preact components.
+## Code of Conduct

-Any static assets, like images, can be placed in the `public/` directory.
+Before interacting with our community, please read our [Code of Conduct](CODE_OF_CONDUCT.md).

-## 🧞 Commands
+## License

-All commands are run from the root of the project, from a terminal:
+This software is licensed under our [global software license](https://docs.nhcarrigan.com/#/license).

-| Command                   | Action                                           |
-| :------------------------ | :----------------------------------------------- |
-| `npm install`             | Installs dependencies                            |
-| `npm run dev`             | Starts local dev server at `localhost:4321`      |
-| `npm run build`           | Build your production site to `./dist/`          |
-| `npm run preview`         | Preview your build locally, before deploying     |
-| `npm run astro ...`       | Run CLI commands like `astro add`, `astro check` |
-| `npm run astro -- --help` | Get help using the Astro CLI                     |
+Copyright held by Naomi Carrigan.

-## 👀 Want to learn more?
+## Contact

-Feel free to check [our documentation](https://docs.astro.build) or jump into our [Discord server](https://astro.build/chat).
+We may be contacted through our [Chat Server](http://chat.nhcarrigan.com) or via email at `contact@nhcarrigan.com`
@@ -0,0 +1,24 @@
+# Security
+
+# Do not execute any scripts of installed packages (project scripts still run)
+ignoreDepScripts: true
+# Do not automatically run pre/post scripts (e.g. preinstall, postbuild)
+enablePrePostScripts: false
+# Only allow packages published at least 10 days ago (reduces risk of compromised packages)
+minimumReleaseAge: 14400
+# Fail if a package's trust level has decreased compared to previous releases
+trustPolicy: no-downgrade
+# Ignore trust policy for packages published more than 1 year ago (predates provenance signing)
+trustPolicyIgnoreAfter: 525960
+# Fail if there are missing or invalid peer dependencies
+strictPeerDependencies: true
+# Prevent transitive dependencies from using exotic sources (git repos, direct tarball URLs)
+blockExoticSubdeps: true
+overrides:
+  vite: 6.1.0
+  nanoid: 3.3.11
+
+# Lockfile
+
+# Allow the lockfile to be updated during install (set to true in CI for stricter reproducibility)
+preferFrozenLockfile: false
@@ -1,5 +1,6 @@
 export const navigation = [
  {
+    // #region About Us
    label: "About Us",
    collapsed: true,
    items: [
@@ -49,6 +50,8 @@ export const navigation = [
      },
    ].sort((a, b) => a.label.localeCompare(b.label)),
  },
+  // #endregion
+  // #region Legal Information
  {
    label: "Legal Information",
    collapsed: true,
@@ -115,6 +118,8 @@ export const navigation = [
      },
    ].sort((a, b) => a.label.localeCompare(b.label)),
  },
+  // #endregion
+  // #region Community Policies
  {
    label: "Community Policies",
    collapsed: true,
@@ -143,8 +148,14 @@ export const navigation = [
        label: "Community Feedback and Participation Policy",
        link: "/community/feedback",
      },
+      {
+        label: "Fan Art Guidelines",
+        link: "/community/fan-art",
+      }
    ].sort((a, b) => a.label.localeCompare(b.label)),
  },
+  // #endregion
+  // #region Development Documentation
  {
    label: "Development Documentation",
    collapsed: true,
@@ -169,20 +180,14 @@ export const navigation = [
        label: "Development Environment",
        link: "/dev/environment",
      },
-      {
-        label: "Server Setup",
-        link: "/dev/servers",
-      },
-      {
-        label: "Naomi's VTubing Setup",
-        link: "/dev/vtubing",
-      },
      {
        label: "Security Hall of Fame",
        link: "/dev/hall-of-fame",
      }
    ].sort((a, b) => a.label.localeCompare(b.label)),
  },
+  // #endregion
+  // #region Mentorship Programme
  {
    label: "Mentorship Programme",
    collapsed: true,
@@ -279,6 +284,8 @@ export const navigation = [
      }
    ].sort((a, b) => a.label.localeCompare(b.label)),
  },
+  // #endregion
+  // #region Project Documentation
  {
    label: "Project Documentation",
    collapsed: true,
@@ -715,6 +722,8 @@ export const navigation = [
      },
    ].sort((a, b) => a.label.localeCompare(b.label)),
  },
+  // #endregion
+  // #region Staff Guidelines
  {
    label: "Staff Guidelines",
    collapsed: true,
@@ -807,6 +816,10 @@ export const navigation = [
            label: "Documentation and Transparency Training for Staff",
            link: "/staff/training/documentation-transparency",
          },
+          {
+            label: "Support Forum Moderation Training for Staff",
+            link: "/staff/training/forum-moderation",
+          },
          {
            label: "Harassment and Bullying Response Training for Staff",
            link: "/staff/training/harassment-bullying-response",
@@ -835,29 +848,21 @@ export const navigation = [
      },
    ].sort((a, b) => a.label.localeCompare(b.label)),
  },
+  // #endregion
+  // #region External Links
  {
-    label: "Miscellaneous Documents",
-    collapsed: true,
-    items: [
-      {
-        label: "Managing Local Music",
-        link: "/misc/music",
-      },
-      {
-        label: "Templates",
-        link: "/misc/templates",
-      },
-      {
-        label: "AI Prompts",
-        link: "/misc/prompts",
-      }
-    ].sort((a, b) => a.label.localeCompare(b.label)),
-  },
-  {
-    label: "Sitemap",
-    link: "https://sitemap.nhcarrigan.com",
+    label: "Discord",
+    link: "https://chat.nhcarrigan.com",
    attrs: {
      target: "_blank",
    },
  },
+  {
+    label: "Support Forum",
+    link: "https://support.nhcarrigan.com",
+    attrs: {
+      target: "_blank",
+    },
+  }
+  // #endregion
 ];
@@ -135,9 +135,9 @@ Our code repositories are all self-hosted. Git accounts are only granted to Team
  - Issue tracking
  - Source code for all of our products
 - Best for: Viewing source code and documentation
- **Bug Reports and Feature Requests**: To report bugs or request features, please use our Discord forum channels:
-  - `#bug-reports` forum channel for bug reports
-  - `#feature-requests` forum channel for feature requests
+- **Bug Reports and Feature Requests**: To report bugs or request features, please use our support forum:
+  - [Bug Reports](https://support.nhcarrigan.com/c/bug-reports/6) for bug reports
+  - [Feature Requests](https://support.nhcarrigan.com/c/feature-requests/7) for feature requests

 ### 2.3. Etiquette and Best Practices

@@ -236,11 +236,11 @@ We offer several email addresses for specific types of inquiries. Please use the

 ### 5.2. Billing and Financial Matters

-:::tip[Preferred Method]{icon=message}
-We encourage you to use the **#billing-questions** Discord forum channel for billing inquiries. This allows for public discussion and faster responses. If you need to share sensitive financial information, you can ask staff to make your thread private, or contact us via email for complete confidentiality.
+:::tip[Preferred Method]{icon=star}
+We encourage you to use the [**Billing Questions**](https://support.nhcarrigan.com/c/billing-questions/13) category on our support forum for billing inquiries. This allows for public discussion and faster responses. If you need to share sensitive financial information, you can ask staff to make your thread private, or contact us via email for complete confidentiality.
 :::

- **Discord Forum:** `#billing-questions` (preferred for most inquiries)
+- **Support Forum:** [Billing Questions](https://support.nhcarrigan.com/c/billing-questions/13) (preferred for most inquiries)
 - Email: billing@nhcarrigan.com (for highly sensitive financial information requiring complete confidentiality)
 - Use for:
  - Questions about payments or invoices
@@ -250,11 +250,11 @@ We encourage you to use the **#billing-questions** Discord forum channel for bil

 ### 5.3. Technical Support

-:::tip[Preferred Method]{icon=message}
-We encourage you to use the **#technical-support** Discord forum channel for support inquiries. This allows for public discussion and faster responses. If you need to share sensitive information, you can ask staff to make your thread private, or contact us via email for complete confidentiality.
+:::tip[Preferred Method]{icon=star}
+We encourage you to use the [**Technical Support**](https://support.nhcarrigan.com/c/technical-support/5) category on our support forum for support inquiries. This allows for public discussion and faster responses. If you need to share sensitive information, you can ask staff to make your thread private, or contact us via email for complete confidentiality.
 :::

- **Discord Forum:** `#technical-support` (preferred for most inquiries)
+- **Support Forum:** [Technical Support](https://support.nhcarrigan.com/c/technical-support/5) (preferred for most inquiries)
 - Email: support@nhcarrigan.com
 - Use for:
  - Assistance with using our software or services
@@ -263,7 +263,14 @@ We encourage you to use the **#technical-support** Discord forum channel for sup

 ### 5.4. Privacy Concerns

- Email: privacy@nhcarrigan.com
+:::tip[Preferred Method]{icon=star}
+We encourage you to use our **Privacy Request Form** for privacy-related requests: https://forms.nhcarrigan.com/o/docs/forms/qEJgBWGDfyHv6x51VU9aVX/4
+
+This form helps ensure we collect all necessary information to process your request efficiently and in compliance with applicable data protection laws.
+:::
+
+- **Privacy Request Form** (Preferred): https://forms.nhcarrigan.com/o/docs/forms/qEJgBWGDfyHv6x51VU9aVX/4
+- Email: privacy@nhcarrigan.com (for general privacy questions or if you prefer email)
 - Use for:
  - Questions about our privacy policy
  - Requests for data access or deletion
@@ -272,7 +279,15 @@ We encourage you to use the **#technical-support** Discord forum channel for sup

 ### 5.5. Security Matters

- Email: security@nhcarrigan.com
+:::tip[Preferred Method]{icon=star}
+We encourage you to use our **Security Vulnerability Report Form** for reporting security vulnerabilities: https://forms.nhcarrigan.com/o/docs/forms/wgdbBkS4tjCGoVZTqtmMNx/4
+
+This form helps ensure we collect all necessary information to investigate and address security issues efficiently and securely.
+:::
+
+- **Security Vulnerability Report Form** (Preferred): https://forms.nhcarrigan.com/o/docs/forms/wgdbBkS4tjCGoVZTqtmMNx/4
+- **Public Security Reports:** View aggregated and sanitized security vulnerability reports for all our products at: https://security.nhcarrigan.com/report/
+- Email: security@nhcarrigan.com (for general security questions or if you prefer email)
 - Use for:
  - Reporting security vulnerabilities
  - Questions about our security practices
@@ -280,11 +295,11 @@ We encourage you to use the **#technical-support** Discord forum channel for sup

 ### 5.6. Legal Inquiries

-:::tip[Preferred Method]{icon=message}
-We encourage you to use the **#legal-notices** Discord forum channel for legal inquiries. This allows for public discussion and transparency. If you need to share sensitive legal information, you can ask staff to make your thread private, or contact us via email for urgent matters requiring immediate confidentiality.
+:::tip[Preferred Method]{icon=star}
+We encourage you to use the [**Legal Notices**](https://support.nhcarrigan.com/c/legal-notices/12) category on our support forum for legal inquiries. This allows for public discussion and transparency. If you need to share sensitive legal information, you can ask staff to make your thread private, or contact us via email for urgent matters requiring immediate confidentiality.
 :::

- **Discord Forum:** `#legal-notices` (preferred for most inquiries)
+- **Support Forum:** [Legal Notices](https://support.nhcarrigan.com/c/legal-notices/12) (preferred for most inquiries)
 - Email: legal@nhcarrigan.com (for urgent legal matters requiring immediate confidentiality)
 - Use for:
  - Legal questions or concerns
@@ -294,7 +309,18 @@ We encourage you to use the **#legal-notices** Discord forum channel for legal i

 ### 5.7. Feedback and Suggestions

- Email: feedback@nhcarrigan.com
+:::tip[Preferred Method]{icon=star}
+We encourage you to use our support forum for different types of feedback:
+- [**Community Feedback**](https://support.nhcarrigan.com/c/community-feedback/8) for general feedback about our community, services, events, and initiatives
+- [**Policy Ideation**](https://support.nhcarrigan.com/c/policy-ideation/9) for suggestions about community policies and governance
+- [**Accessibility Feedback**](https://support.nhcarrigan.com/c/accessibility-feedback/10) for reporting accessibility barriers and improvement suggestions
+:::
+
+- **Support Forum:**
+  - [Community Feedback](https://support.nhcarrigan.com/c/community-feedback/8) (preferred for general feedback)
+  - [Policy Ideation](https://support.nhcarrigan.com/c/policy-ideation/9) (preferred for policy suggestions)
+  - [Accessibility Feedback](https://support.nhcarrigan.com/c/accessibility-feedback/10) (preferred for accessibility matters)
+- Email: feedback@nhcarrigan.com (if you prefer email communication)
 - Use for:
  - Providing feedback on our work or projects
  - Suggesting improvements or new features
@@ -303,11 +329,11 @@ We encourage you to use the **#legal-notices** Discord forum channel for legal i

 ### 5.8. Press/Media Inquiries

-:::tip[Preferred Method]{icon=message}
-We encourage you to use the **#press-inquiries** Discord forum channel for media inquiries. This allows for public discussion and community visibility. If you need to share sensitive information, you can ask staff to make your thread private, or contact us via email for highly sensitive media matters requiring complete confidentiality.
+:::tip[Preferred Method]{icon=star}
+We encourage you to use the [**Press Inquiries**](https://support.nhcarrigan.com/c/press-inquiries/14) category on our support forum for media inquiries. This allows for public discussion and community visibility. If you need to share sensitive information, you can ask staff to make your thread private, or contact us via email for highly sensitive media matters requiring complete confidentiality.
 :::

- **Discord Forum:** `#press-inquiries` (preferred for most inquiries)
+- **Support Forum:** [Press Inquiries](https://support.nhcarrigan.com/c/press-inquiries/14) (preferred for most inquiries)
 - Email: press@nhcarrigan.com (for highly sensitive media matters requiring complete confidentiality)
 - Use for:
  - Requesting comment regarding news
@@ -325,11 +351,11 @@ We encourage you to use the **#press-inquiries** Discord forum channel for media

 ### 5.10. Marketing Inquiries

-:::tip[Preferred Method]{icon=message}
-We encourage you to use the **#marketing-proposals** Discord forum channel for marketing inquiries. This allows for public discussion and community input. If you need to share highly confidential business information, you can ask staff to make your thread private, or contact us via email for proposals requiring complete privacy.
+:::tip[Preferred Method]{icon=star}
+We encourage you to use the [**Marketing Proposals**](https://support.nhcarrigan.com/c/marketing-proposals/15) category on our support forum for marketing inquiries. This allows for public discussion and community input. If you need to share highly confidential business information, you can ask staff to make your thread private, or contact us via email for proposals requiring complete privacy.
 :::

- **Discord Forum:** `#marketing-proposals` (preferred for most inquiries)
+- **Support Forum:** [Marketing Proposals](https://support.nhcarrigan.com/c/marketing-proposals/15) (preferred for most inquiries)
 - Email: marketing@nhcarrigan.com (for highly confidential business proposals requiring complete privacy)
 - Use for:
  - Marketing collaboration proposals
@@ -348,11 +374,11 @@ We encourage you to use the **#marketing-proposals** Discord forum channel for m

 ### 5.12. Partnerships

-:::tip[Preferred Method]{icon=message}
-We encourage you to use the **#partnership-requests** Discord forum channel for partnership inquiries. This allows for public discussion and community input on potential partnerships. If you need to share sensitive business information, you can ask staff to make your thread private, or contact us via email if you need complete confidentiality from the start.
+:::tip[Preferred Method]{icon=star}
+We encourage you to use the [**Partnership Requests**](https://support.nhcarrigan.com/c/partnership-requests/11) category on our support forum for partnership inquiries. This allows for public discussion and community input on potential partnerships. If you need to share sensitive business information, you can ask staff to make your thread private, or contact us via email if you need complete confidentiality from the start.
 :::

- **Discord Forum:** `#partnership-requests` (preferred for most inquiries)
+- **Support Forum:** [Partnership Requests](https://support.nhcarrigan.com/c/partnership-requests/11) (preferred for most inquiries)
 - Email: partners@nhcarrigan.com (if you need complete confidentiality from the start)
 - Use for:
  - Requesting a collaboration between our organisation and yours
@@ -217,10 +217,10 @@ Community Members are required to:

 #### 5.1.1. Available Reporting Methods
 Community Members can report Code of Conduct violations through the following channels:
+- **Incident Report Form** (Preferred): Submit reports through our official Incident Report Form: https://forms.nhcarrigan.com/o/docs/forms/t7CYeYS4uyUuLiKFatoEvs/4
 - **Discord Reporting**: Type `@Moderator` in any channel to alert Community Leaders
 - **Direct Communication**: Contact any Community Leader through private messages
 - **Email Contact**: Submit reports to contact@nhcarrigan.com
- **Anonymous Reporting**: Use designated anonymous reporting forms where available

 #### 5.1.2. Information to Include in Reports
 Effective reports should include:
@@ -0,0 +1,186 @@
+---
+title: Fan Art Guidelines
+---
+
+## 1. Introduction and Purpose
+
+### 1.1. Welcome to Our Fan Art Community!
+
+Are you interested in creating art for our lovely Naomi? We absolutely love seeing creative interpretations of our characters and would be thrilled to feature your work! These guidelines will help you understand what we're looking for and how to submit your creations.
+
+### 1.2. Scope
+
+These guidelines apply to:
+- Fan art of Naomi and her various designs
+- Fan art of Original Characters (OCs) shared in our #characters channel (Naomi's OCs)
+- Any artistic interpretations of our characters and community
+
+## 2. Content Guidelines
+
+### 2.1. Content Standards
+
+#### 2.1.1. Family-Friendly Public Submissions
+
+For art that will be shared in our public spaces (such as our fan art channel), we maintain family-friendly standards:
+
+**(a)** **No Obscene or NSFW Content**: Public submissions must be appropriate for all audiences. We want to show your work off to everyone!
+
+**(b)** **Original Works Only**: Please no AI-generated content. We want to see your original works! If Naomi wanted AI-generated art, she would generate it herself.
+
+**(c)** **Creative Freedom**: You are free to give Naomi whatever outfit you would like. Refer to our reference channel for reference images to get an idea of her style.
+
+#### 2.1.2. NSFW Content Policy
+
+We understand that some artists may wish to create mature content featuring our characters. We have the following policy for such works:
+
+**(a)** **DM Submission Required**: NSFW works must be sent to us via direct message (DM) only. Do not post NSFW content in any public channels.
+
+**(b)** **Private Appreciation**: While we appreciate all artistic interpretations, NSFW works will not be shared in our public spaces as we are a family-friendly community.
+
+**(c)** **Respectful Content**: Even for private submissions, we reserve the right to decline content that we find inappropriate or that violates our community standards.
+
+**(d)** **Recognition**: Accepted NSFW submissions will still qualify for the role!
+
+### 2.2. Original Characters (OCs)
+
+We have a dedicated **#characters** channel where Naomi shares her Original Characters! You are welcome and encouraged to create fan art of these OCs as well. When creating art of Naomi's OCs:
+
+**(a)** **Respect Character Design**: Please respect the original character designs and creator intentions.
+
+**(b)** **Follow Same Guidelines**: All content guidelines (family-friendly for public, NSFW via DM only) apply to OC fan art as well.
+
+## 3. Reference Materials and Resources
+
+### 3.1. Available Reference Materials
+
+#### 3.1.1. Reference Images
+
+We maintain reference images in our Discord reference channel. These images can help you understand Naomi's style, color palette, and design elements.
+
+### 3.2. Important Disclaimer About Reference Materials
+
+:::warning[AI-Generated Reference Materials Disclaimer]
+**Please be aware that our current reference sheets and other visual assets are AI-generated. This is a temporary situation.**
+
+We operate at a significant loss and do not currently have the budget to commission proper, human-created art for all of our reference materials. However, we are committed to replacing these AI-generated assets with proper commissioned art as funds become available.
+
+**How You Can Help:**
+
+- **Financial Support**: If you would like to help us replace our AI-generated assets with proper art, you can donate at [donate.nhcarrigan.com](https://donate.nhcarrigan.com). All donations help us work toward commissioning proper reference art.
+
+- **Art Donations**: We would be absolutely thrilled to accept donated art to replace our AI-generated assets! If you're interested in creating reference art or other assets for us, please reach out via DM to discuss.
+
+We appreciate your understanding and patience as we work to improve our resources. Our goal is to have all human-created, properly commissioned art, and we're working toward that goal every day.
+:::
+
+## 4. Submission Process
+
+### 4.1. How to Submit Your Art
+
+#### 4.1.1. Public Submissions (Family-Friendly Content)
+
+To submit family-friendly fan art for public sharing:
+
+1. **Create Your Art**: Follow the guidelines above to ensure your work meets our standards.
+
+2. **DM Your Submission**: Send your artwork to Naomi directly via DM.
+
+3. **Review Process**: If accepted, your art will be shared in our fan art channel (with full credit - you will be tagged in the post).
+
+4. **Recognition**: Accepted submissions will receive a special role recognizing your contribution!
+
+#### 4.1.2. Private Submissions (NSFW Content)
+
+For NSFW works:
+
+1. **DM Only**: Send your NSFW artwork directly to Naomi via DM.
+
+2. **Private Appreciation**: These works will be appreciated privately and will not be shared in public spaces.
+
+3. **No Public Sharing**: Please do not post NSFW content in any public channels, even if you think it might be acceptable.
+
+4. **Recognition**: Accepted submissions will still qualify for the role!
+
+### 4.2. What Happens After Submission
+
+#### 4.2.1. Review Timeline
+
+We review submissions as quickly as possible, but please be patient. We want to give each piece the attention it deserves!
+
+#### 4.2.2. Acceptance and Sharing
+
+If your public submission is accepted:
+- Your art will be posted in our fan art channel
+- You will be tagged and credited in the post
+- You will receive a special role recognizing your contribution
+- We may share your work on other platforms (with credit)
+
+#### 4.2.3. If Your Submission Isn't Accepted
+
+If we decline a submission, we'll do our best to explain why. Common reasons include:
+- Content doesn't meet our family-friendly standards (for public submissions)
+- Quality concerns (though we appreciate all skill levels!)
+- Copyright or intellectual property issues
+- Other community guideline violations
+
+We're always happy to provide feedback and work with artists to create content that fits our community!
+
+## 5. Rights and Permissions
+
+### 5.1. Artist Rights and Rights Transfer
+
+**(a)** **Rights Transfer**: By submitting your art to us, you transfer the rights to your creation to us. This transfer occurs upon submission and acceptance of your work.
+
+**(b)** **Credit Always Given**: We will always credit you when sharing your work, even though rights have been transferred.
+
+**(c)** **Usage Rights**: Once rights are transferred, we have the right to use, display, share, and distribute your submitted artwork in our community spaces and on other platforms with proper credit.
+
+### 5.2. Character Rights
+
+**(a)** **Character Ownership**: Naomi and other official characters remain the property of NHCarrigan.
+
+**(b)** **Fan Art Rights**: Creating fan art is generally considered fair use, but please be respectful of the characters and community.
+
+**(c)** **Commercial Use**: If you're interested in commercial use of our characters, please contact us to discuss licensing.
+
+## 6. Community Support and Appreciation
+
+### 6.1. We Love Your Art!
+
+We genuinely appreciate every piece of art created for our community. Whether it's a quick sketch or a detailed masterpiece, your creativity and effort mean the world to us!
+
+### 6.2. Growing Together
+
+We're always working to improve our resources and support for artists. As we grow and develop better reference materials (see our disclaimer above), we hope to make it even easier for artists to create amazing fan art!
+
+### 6.3. Questions or Concerns?
+
+If you have any questions about these guidelines, the submission process, or anything else related to fan art, please don't hesitate to reach out via DM or ask in our community channels!
+
+---
+
+## Summary: Quick Reference
+
+**✅ DO:**
+- Create original, family-friendly art for public sharing
+- DM your submissions to Naomi
+- Feel free to be creative with outfits and styles
+- Create art of Naomi's OCs from our #characters channel
+- Send NSFW works via DM only (they won't be shared publicly)
+
+**❌ DON'T:**
+- Submit AI-generated content
+- Post NSFW content in public channels
+- Disrespect character designs when making OC fan art
+- Submit content that violates our community standards
+
+**📝 Remember:**
+- Reference materials are currently AI-generated (temporary!)
+- You can help us get proper art by donating or creating art donations
+- By submitting art, you transfer rights to your creation to us
+- We always credit artists when sharing their work
+- Questions? Just ask!
+
+---
+
+*Thank you for your interest in creating art for our community! We can't wait to see what you create!*
@@ -44,10 +44,10 @@ This Policy operates within our comprehensive legal and policy framework, incorp
 #### 2.1.1. Daily and Ongoing Feedback Channels

 **Open Communication Channels:**
- Dedicated feedback forum channels accessible to all community members for ongoing input and suggestions
-  - Community: `#community-feedback` forum channel on Discord
-  - Products: `#bug-reports` or `#feature-requests` forum channel on Discord
-  - Policies: `#policy-ideation` forum channel on Discord
+- Dedicated feedback forum categories accessible to all community members for ongoing input and suggestions
+  - Community: [Community Feedback](https://support.nhcarrigan.com/c/community-feedback/8) category on our support forum
+  - Products: [Bug Reports](https://support.nhcarrigan.com/c/bug-reports/6) or [Feature Requests](https://support.nhcarrigan.com/c/feature-requests/7) categories on our support forum
+  - Policies: [Policy Ideation](https://support.nhcarrigan.com/c/policy-ideation/9) category on our support forum
 - Direct messaging opportunities with community leadership for individual concerns and suggestions
 - Public discussion forums for community-wide conversation about policies and improvements

@@ -1,428 +0,0 @@
---
-title: Server Setup
---
-
-**ESTABLISHING SERVER CONFIGURATION STANDARDS AND SECURITY REQUIREMENTS**
-
-## 1. INTRODUCTION AND LEGAL FRAMEWORK
-
-### 1.1. Policy Overview
-
-This Server Setup Documentation (hereinafter referred to as "the Documentation") establishes mandatory standards, procedures, and security requirements for configuring remote servers used to host projects maintained by our organisation. This Documentation operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Security Policy, and all applicable legal protections by reference.
-
-### 1.2. Scope and Applicability
-
-This Documentation applies to all remote servers used to host projects, services, or infrastructure maintained by our organisation. All personnel responsible for server configuration, deployment, or maintenance must comply with the standards set forth in this Documentation.
-
-**IMPORTANT: Non-compliance with server security and configuration standards set forth in this Documentation may result in security vulnerabilities, service disruptions, or other serious consequences. All server administrators must strictly adhere to these requirements.**
-
-### 1.3. Security and Compliance Requirements
-
-Server configuration must comply with:
- Our Security Policy and security standards
- Applicable data protection and privacy regulations
- Industry best practices for server security
- All relevant legal and regulatory requirements
-
-## 2. PROVISIONING A SERVER
-
-We use DigitalOcean as our provider. Regardless of your choice, provision a new VPS using the **latest Ubuntu LTS version**. Add your `ssh` key AND Naomi's `ssh` key in the setup process.
-
-## 3. SETTING UP USER ACCOUNTS
-
-You should never run applications on root. SSH into the new VPS to prepare your user.
-
-### 3.1. Creating the User Account
-
-You'll need to set a password for the `root` account first.
-
-```bash
-passwd
-```
-
-Once you have set a password, ensure that you have provided it to Naomi to store in the vault.
-
-Create an `NHCarrigan` user for our organisation.
-
-```bash
-adduser NHCarrigan
-```
-
-Set a **different** password, and provide that to Naomi as well. For all of the user information, use the default blank values.
-
-Add the new user to the sudoers file.
-
-```bash
-usermod -aG sudo NHCarrigan
-```
-
-Then sync the SSH keys so we can authenticate as that user.
-
-```bash
-rsync --archive --chown=NHCarrigan:NHCarrigan ~/.ssh /home/NHCarrigan
-```
-
-While you are there, set the timezone for the server to our business' local timezone.
-
-```bash
-sudo timedatectl set-timezone America/Los_Angeles
-```
-
-## 4. PREPARING FOR WEB REQUESTS
-
-To prepare the server to receive web requests, you'll need to follow a few steps.
-
-### 4.1. SSL Certificate Configuration
-
-:::note
-If the Firewall has been set up, you'll need to temporarily allow port 80 for the certificate to generate.
-:::
-
-We use LetsEncrypt to provision our SSL certificates. If it is not installed, install it with:
-
-```bash
-sudo snap install --classic certbot
-```
-
-Then link the snap to our `usr` directory.
-
-```bash
-sudo ln -s /snap/bin/certbot /usr/bin/certbot
-```
-
-Generate a certificate with:
-
-```bash
-sudo certbot certonly --standalone
-```
-
-And allow applications to read it:
-
-```bash
-sudo chmod -R a+rwx /etc/letsencrypt
-```
-
-When you need to renew the certificate:
-
-```bash
-sudo certbot renew
-```
-
-### 4.2. NGINX Configuration
-
-All requests should be routed through NGINX. At no point should an application run directly on ports 80 or 443.
-
-Install NGINX:
-
-```bash
-sudo apt-get install nginx
-```
-
-Edit the configuration file:
-
-```bash
-sudo emacs /etc/nginx/conf.d/server.conf
-```
-
-Use this template to set up a reverse proxy on the standard HTTPS port 443:
-
-```nginx
-server {
-    listen 443 ssl;
-    server_name subdomain.domain.tld;
-    ssl_certificate /etc/letsencrypt/live/subdomain.domain.tld/fullchain.pem;
-    ssl_certificate_key /etc/letsencrypt/live/subdomain.domain.tld/privkey.pem;
-
-    location / {
-        proxy_set_header Host $host;
-        proxy_pass https://127.0.0.1:port;
-        proxy_redirect off;
-    }
-}
-```
-
-Validate that the config is correct with:
-
-```bash
-sudo nginx -t
-```
-
-If so, restart NGINX to apply the changes:
-
-```bash
-sudo systemctl restart nginx
-```
-
-## 5. SECURING THE SERVER
-
-We have a minimum level of security that is required on ALL of our servers. This section should not be treated as the best effort, but as the minimal requirements to comply with our policies.
-
-### 5.1. Firewall Configuration
-
-We use `ufw` as our firewall. First, enable the SSH port.
-
-```bash
-sudo ufw allow "OpenSSH"
-```
-
-Then, allow the standard HTTPS port and **deny** the standard HTTP port.
-
-```bash
-sudo ufw deny http
-sudo ufw allow https
-```
-
-Enable the firewall. You may get dropped from the SSH connection.
-
-```bash
-sudo ufw enable
-```
-
-### 5.2. Fail2Ban Configuration
-
-We also use Fail2Ban to block IP addresses which fail to make requests too often.
-
-Install the tool:
-
-```bash
-sudo apt-get install fail2ban
-```
-
-Configure the NGINX jail in `/etc/fail2ban/jail.d/nginx-auth.conf`:
-
-```ini
-[nginx-auth]
-enabled = true
-filter = nginx-auth
-logpath = /var/log/nginx/access.log
-maxretry = 3
-findtime = 86400
-bantime = 86400
-```
-
-Configure the NGINX filter in `/etc/fail2ban/filter.d/nginx-auth.conf`:
-
-```ini
-[Definition]
-failregex = ^<HOST> - .* \[.*\] ".*" (4\d{2}) .*$
-```
-
-Because we use Cloudflare, you'll need to grab the original IP for all requests. Start by creating a file to store Cloudflare's IPs.
-
-```bash
-sudo touch /etc/nginx/cloudflare_ips.conf
-```
-
-Then create your script:
-
-```bash
-nano ~/update_cf_ips.sh
-```
-
-```bash
-#!/bin/bash
-
-# Create a temporary file
-temp_file=$(mktemp)
-
-# Download IPv4 ranges and format each line
-curl -s https://www.cloudflare.com/ips-v4 | while read ip; do
-    echo "set_real_ip_from $ip;" >> "$temp_file"
-done
-
-# Download IPv6 ranges and format each line
-curl -s https://www.cloudflare.com/ips-v6 | while read ip; do
-    echo "set_real_ip_from $ip;" >> "$temp_file"
-done
-
-# Add the real_ip_header directive
-echo "real_ip_header CF-Connecting-IP;" >> "$temp_file"
-
-# Replace the old file with the new one
-sudo mv "$temp_file" /etc/nginx/cloudflare_ips.conf
-
-# Test Nginx configuration
-sudo nginx -t
-
-# If the test is successful, reload Nginx
-if [ $? -eq 0 ]; then
-    sudo systemctl reload nginx
-    echo "Nginx configuration updated and reloaded successfully."
-else
-    echo "Nginx configuration test failed. Please check your configuration."
-fi
-```
-
-Make it executable and run it:
-
-```bash
-sudo chmod +x update_cf_ips.sh
-sudo ./update_cf_ips.sh
-```
-
-If it runs as expected, set it up to run on a CRON.
-
-```bash
-sudo crontab -e
-```
-
-```bash
-0 3 * * 1 ~/update_cf_ips.sh
-```
-
-Then, update the `/etc/nginx/nginx.conf` to use all of this new logic. This goes at the end of your `http` directive block.
-
-```nginx
-# Look at the real IP, not the cloudflare IP.
-include /etc/nginx/cloudflare_ips.conf;
-
-log_format custom_format '$remote_addr - $remote_user [$time_local] '
-                        '"$request" $status $body_bytes_sent '
-                        '"$http_referer" "$http_user_agent" '
-                        '"$http_x_forwarded_for"';
-
-access_log /var/log/nginx/access.log custom_format;
-```
-
-Confirm the NGINX configuration is correct:
-
-```bash
-sudo nginx -t
-```
-
-Then restart everything.
-
-```bash
-sudo systemctl restart nginx
-sudo systemctl restart fail2ban
-```
-
-To view banned IPs:
-
-```bash
-sudo fail2ban-client status nginx-auth
-```
-
-And to unban them:
-
-```bash
-sudo fail2ban-client set nginx-auth unbanip <ip>
-```
-
-## 6. UPLOADING PROJECTS
-
-To upload a project, you should **not** use `git` to clone the project to the machine. Instead, start by cloning the project to your local environment and navigating to the directory:
-
-```bash
-git clone <url>
-cd /path/to/project
-```
-
-Then sync the project up to the machine, ignoring any installed packages.
-
-```bash
-rsync -av --exclude='node_modules' ./ <server name>:/home/NHCarrigan/<project directory>
-```
-
-## 7. RUNNING PROJECTS
-
-Now you are ready to start running the project.
-
-### 7.1. Node.js Setup
-
-Most of our projects will run on Node. For a new machine, you'll need to set that up.
-
-We use `nvm` to manage Node versions. Fetch and run the install script:
-
-```bash
-curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.37.2/install.sh | bash
-```
-
-The script will automatically update the `.bashrc` file to load `nvm` into the PATH. Reload that:
-
-```bash
-source ~/.bashrc
-```
-
-Install the long-term support Node version.
-
-```bash
-nvm install --lts
-```
-
-This should automatically set it as the default. When updating, be sure to remove any older versions!
-
-Finally, install `pnpm` as the package manager.
-
-```bash
-npm i -g pnpm
-```
-
-### 7.2. PM2 Process Management
-
-All of our processes run with PM2 to allow for monitoring and auto-restarts. You'll need to install it.
-
-```bash
-pnpm i -g pm2
-```
-
-To start a project, use this template:
-
-```bash
-pm2 start '<script>' --name '<name>'
-```
-
-Then run `pm2 save` to save the application list.
-
-## 8. LIMITATION OF LIABILITY AND DISCLAIMERS
-
-### 8.1. Reference to Comprehensive Liability Framework
-
-**IMPORTANT: Comprehensive liability limitations, damage exclusions, and maximum liability caps are set forth in our Limitation of Liability and Indemnification Policy, which is incorporated herein by reference.**
-
-### 8.2. Server Configuration Disclaimer
-
-This Documentation establishes mandatory security and configuration standards. However, compliance with these standards does not guarantee:
-
- Complete protection against all security threats or vulnerabilities
- Uninterrupted service availability or performance
- Compatibility with all applications or use cases
- Protection against all forms of attack or compromise
-
-### 8.3. Security Disclaimer
-
-While this Documentation establishes security requirements, server administrators are responsible for:
-
- Implementing additional security measures appropriate to their specific threat environment
- Regularly updating and patching all software and dependencies
- Monitoring server logs and security alerts
- Responding promptly to security incidents
- Maintaining compliance with all applicable security regulations and standards
-
-### 8.4. Third-Party Services and Tools
-
-This Documentation references various third-party services, tools, and software packages. Our organisation:
-
- Does not guarantee the security, availability, or functionality of third-party services
- Is not responsible for issues arising from the use of third-party tools or services
- Recommends that administrators review third-party licenses, terms of service, and security practices
- Does not provide support for third-party tools beyond what is necessary for project functionality
-
-### 8.5. Technical Accuracy Disclaimer
-
-While we strive to maintain accurate and current information in this Documentation, technical standards, software versions, and security best practices evolve continuously. Server administrators are responsible for:
-
- Verifying current software versions and compatibility
- Adapting configurations to their specific system requirements
- Ensuring compliance with current security standards and regulations
- Consulting additional resources for the most current security recommendations
-
-## 9. CONCLUSION
-
-This Server Setup Documentation establishes mandatory standards and procedures for configuring remote servers used to host projects maintained by our organisation. Strict adherence to these requirements is essential for maintaining security, reliability, and compliance with our organisational policies and legal obligations.
-
-All personnel responsible for server configuration, deployment, or maintenance must familiarise themselves with and comply with the requirements set forth in this Documentation. Questions about server configuration requirements or security standards should be directed to appropriate technical leadership through designated communication channels.
-
---
-
-*For questions about server configuration requirements or to suggest improvements, please contact technical leadership through the designated channels outlined in our Security Policy.*
@@ -12,10 +12,12 @@ This Style Guide (hereinafter referred to as "the Guide") establishes mandatory

 ### 1.2. Scope and Applicability

-This Guide applies to all code contributions, regardless of contributor status, project type, or development context. All contributors are required to comply with the standards set forth in this Guide.
+This Guide applies to all code contributions to NHCarrigan-maintained repositories, regardless of contributor status. All contributors to our projects are required to comply with the standards set forth in this Guide.

 **IMPORTANT: Non-compliance with this Guide may result in rejection of contributions, requests for modification, or other appropriate actions as determined by project maintainers.**

+**Note for Mentorship Programme Participants:** This Guide governs contributions to NHCarrigan-maintained repositories only. It does not apply to your flagship project. Your flagship project is your own intellectual property, and you are entirely free to set your own style standards, choose your own licence, and use your own copyright attribution.
+
 ### 1.3. Legal Compliance and Intellectual Property

 All code contributions must comply with:
@@ -1,54 +0,0 @@
---
-title: Naomi's VTubing Setup
---
-
-Naomi uses her VTuber model for all of her client meetings, as well as streaming. Getting the software to work on Linux is a bit of a nightmare, so this page documents how she does so.
-
-## 1. OpenSeeFace
-
-In order to track her webcamera, OpenSeeFace needs to be run independently as a native script.
-
-### 1.1. Installation
-
-This should all be done in your home `~` directory.
-
- Begin by cloning the repository:
-  - `git clone https://github.com/emilianavt/OpenSeeFace`
-  - `cd OpenSeeFace`
- You will need to prepare Python
-  - Install the packages: `yay -Sy python python-virtualenv`
-  - Prepare the environment: `virtualenv -p python3 env`
-  - Source the environment: `source env/bin/activate`
-  - Install the dependencies: `pip3 install onnxruntime opencv-python pillow numpy`
-
-### 1.2. Running
-
-```
-cd OpenSeeFace
-source env/bin/activate
-python facetracker.py -c 0 -W 1280 -H 720 --discard-after 0 --scan-every 0 --no-3d-adapt 1 --max-feature-updates 900
-```
-
-## 2. VSeeFace
-
-VSeeFace does not run natively, and will need to run with Wine.
-
-### 2.1. Installation
-
-[Download and run the installer](https://www.vseeface.icu/#download). When selecting a directory, put it in `~/VSeeFace`.
-
-### 2.2. Running
-
-```bash
-wine ~/VSeeFace/VSeeFace.exe --background-color "#00FF00"
-```
-
-The `--background-color` flag creates a green screen background to be chroma-keyed out by OBS.
-
-## 3. OBS
-
-OBS allows for virtual camera, as well as for streaming.
-
-### 3.1. Installation
-
-The `obs-studio-git` AUR package is Naomi's current installation.
@@ -670,6 +670,8 @@ For questions about this AUP:

 To report policy violations:

+**Incident Report Form** (Preferred): Submit reports through our official Incident Report Form: https://forms.nhcarrigan.com/o/docs/forms/t7CYeYS4uyUuLiKFatoEvs/4
+
 **Email:** abuse@nhcarrigan.com

 **Subject Line:** Policy Violation Report - [Service/Platform]
@@ -62,7 +62,7 @@ This policy applies to all forms of support exchange within our community platfo
 - Assistance with community projects and initiatives
 - Collaborative problem-solving on shared challenges
 - Skill sharing and mentorship opportunities
- Accessibility assistance and accommodation support
+- Accessibility assistance and accommodation support (request accommodations via our [Accessibility Accommodation Request Form](https://forms.nhcarrigan.com/o/docs/forms/2FXY87PB6aaMHspcnXYCZX/4))
 - Platform-specific guidance and orientation

 #### 2.1.2. Specialised Support Areas
@@ -316,7 +316,7 @@ We are working very hard to get them in place as soon as possible. If you would
 **Designated Support Channels:**
 - **#support**: General questions and peer support requests
 - **#support-ticket**: Technical assistance and troubleshooting
- **#accessibility**: Accessibility-related assistance and resources
+- **#accessibility**: Accessibility-related assistance and resources (for accommodation requests, use our [Accessibility Accommodation Request Form](https://forms.nhcarrigan.com/o/docs/forms/2FXY87PB6aaMHspcnXYCZX/4))
 - **Identity-specific channels**: Support spaces for specific communities and identities

 **Direct Message Guidelines:**
@@ -192,13 +192,15 @@ Regardless of your location, you have the following rights regarding your person

 To exercise any of these rights:

-**(a)** Submit requests to **privacy@nhcarrigan.com** from the email address associated with your account;
+**(a)** Submit requests through our **Privacy Request Form** (Preferred): https://forms.nhcarrigan.com/o/docs/forms/qEJgBWGDfyHv6x51VU9aVX/4

-**(b)** Provide sufficient information to verify your identity;
+**(b)** Alternatively, submit requests to **privacy@nhcarrigan.com** from the email address associated with your account;

-**(c)** Specify clearly which right you wish to exercise;
+**(c)** Provide sufficient information to verify your identity;

-**(d)** Include any relevant details or documentation to support your request.
+**(d)** Specify clearly which right you wish to exercise;
+
+**(e)** Include any relevant details or documentation to support your request.

 ### 5.3. Response Timeframes

@@ -48,6 +48,8 @@ This Policy is designed to operate within the framework of applicable laws and r

 If you discover a security vulnerability within any of our systems or applications, please report it exclusively through our designated secure reporting channel:

+**Security Vulnerability Report Form** (Preferred): https://forms.nhcarrigan.com/o/docs/forms/wgdbBkS4tjCGoVZTqtmMNx/4
+
 **Primary Contact:** security@nhcarrigan.com

 **Subject Line Format:** [SECURITY] Brief description of vulnerability
@@ -172,7 +174,7 @@ Our standard coordinated disclosure timeline follows this process:

 **(c)** **Remediation Period:** Development and deployment of fixes (30-90 days depending on complexity);

-**(d)** **Public Disclosure:** Joint announcement of vulnerability and resolution (after fix deployment and reasonable notice period).
+**(d)** **Public Disclosure:** Joint announcement of vulnerability and resolution (after fix deployment and reasonable notice period). Aggregated and sanitized vulnerability reports are published at: https://security.nhcarrigan.com/report/

 ### 4.3. Public Acknowledgement

@@ -386,21 +388,17 @@ We utilise a comprehensive suite of security tools integrated into our developme

 ### 8.4. Public Security Reporting

-:::tip[Heads Up!]{icon=pen}
-The policy or policies in this section are still a work in progress. We have not yet implemented the necessary infrastructure to comply with this section.
-
-We are working very hard to get them in place as soon as possible. If you would like to help, consider [applying to join our team!](https://forms.nhcarrigan.com/o/docs/forms/mCxDu3snk9TzFiDjrT4Vc8/4)
-:::
-
 We maintain transparency about our security posture through publicly accessible security reports and dashboards:

-**(a)** **Quality Dashboard:** Real-time security and quality metrics available;
+**(a)** **Security Vulnerability Reports:** Aggregated and sanitized security vulnerability reports for all our products are published at: https://security.nhcarrigan.com/report/

-**(b)** **Security Reports:** Comprehensive security scan results published;
+**(b)** **Quality Dashboard:** Real-time security and quality metrics available;

-**(c)** **Regular Updates:** Weekly scanning cycles ensure up-to-date security information;
+**(c)** **Security Reports:** Comprehensive security scan results published;

-**(d)** **Trend Analysis:** Historical data tracking to identify and address security trends over time.
+**(d)** **Regular Updates:** Weekly scanning cycles ensure up-to-date security information;
+
+**(e)** **Trend Analysis:** Historical data tracking to identify and address security trends over time.

 ### 8.5. Security Development Lifecycle

@@ -470,6 +468,8 @@ If vulnerability research reveals potential regulatory compliance issues or lega

 For all security-related matters, including vulnerability reports, questions about this Policy, and general security inquiries:

+**Security Vulnerability Report Form** (Preferred for vulnerability reports): https://forms.nhcarrigan.com/o/docs/forms/wgdbBkS4tjCGoVZTqtmMNx/4
+
 **Email:** security@nhcarrigan.com

 **Response Time:** We aim to respond to all security inquiries within 7-10 business days
@@ -352,7 +352,7 @@ Regarding data processed by subprocessors, users may:

 To exercise rights regarding subprocessor data processing:

-**(a)** **Primary Contact:** Contact us at privacy@nhcarrigan.com for coordination;
+**(a)** **Primary Contact:** Submit requests through our **Privacy Request Form** (Preferred): https://forms.nhcarrigan.com/o/docs/forms/qEJgBWGDfyHv6x51VU9aVX/4 or contact us at privacy@nhcarrigan.com for coordination;

 **(b)** **Direct Contact:** Contact subprocessors directly using their provided channels;

@@ -2,6 +2,14 @@
 title: 00. Frequently Asked Questions
 ---

+:::caution[Programme Sunset]
+The open Mentorship Programme has been sunset and is no longer accepting new participants. These pages remain available as reference material.
+
+I'm now running a private, personalised professional development programme on an invite-only basis - hand-selecting a small number of participants so the shape of each journey can be built around them. There is no application process; participation is by direct invitation only.
+
+Being active in my [Discord community](https://chat.nhcarrigan.com/) increases your chances of being invited.
+:::
+
 **PROVIDING ANSWERS TO FREQUENTLY ASKED QUESTIONS REGARDING THE MENTORSHIP PROGRAMME**

 ## 1. INTRODUCTION AND LEGAL FRAMEWORK
@@ -67,7 +75,7 @@ This FAQ addresses common questions and concerns regarding programme participati

 **Response Time Guidelines:**
 - Most programme activities can be completed independently using provided documentation
- If you have questions, feel free to ask in the #mentee-chat channel
+- If you have questions, feel free to ask in the #⚗️│alchemy-lab channel
 - If you have not received a response within 10 business days, you may send a gentle reminder
 - Repeated communications at intervals of less than 10 business days may result in disciplinary action
 - We appreciate your patience and understanding regarding response timelines
@@ -140,7 +148,7 @@ All expulsion decisions are made in accordance with our Mentorship Programme Ter

 - Review the comprehensive mentorship documentation (01-10) for detailed guidance on each programme stage
 - Check the resource library for templates, examples, and additional materials
- Contact programme leadership through the designated #mentee-chat channel in our Discord community
+- Contact programme leadership through the designated #⚗️│alchemy-lab channel in our Discord community
 - Ask community members and alumni for peer support and guidance
 - Programme leadership is available to answer questions when asked, but most activities can be completed independently
 - Additional information is available in our comprehensive [Mentorship Programme Terms and Conditions](/about/mentorship)
@@ -2,6 +2,14 @@
 title: 01. Onboarding
 ---

+:::caution[Programme Sunset]
+The open Mentorship Programme has been sunset and is no longer accepting new participants. These pages remain available as reference material.
+
+I'm now running a private, personalised professional development programme on an invite-only basis - hand-selecting a small number of participants so the shape of each journey can be built around them. There is no application process; participation is by direct invitation only.
+
+Being active in my [Discord community](https://chat.nhcarrigan.com/) increases your chances of being invited.
+:::
+
 **ESTABLISHING ONBOARDING PROCEDURES AND REQUIREMENTS FOR MENTORSHIP PROGRAMME PARTICIPANTS**

 ## 1. INTRODUCTION AND LEGAL FRAMEWORK
@@ -2,6 +2,14 @@
 title: 02. Goal Setting
 ---

+:::caution[Programme Sunset]
+The open Mentorship Programme has been sunset and is no longer accepting new participants. These pages remain available as reference material.
+
+I'm now running a private, personalised professional development programme on an invite-only basis - hand-selecting a small number of participants so the shape of each journey can be built around them. There is no application process; participation is by direct invitation only.
+
+Being active in my [Discord community](https://chat.nhcarrigan.com/) increases your chances of being invited.
+:::
+
 **ESTABLISHING GOAL-SETTING PROCEDURES AND REQUIREMENTS FOR MENTORSHIP PROGRAMME PARTICIPANTS**

 ## 1. INTRODUCTION AND LEGAL FRAMEWORK
@@ -24,7 +32,7 @@ Goal-setting procedures must be initiated following completion of onboarding pro

 ### 2.2. Goal-Setting Forum Post Creation

-**Required Action:** Create a thread in the #goal-setting forum channel on our Discord community.
+**Required Action:** Create a thread in the #🎯│oaths forum channel on our Discord community.

 **Thread Naming Convention:**
 ```markdown
@@ -63,7 +71,7 @@ Goal-setting procedures must be initiated following completion of onboarding pro
 ### 2.4. Optional Feedback and Clarification

 If you would like feedback on your goal-setting post or have questions about creating your roadmap, you can:
- Ask questions in the #mentee-chat channel in Discord
+- Ask questions in the #⚗️│alchemy-lab channel in Discord
 - Request feedback from programme leadership or community members
 - Review roadmap templates and examples in the resource library
 - Proceed independently if you feel confident in your goals and plan
@@ -2,6 +2,14 @@
 title: 03. Project Planning
 ---

+:::caution[Programme Sunset]
+The open Mentorship Programme has been sunset and is no longer accepting new participants. These pages remain available as reference material.
+
+I'm now running a private, personalised professional development programme on an invite-only basis - hand-selecting a small number of participants so the shape of each journey can be built around them. There is no application process; participation is by direct invitation only.
+
+Being active in my [Discord community](https://chat.nhcarrigan.com/) increases your chances of being invited.
+:::
+
 **ESTABLISHING PROJECT PLANNING PROCEDURES AND REQUIREMENTS FOR MENTORSHIP PROGRAMME PARTICIPANTS**

 ## 1. INTRODUCTION AND LEGAL FRAMEWORK
@@ -24,7 +32,7 @@ Project planning procedures must be initiated following completion of goal-setti

 ### 2.2. Project Planning Forum Post Creation

-**Required Action:** Create a post in the #project-plan forum channel on our Discord community.
+**Required Action:** Create a post in the #🗺️│quest-board forum channel on our Discord community.

 **Post Naming Convention:**
 ```markdown
@@ -51,7 +59,7 @@ Project planning procedures must be initiated following completion of goal-setti
 **Project Idea Assistance:**
 - If you do not yet have a project idea, create your post with a statement such as: "I need help brainstorming a project idea"
 - Review project idea examples in the resource library for inspiration
- Ask for help in the #mentee-chat channel if you'd like community input
+- Ask for help in the #⚗️│alchemy-lab channel if you'd like community input
 - Programme leadership and community members can provide feedback if requested
 - You can also proceed independently by researching project ideas online or adapting examples

@@ -68,7 +76,7 @@ Once your project planning post is created, you will develop your project plan i
 - Create a detailed project plan ready for development work

 **Optional Support:**
- If you need help brainstorming or refining your project idea, ask in the #mentee-chat channel
+- If you need help brainstorming or refining your project idea, ask in the #⚗️│alchemy-lab channel
 - Community members and programme leadership can provide feedback if requested
 - You can proceed independently once you have a project concept you're happy with

@@ -2,6 +2,14 @@
 title: 04. User Stories
 ---

+:::caution[Programme Sunset]
+The open Mentorship Programme has been sunset and is no longer accepting new participants. These pages remain available as reference material.
+
+I'm now running a private, personalised professional development programme on an invite-only basis - hand-selecting a small number of participants so the shape of each journey can be built around them. There is no application process; participation is by direct invitation only.
+
+Being active in my [Discord community](https://chat.nhcarrigan.com/) increases your chances of being invited.
+:::
+
 **ESTABLISHING USER STORY DEVELOPMENT PROCEDURES AND REQUIREMENTS FOR MENTORSHIP PROGRAMME PARTICIPANTS**

 ## 1. INTRODUCTION AND LEGAL FRAMEWORK
@@ -93,7 +101,7 @@ Separate issues provide:

 **Optional Review:**
 - If you would like feedback on your user stories, you can:
-  - Request review in the #mentee-chat channel in Discord
+  - Request review in the #⚗️│alchemy-lab channel in Discord
  - Ask community members or alumni for peer review
  - Review user story examples in the resource library for comparison
 - Reviews are optional and available upon request, not required
@@ -2,6 +2,14 @@
 title: 05. Technical Breakdown
 ---

+:::caution[Programme Sunset]
+The open Mentorship Programme has been sunset and is no longer accepting new participants. These pages remain available as reference material.
+
+I'm now running a private, personalised professional development programme on an invite-only basis - hand-selecting a small number of participants so the shape of each journey can be built around them. There is no application process; participation is by direct invitation only.
+
+Being active in my [Discord community](https://chat.nhcarrigan.com/) increases your chances of being invited.
+:::
+
 **ESTABLISHING TECHNICAL BREAKDOWN PROCEDURES AND REQUIREMENTS FOR MENTORSHIP PROGRAMME PARTICIPANTS**

 ## 1. INTRODUCTION AND LEGAL FRAMEWORK
@@ -183,7 +191,7 @@ Complete the technical breakdown template for each user story. Completion includ

 **Optional Review:**
 - If you would like feedback on your technical breakdowns, you can:
-  - Request review in the #mentee-chat channel in Discord
+  - Request review in the #⚗️│alchemy-lab channel in Discord
  - Ask community members or alumni for peer review
  - Review technical breakdown examples in the resource library for comparison

@@ -2,6 +2,14 @@
 title: 06. Priority and Effort
 ---

+:::caution[Programme Sunset]
+The open Mentorship Programme has been sunset and is no longer accepting new participants. These pages remain available as reference material.
+
+I'm now running a private, personalised professional development programme on an invite-only basis - hand-selecting a small number of participants so the shape of each journey can be built around them. There is no application process; participation is by direct invitation only.
+
+Being active in my [Discord community](https://chat.nhcarrigan.com/) increases your chances of being invited.
+:::
+
 **ESTABLISHING PRIORITY AND EFFORT ASSIGNMENT PROCEDURES FOR MENTORSHIP PROGRAMME PARTICIPANTS**

 ## 1. INTRODUCTION AND LEGAL FRAMEWORK
@@ -133,7 +141,7 @@ The purpose of applying effort labels is to help plan work timelines and resourc

 **Optional Review:**
 - If you would like feedback on your priority and effort assignments, you can:
-  - Request review in the #mentee-chat channel in Discord
+  - Request review in the #⚗️│alchemy-lab channel in Discord
  - Ask community members or alumni for peer review
  - Review priority and effort examples in the resource library for comparison
 - Reviews are optional and available upon request, not required
@@ -2,6 +2,14 @@
 title: 07. Writing Code
 ---

+:::caution[Programme Sunset]
+The open Mentorship Programme has been sunset and is no longer accepting new participants. These pages remain available as reference material.
+
+I'm now running a private, personalised professional development programme on an invite-only basis - hand-selecting a small number of participants so the shape of each journey can be built around them. There is no application process; participation is by direct invitation only.
+
+Being active in my [Discord community](https://chat.nhcarrigan.com/) increases your chances of being invited.
+:::
+
 **ESTABLISHING CODE DEVELOPMENT PROCEDURES AND REQUIREMENTS FOR MENTORSHIP PROGRAMME PARTICIPANTS**

 ## 1. INTRODUCTION AND LEGAL FRAMEWORK
@@ -14,7 +22,7 @@ This Writing Code Documentation (hereinafter referred to as "the Documentation")

 This Documentation applies to all participants in our Mentorship Programme following completion of priority and effort assignment procedures. All participants should comply with the code development procedures set forth in this Documentation.

-**IMPORTANT: Code development should comply with our Style Guide, Contributor Covenant, and all applicable development standards. Code reviews are optional and available upon request, not mandatory.**
+**IMPORTANT: Whilst developing your flagship project, you must comply with our [Community Code of Conduct](/community/coc) and [Community Guidelines](/community/guide). Your mentorship repository must not be used for any code or non-code content or behaviour that is illegal, harmful to others, discriminatory, or bigoted. See Section 7.3 for details on intellectual property and style standards. Code reviews are optional and available upon request, not mandatory.**

 ## 2. DEVELOPMENT WORKFLOW REQUIREMENTS

@@ -63,7 +71,7 @@ Before writing code, participants must consider and address the requirements set
 - Community members and alumni may also provide peer reviews if requested

 **Requesting Reviews:**
- If you would like a code review, request one in the #mentee-chat channel or tag programme leadership on your PR
+- If you would like a code review, request one in the #⚗️│alchemy-lab channel or tag programme leadership on your PR
 - Reviews are provided when available, not guaranteed immediately
 - You can proceed with development while waiting for reviews

@@ -169,9 +177,11 @@ This Documentation establishes code development procedures and requirements. How
 - Programme leadership is not responsible for participants' ability to complete development work
 - Individual results may vary based on participant skill, effort, and other factors

-### 7.3. Intellectual Property Considerations
+### 7.3. Intellectual Property Ownership

-All code developed as part of the Mentorship Programme is subject to our Mentorship Programme Terms and Conditions regarding intellectual property rights. Participants should familiarise themselves with these terms before beginning development work.
+**Your flagship project belongs to you.** NHCarrigan makes no claim to intellectual property rights over projects developed during the Mentorship Programme. You own your project outright and are free to licence it however you choose.
+
+**Regarding style standards:** Our Style Guide applies only to contributions to NHCarrigan-maintained repositories — it does not apply to your flagship project. You are entirely free to choose your own coding style, linting tools, licence, and copyright attribution for your own project.

 ## 8. CONCLUSION

@@ -2,6 +2,14 @@
 title: 08. Final Polish
 ---

+:::caution[Programme Sunset]
+The open Mentorship Programme has been sunset and is no longer accepting new participants. These pages remain available as reference material.
+
+I'm now running a private, personalised professional development programme on an invite-only basis - hand-selecting a small number of participants so the shape of each journey can be built around them. There is no application process; participation is by direct invitation only.
+
+Being active in my [Discord community](https://chat.nhcarrigan.com/) increases your chances of being invited.
+:::
+
 **ESTABLISHING FINAL POLISH AND DEPLOYMENT PROCEDURES FOR MENTORSHIP PROGRAMME PARTICIPANTS**

 ## 1. INTRODUCTION AND LEGAL FRAMEWORK
@@ -28,7 +36,7 @@ When you believe your flagship project has reached a state where it can be proud
 - Begin addressing items on the checklist independently

 **Optional Support:**
- If you would like feedback on project readiness, ask in the #mentee-chat channel
+- If you would like feedback on project readiness, ask in the #⚗️│alchemy-lab channel
 - Programme leadership or community members can provide guidance if requested
 - You can proceed independently using the provided resources

@@ -81,7 +89,7 @@ Use the provided documentation templates and examples in the resource library to
 - End user documentation examples

 **Optional Support:**
- If you need help with documentation, ask in the #mentee-chat channel
+- If you need help with documentation, ask in the #⚗️│alchemy-lab channel
 - Programme leadership or community members can provide guidance if requested
 - You can proceed independently using the provided templates

@@ -163,7 +171,7 @@ You should deploy a live version of your application for professional presentati
 - Free options may not always be viable depending on project requirements

 **Optional Support:**
- If you encounter issues during deployment, ask for help in the #mentee-chat channel
+- If you encounter issues during deployment, ask for help in the #⚗️│alchemy-lab channel
 - Programme leadership or community members can provide guidance if requested
 - Most deployment can be completed independently using the provided guides

@@ -2,6 +2,14 @@
 title: 09. Career Prep
 ---

+:::caution[Programme Sunset]
+The open Mentorship Programme has been sunset and is no longer accepting new participants. These pages remain available as reference material.
+
+I'm now running a private, personalised professional development programme on an invite-only basis - hand-selecting a small number of participants so the shape of each journey can be built around them. There is no application process; participation is by direct invitation only.
+
+Being active in my [Discord community](https://chat.nhcarrigan.com/) increases your chances of being invited.
+:::
+
 **ESTABLISHING CAREER PREPARATION PROCEDURES AND REQUIREMENTS FOR MENTORSHIP PROGRAMME PARTICIPANTS**

 ## 1. INTRODUCTION AND LEGAL FRAMEWORK
@@ -63,7 +71,7 @@ Upon reaching the career preparation stage, you have access to comprehensive res
 - Present your project effectively on your resume

 **Optional Review:**
- If you would like feedback on your resume, request a review in the #mentee-chat channel
+- If you would like feedback on your resume, request a review in the #⚗️│alchemy-lab channel
 - Programme leadership or community members can provide feedback if requested
 - Reviews are optional and available upon request

@@ -92,7 +100,7 @@ LinkedIn profile preparation should focus on:
 - Optimizing profile for recruiter visibility

 **Optional Review:**
- If you would like feedback on your LinkedIn profile, request a review in the #mentee-chat channel
+- If you would like feedback on your LinkedIn profile, request a review in the #⚗️│alchemy-lab channel
 - Programme leadership or community members can provide feedback if requested
 - Reviews are optional and available upon request

@@ -126,7 +134,7 @@ LinkedIn profile preparation should focus on:
 - Review application content using provided checklists

 **Optional Support:**
- If you would like feedback on your applications, request a review in the #mentee-chat channel
+- If you would like feedback on your applications, request a review in the #⚗️│alchemy-lab channel
 - Programme leadership or community members can provide feedback if requested
 - Support is limited to guidance and feedback on application content
 - You are responsible for submitting your own applications
@@ -153,7 +161,7 @@ LinkedIn profile preparation should focus on:

 **Mock Interview Availability:**
 - Mock interviews are available upon request when programme leadership or community members are available
- Request mock interviews in the #mentee-chat channel
+- Request mock interviews in the #⚗️│alchemy-lab channel
 - Mock interviews prepare you for real interview situations
 - Feedback and coaching on interview performance may be provided

@@ -2,6 +2,14 @@
 title: 10. Graduation
 ---

+:::caution[Programme Sunset]
+The open Mentorship Programme has been sunset and is no longer accepting new participants. These pages remain available as reference material.
+
+I'm now running a private, personalised professional development programme on an invite-only basis - hand-selecting a small number of participants so the shape of each journey can be built around them. There is no application process; participation is by direct invitation only.
+
+Being active in my [Discord community](https://chat.nhcarrigan.com/) increases your chances of being invited.
+:::
+
 **ESTABLISHING GRADUATION CRITERIA AND ALUMNI PROGRAMME PROCEDURES FOR MENTORSHIP PROGRAMME PARTICIPANTS**

 ## 1. INTRODUCTION AND LEGAL FRAMEWORK
@@ -2,6 +2,14 @@
 title: Career Preparation Resources
 ---

+:::caution[Programme Sunset]
+The open Mentorship Programme has been sunset and is no longer accepting new participants. These pages remain available as reference material.
+
+I'm now running a private, personalised professional development programme on an invite-only basis - hand-selecting a small number of participants so the shape of each journey can be built around them. There is no application process; participation is by direct invitation only.
+
+Being active in my [Discord community](https://chat.nhcarrigan.com/) increases your chances of being invited.
+:::
+
 **RESUME TEMPLATES, LINKEDIN GUIDES, APPLICATION GUIDES, INTERVIEW RESOURCES, AND JOB SEARCH STRATEGIES**

 ## Resume Templates
@@ -2,6 +2,14 @@
 title: Code Development Resources
 ---

+:::caution[Programme Sunset]
+The open Mentorship Programme has been sunset and is no longer accepting new participants. These pages remain available as reference material.
+
+I'm now running a private, personalised professional development programme on an invite-only basis - hand-selecting a small number of participants so the shape of each journey can be built around them. There is no application process; participation is by direct invitation only.
+
+Being active in my [Discord community](https://chat.nhcarrigan.com/) increases your chances of being invited.
+:::
+
 **CODE REVIEW CHECKLIST, SELF-REVIEW GUIDELINES, AND BEST PRACTICES**

 ## Code Review Checklist
@@ -2,6 +2,14 @@
 title: Code Review Checklist
 ---

+:::caution[Programme Sunset]
+The open Mentorship Programme has been sunset and is no longer accepting new participants. These pages remain available as reference material.
+
+I'm now running a private, personalised professional development programme on an invite-only basis - hand-selecting a small number of participants so the shape of each journey can be built around them. There is no application process; participation is by direct invitation only.
+
+Being active in my [Discord community](https://chat.nhcarrigan.com/) increases your chances of being invited.
+:::
+
 **SELF-REVIEW CHECKLIST FOR CODE QUALITY**

 Use this checklist to review your own code before merging pull requests or when preparing for optional code reviews.
@@ -2,6 +2,14 @@
 title: Final Polish Checklist
 ---

+:::caution[Programme Sunset]
+The open Mentorship Programme has been sunset and is no longer accepting new participants. These pages remain available as reference material.
+
+I'm now running a private, personalised professional development programme on an invite-only basis - hand-selecting a small number of participants so the shape of each journey can be built around them. There is no application process; participation is by direct invitation only.
+
+Being active in my [Discord community](https://chat.nhcarrigan.com/) increases your chances of being invited.
+:::
+
 **COMPREHENSIVE CHECKLIST FOR PROJECT FINAL POLISH**

 Use this checklist to ensure your flagship project is ready for professional presentation.
@@ -2,6 +2,14 @@
 title: Final Polish Resources
 ---

+:::caution[Programme Sunset]
+The open Mentorship Programme has been sunset and is no longer accepting new participants. These pages remain available as reference material.
+
+I'm now running a private, personalised professional development programme on an invite-only basis - hand-selecting a small number of participants so the shape of each journey can be built around them. There is no application process; participation is by direct invitation only.
+
+Being active in my [Discord community](https://chat.nhcarrigan.com/) increases your chances of being invited.
+:::
+
 **FINAL POLISH CHECKLIST, CODE CLEANUP GUIDELINES, DOCUMENTATION TEMPLATES, AND DEPLOYMENT GUIDES**

 ## Final Polish Checklist
@@ -2,6 +2,14 @@
 title: Goal Setting Resources
 ---

+:::caution[Programme Sunset]
+The open Mentorship Programme has been sunset and is no longer accepting new participants. These pages remain available as reference material.
+
+I'm now running a private, personalised professional development programme on an invite-only basis - hand-selecting a small number of participants so the shape of each journey can be built around them. There is no application process; participation is by direct invitation only.
+
+Being active in my [Discord community](https://chat.nhcarrigan.com/) increases your chances of being invited.
+:::
+
 **ROADMAP TEMPLATES AND GOAL-SETTING RESOURCES**

 ## Roadmap Templates
@@ -2,6 +2,14 @@
 title: Priority and Effort Resources
 ---

+:::caution[Programme Sunset]
+The open Mentorship Programme has been sunset and is no longer accepting new participants. These pages remain available as reference material.
+
+I'm now running a private, personalised professional development programme on an invite-only basis - hand-selecting a small number of participants so the shape of each journey can be built around them. There is no application process; participation is by direct invitation only.
+
+Being active in my [Discord community](https://chat.nhcarrigan.com/) increases your chances of being invited.
+:::
+
 **PRIORITY ASSIGNMENT AND EFFORT ESTIMATION GUIDES**

 ## Priority Assignment Guide
@@ -2,6 +2,14 @@
 title: Project Planning Resources
 ---

+:::caution[Programme Sunset]
+The open Mentorship Programme has been sunset and is no longer accepting new participants. These pages remain available as reference material.
+
+I'm now running a private, personalised professional development programme on an invite-only basis - hand-selecting a small number of participants so the shape of each journey can be built around them. There is no application process; participation is by direct invitation only.
+
+Being active in my [Discord community](https://chat.nhcarrigan.com/) increases your chances of being invited.
+:::
+
 **PROJECT PLAN EXAMPLES AND BRAINSTORMING GUIDES**

 ## Project Plan Example
@@ -2,6 +2,14 @@
 title: Technical Breakdown Resources
 ---

+:::caution[Programme Sunset]
+The open Mentorship Programme has been sunset and is no longer accepting new participants. These pages remain available as reference material.
+
+I'm now running a private, personalised professional development programme on an invite-only basis - hand-selecting a small number of participants so the shape of each journey can be built around them. There is no application process; participation is by direct invitation only.
+
+Being active in my [Discord community](https://chat.nhcarrigan.com/) increases your chances of being invited.
+:::
+
 **TECHNICAL BREAKDOWN TEMPLATE AND EXAMPLES**

 ## Technical Breakdown Template
@@ -2,6 +2,14 @@
 title: User Story Resources
 ---

+:::caution[Programme Sunset]
+The open Mentorship Programme has been sunset and is no longer accepting new participants. These pages remain available as reference material.
+
+I'm now running a private, personalised professional development programme on an invite-only basis - hand-selecting a small number of participants so the shape of each journey can be built around them. There is no application process; participation is by direct invitation only.
+
+Being active in my [Discord community](https://chat.nhcarrigan.com/) increases your chances of being invited.
+:::
+
 **USER STORY TEMPLATES, EXAMPLES, AND WRITING GUIDES**

 ## User Story Format
@@ -1,94 +0,0 @@
---
-title: Managing Local Music
---
-
-**DOCUMENTING LOCAL MUSIC LIBRARY MANAGEMENT PROCEDURES**
-
-## 1. INTRODUCTION AND LEGAL FRAMEWORK
-
-### 1.1. Policy Overview
-
-This Music Management Documentation (hereinafter referred to as "the Documentation") provides technical procedures and instructions for managing local music libraries on Linux systems. This Documentation operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, and all applicable legal protections by reference.
-
-### 1.2. Purpose and Scope
-
-This Documentation describes technical procedures for managing local music libraries. This information is provided for informational purposes and personal use only.
-
-**IMPORTANT: Users are solely responsible for ensuring that all music acquisition, storage, and management activities comply with applicable copyright laws, licensing agreements, and legal requirements. Our organisation does not condone or support any illegal activities, including copyright infringement or piracy.**
-
-### 1.3. Legal Compliance Disclaimer
-
-All users must ensure that their music acquisition and management activities comply with:
-
- Applicable copyright laws and regulations
- Terms of service of music platforms and services
- Licensing agreements for music content
- All relevant intellectual property laws
-
-Our organisation assumes no responsibility for any illegal activities conducted using information from this Documentation.
-
-## 2. ACQUIRING MUSIC
-
-You are welcome to use any method you wish to *LEGALLY* acquire music. We would never encourage the criminal act of piracy. But maybe you're an artist and you want to archive or back up your own music - in that case, here you go:
-
-```bash
-yt-dlp -x --audio-format mp3 <url> --cookies-from-browser firefox
-```
-
-Omit the `--cookies-from-browser firefox` if you do not need authentication (auth is required for age-restricted content, for example).
-
-## 3. EDITING METADATA
-
-The specific meta tags you may need to set will vary depending on the music software you use. We have confirmed that `TIT2` is read as the title and `TPE1` is read as the artist when using Amberol on Linux and Musicolet on Android. Using `-t` and `-a` might work.
-
-```bash
-id3v2 "/path/to/song" --TIT2 "Song Title" --TPE1 "Song Artist" 
-```
-
-## 4. ADDING COVER IMAGES
-
-Download the image (we have confirmed JPEGs work) that you want to apply to the song, then run:
-
-```bash
-eyeD3 --add-image="/path/to/img":FRONT_COVER "/path/to/mp3"
-```
-
-## 5. COPYING TO ANDROID DEVICES
-
-You'll need to replace your paths and your device ID to match your local setup, but:
-
-```bash
-adb -s 192.168.12.105:5555 push music/* /storage/self/primary/Music
-```
-
-## 6. LIMITATION OF LIABILITY AND DISCLAIMERS
-
-### 6.1. Reference to Comprehensive Liability Framework
-
-**IMPORTANT: Comprehensive liability limitations, damage exclusions, and maximum liability caps are set forth in our Limitation of Liability and Indemnification Policy, which is incorporated herein by reference.**
-
-### 6.2. Legal Compliance Disclaimer
-
-This Documentation provides technical procedures only. Our organisation:
-
- Does not provide legal advice regarding music acquisition or copyright compliance
- Does not endorse or support any illegal activities, including copyright infringement
- Assumes no responsibility for users' compliance with copyright laws or licensing agreements
- Recommends that users consult qualified legal counsel for questions about copyright compliance
-
-### 6.3. Technical Accuracy Disclaimer
-
-While we strive to maintain accurate and current information in this Documentation, software tools, commands, and procedures may change over time. Users are responsible for:
-
- Verifying current software versions and compatibility
- Adapting procedures to their specific system configurations
- Ensuring their technical setup meets the requirements for these procedures
- Consulting additional resources for the most current technical information
-
-## 7. CONCLUSION
-
-This Music Management Documentation provides technical procedures for managing local music libraries on Linux systems. All users must ensure that their use of these procedures complies with applicable copyright laws, licensing agreements, and legal requirements.
-
---
-
-*For questions about music management procedures or legal compliance, please consult qualified legal counsel.*
@@ -1,151 +0,0 @@
---
-title: AI Prompts
---
-
-**DOCUMENTING STANDARD AI PROMPTS AND WORKFLOW TEMPLATES**
-
-## 1. INTRODUCTION AND LEGAL FRAMEWORK
-
-### 1.1. Policy Overview
-
-This AI Prompts Documentation (hereinafter referred to as "the Documentation") provides standard prompts, templates, and workflow instructions for using artificial intelligence tools in our organisational workflows. This Documentation operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, and all applicable legal protections by reference.
-
-### 1.2. Purpose and Scope
-
-This Documentation serves as a reference for standardised AI prompts used in various organisational contexts. These prompts are provided for convenience and consistency but may require customisation for specific use cases.
-
-**IMPORTANT: These prompts are provided as starting points and may require modification to meet specific requirements. Users are responsible for ensuring that any use of AI tools complies with applicable laws, regulations, and organisational policies.**
-
-### 1.3. AI Tool Usage Disclaimer
-
-Our organisation does not guarantee the accuracy, reliability, or appropriateness of outputs generated using these prompts. Users are responsible for:
-
- Reviewing and validating all AI-generated content
- Ensuring compliance with applicable laws and regulations
- Maintaining appropriate oversight of AI tool usage
- Protecting sensitive or confidential information when using AI tools
-
-## 2. AI PROMPTS
-
-### 2.1. Documentation Generation Prompt
-
-Open Claude Code in your project directory, then provide this prompt:
-
-```md
-Please go through the entire `src` directory and use the codebase to generate documentation for me, given the following template:
-
---
-title: <app name>
---
-
-<app name> (hereinafter the "Application") is <description>
-
-## 1. User Documentation
-
-This section is for those interacting with a live instance of the Application.
-
-## 2. Technical Documentation
-
-This section is for those interested in running their own instance of the Application.
-
-## 3. Legal Documentation
-
-This section is for expansions to our legal policies specific to the Application.
-
-## 4. Contributing Documentation
-
-This section is for documentation related to contributing to the Application's codebase.
-```
-
-### 2.2. Comprehension Question Generation Prompt
-
-We use this for some of our client work, but this is great for creating questions to quiz yourself on any document you've read.
-
-````md
-You must create three comprehension check questions for the lecture script the user provides. Do not include any other information. Format the response as a code block so the user can easily copy the syntax.
-
-Here is the format:
-
-```
-### Question 1:
-
-Which of the following is a key characteristic of relational databases?
-
-**A.** Flexible schema
-
-**B.** Document-based structure
-
-**C.** Key-value pairs
-
-**D.** Structured data in tables
-
-Hint: Think about how data is organised in relational databases.
-
-Answer: **D.** Structured data in tables
-
-### Question 2:
-
-Which of the following is a key characteristic of relational databases?
-
-**A.** Flexible schema
-
-**B.** Document-based structure
-
-**C.** Key-value pairs
-
-**D.** Structured data in tables
-
-Hint: Think about how data is organised in relational databases.
-
-Answer: **D.** Structured data in tables
-
-### Question 3:
-
-Which of the following is a key characteristic of relational databases?
-
-**A.** Flexible schema
-
-**B.** Document-based structure
-
-**C.** Key-value pairs
-
-**D.** Structured data in tables
-
-Hint: Think about how data is organised in relational databases.
-
-Answer: **D.** Structured data in tables
-```
-````
-
-## 3. LIMITATION OF LIABILITY AND DISCLAIMERS
-
-### 3.1. Reference to Comprehensive Liability Framework
-
-**IMPORTANT: Comprehensive liability limitations, damage exclusions, and maximum liability caps are set forth in our Limitation of Liability and Indemnification Policy, which is incorporated herein by reference.**
-
-### 3.2. AI Tool Usage Disclaimer
-
-These prompts are provided for informational purposes only. Our organisation:
-
- Does not guarantee the accuracy, reliability, or appropriateness of outputs generated using these prompts
- Does not warrant that these prompts will produce desired results in all contexts
- Assumes no responsibility for outcomes resulting from the use of these prompts with AI tools
- Recommends that users review and validate all AI-generated content
-
-### 3.3. User Responsibilities
-
-Users are responsible for:
-
- Reviewing and validating all AI-generated content before use
- Ensuring compliance with applicable laws, regulations, and organisational policies
- Protecting sensitive or confidential information when using AI tools
- Maintaining appropriate oversight and quality control of AI tool usage
- Adapting prompts to meet specific requirements and contexts
-
-## 4. CONCLUSION
-
-This AI Prompts Documentation provides standardised prompts and workflow templates for using artificial intelligence tools in our organisational workflows. All users are responsible for ensuring that their use of these prompts complies with applicable laws, regulations, and organisational policies, and for maintaining appropriate oversight of AI tool usage.
-
---
-
-*For questions about AI prompt usage or to suggest improvements, please contact appropriate organisational leadership through designated communication channels.*
@@ -1,852 +0,0 @@
---
-title: Templates
---
-
-**PROVIDING STANDARD TEMPLATES AND DOCUMENTATION FORMS**
-
-## 1. INTRODUCTION AND LEGAL FRAMEWORK
-
-### 1.1. Policy Overview
-
-This Templates Documentation (hereinafter referred to as "the Documentation") provides standard templates, forms, and documentation formats used throughout our organisation. This Documentation operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, and all applicable legal protections by reference.
-
-### 1.2. Purpose and Scope
-
-This Documentation serves as a reference for standardised templates used in various organisational contexts. These templates are provided for convenience and consistency but may require customisation for specific use cases.
-
-**IMPORTANT: These templates are provided as starting points and may require modification to meet specific legal, regulatory, or contextual requirements. Users are responsible for ensuring that any use of these templates complies with applicable laws and regulations.**
-
-### 1.3. Disclaimer
-
-Our organisation does not provide legal advice. These templates are provided for informational purposes only. Users should consult with qualified legal counsel when using these templates for legal matters or when compliance with specific regulations is required.
-
-## 2. TEMPLATES
-
-### 2.1. Legal Templates
-
-#### 2.1.1. DMCA Takedown Template
-
-```md
-To whom it may concern:
-
-We are writing to notify you of the copyright infringement and unlawful use of our copyrighted material that appear on the service for which you are the designated agent.
-
-The infringing material, which we contend belong to us, includes our original visual assets.
-
-The infringing material appears at the following location(s):
-
-<url>
-
-The original material is available at the following location(s):
-
-<url>
-
-This letter is the official notification under Section 512(c) of the Digital Millennium Copyright Act of 1998 ("DMCA") and we request the immediate removal of the aforementioned infringing materials from your servers.
-
-We also request that you immediately notify the infringer of this notice and inform them to cease any further posting of the infringing material to your server in the future.
-
-We are providing this notice in good faith and with the reasonable belief that we are the copyright holder of the material, and that the use of the described material in the manner complained is not authorised by us, our agents, or the law.
-
-We swear, under penalty of perjury, that the information in this notification is accurate and that we are the owner of the copyrighted material involved.
-
-If you have any questions, please feel free to reach out to us.
-```
-
-### 2.2. LinkedIn Templates
-
-#### 2.2.1. LinkedIn Cold Outreach Response Template
-
-```md
-I would be more than happy to chat! You can schedule time directly on my calendar:
-
-https://zcal.co/nhcarrigan/meet
-```
-
-#### 2.2.2. LinkedIn Post-Event Recommendation Template
-
-```md
-I had the absolute pleasure of working with [Participant's Name] during our [event name], where [they] consistently impressed me with [their] dedication, technical growth, and collaborative spirit.
-
-From the start, [Participant's Name] dove into the challenge with enthusiasm, applying [their] skills in [tech stack] to build real, impactful solutions. Whether working independently or as part of a team, [they] brought thoughtful ideas, clear communication, and a passion for learning that elevated everyone around [them].
-
-The value of [Participant's Name]'s contributions are immeasurable. Throughout the event, they [explain loads of goals here].
-
-By the end of the [event name], [Participant's Name] had delivered an outstanding project: [project name or brief description]. More than the final product, what stood out was [their] journey—embracing feedback, overcoming obstacles, and supporting others along the way.
-
-I wholeheartedly recommend [Participant's Name] for any opportunity in tech. [They] bring not just technical ability, but the kind of energy and curiosity that makes any team stronger.
-```
-
-#### 2.2.3. LinkedIn Mentorship Recommendation Template
-
-```md
-I had the privilege of mentoring [Mentee's Name] through my 1:1 mentorship programme, and from our very first session, it was clear that [they] approached learning with curiosity, determination, and an eagerness to grow.
-
-Over the course of the programme, [Mentee's Name] set clear goals and worked diligently towards them—building both technical skills in [specific tech stack, tools, or concepts] and the professional confidence to apply those skills in real-world scenarios. [They] embraced feedback, sought out challenges, and consistently demonstrated the resilience needed to push past obstacles.
-
-What impressed me most was [their] commitment to personal and professional growth—not just in terms of technical ability, but also in communication, collaboration, and problem-solving. By the end of the mentorship, [Mentee's Name] had successfully delivered [describe final project or achievement], showing not only technical proficiency but also the ability to think critically and adapt to new situations.
-
-I am confident that [Mentee's Name] will continue to excel in their career. They bring the kind of focus, curiosity, and dedication that make them a valuable asset to any team, and I am proud to have played a part in their journey.
-```
-
-### 2.3. Form Response Email Templates
-
-#### 2.3.1. Appeals Form - Approval Email Template
-
-Subject Line: `Appeal Decision - [Sanction Type] Appeal Upheld`
-
-```md
-Dear [Appellant's Name],
-
-Thank you for submitting your appeal regarding the disciplinary sanction imposed on [date of original sanction]. We acknowledge receipt of your appeal and have conducted a thorough review in accordance with our Community Disciplinary Appeals Policy.
-
-After careful consideration by the Appeals Panel, which included examination of all evidence and documentation, review of the original decision and its rationale, and assessment of your submissions and arguments, we have determined that your appeal has merit and meets the grounds for appeal as established in our policy.
-
-**Decision**: Your appeal has been upheld. The original disciplinary sanction has been [overturned/modified/reduced] as follows: [Insert specific details about the new decision].
-
-**Reasoning**: [Insert detailed reasoning here, addressing the specific grounds raised in the appeal and explaining why the appeal was successful. This should reference procedural compliance, proportionality of the sanction, factual accuracy, evidence considered, and correct application of community policies.]
-
-As outlined in Section 8.1 of our Community Disciplinary Appeals Policy, decisions of the Appeals Panel are final and binding. The decision outlined above is effective immediately.
-
-We appreciate your engagement with our appeals process and your respect for our community standards. We look forward to your continued positive participation in our community.
-
-Regards,
-```
-
-#### 2.3.2. Appeals Form - Rejection Email Template
-
-Subject Line: `Appeal Decision - [Sanction Type] Appeal Dismissed`
-
-```md
-Dear [Appellant's Name],
-
-Thank you for submitting your appeal regarding the disciplinary sanction imposed on [date of original sanction]. We acknowledge receipt of your appeal and have conducted a thorough review in accordance with our Community Disciplinary Appeals Policy.
-
-After careful consideration by the Appeals Panel, which included examination of all evidence and documentation, review of the original decision and its rationale, and assessment of your submissions and arguments, we have determined that your appeal does not meet the grounds for appeal as established in our policy.
-
-**Decision**: Your appeal has been dismissed. The original disciplinary sanction remains in full effect.
-
-**Reasoning**: [Insert detailed reasoning here, addressing the specific grounds raised in the appeal and explaining why the original decision was appropriate. This should reference procedural compliance, proportionality of the sanction, factual accuracy, evidence considered, and correct application of community policies.]
-
-As outlined in Section 8.1 of our Community Disciplinary Appeals Policy, decisions of the Appeals Panel are final and binding. No further appeals or reviews are available through our internal processes.
-
-We understand that this decision may be disappointing. Our appeals process is designed to ensure fairness and transparency, and we have given your submission careful consideration. The original sanction was imposed in accordance with our community standards and policies, which are designed to maintain a safe and welcoming environment for all members.
-
-If you have any questions about this decision, please note that our Appeals Panel's determination is final. We appreciate your understanding and respect for our community standards and processes.
-
-Regards,
-```
-
-#### 2.3.3. Commissions Form - Approval Email Template
-
-```md
-Hello [Requester's Name],
-
-Thank you for your commission request! We are excited to work with you on [brief description of commission].
-
-We have reviewed your request and are pleased to accept it. We will begin working on your commission and will keep you updated on our progress.
-
-**Next Steps:**
- [Insert specific next steps, timeline, or requirements here]
- You will receive updates via [preferred contact method]
- Expected completion date: [date if applicable]
-
-If you have any questions or need to make changes to your request, please don't hesitate to reach out to us.
-
-We look forward to creating something amazing for you!
-
-Best regards,
-```
-
-#### 2.3.4. Commissions Form - Rejection Email Template
-
-```md
-Hello [Requester's Name],
-
-Thank you for your interest in commissioning work from us. We appreciate you taking the time to submit your request.
-
-After careful review, we have decided not to proceed with your commission request at this time. This decision may be based on factors such as current workload, project scope, timeline constraints, or alignment with our services.
-
-Please note that due to the volume of requests we receive, we are unable to provide detailed feedback on every declined request.
-
-We encourage you to stay engaged with our community and projects. If your needs change or you have a different project in mind, we would welcome a new request in the future.
-
-If you have any questions, please reach out in our Discord community: https://chat.nhcarrigan.com
-
-Best regards,
-```
-
-#### 2.3.5. Community Recognition Form - Approval Email Template
-
-```md
-Hello [Nominator's Name],
-
-Thank you for taking the time to nominate [Nominee's Name] for community recognition! We truly appreciate you highlighting the positive contributions of community members.
-
-We are pleased to inform you that your nomination has been accepted and will be considered in our next recognition cycle. The recognition process involves review by our leadership team, and selected nominees will be celebrated through our community recognition programmes.
-
-**What Happens Next:**
- Your nomination will be reviewed by our recognition committee
- Selected nominees will be notified and celebrated publicly
- Recognition may include awards, spotlights, or other forms of appreciation
- All nominations help us build a more appreciative and inclusive community
-
-Thank you for helping us celebrate the amazing contributions of our community members. Your nomination makes a difference!
-
-If you have any questions, please reach out in our Discord community: https://chat.nhcarrigan.com
-
-Warm regards,
-```
-
-#### 2.3.6. Community Recognition Form - Rejection Email Template
-
-```md
-Hello [Nominator's Name],
-
-Thank you for taking the time to submit a nomination for community recognition. We truly appreciate your effort to highlight positive contributions in our community.
-
-After careful review, we have decided not to proceed with this nomination at this time. This decision may be based on factors such as eligibility criteria, timing, or alignment with our recognition programmes.
-
-Please note that due to the volume of nominations we receive, we are unable to provide detailed feedback on every declined nomination.
-
-We encourage you to continue recognising positive contributions in our community. There are many ways to show appreciation, including direct recognition, peer appreciation, and future nominations.
-
-If you have any questions about our recognition programmes, please reach out in our Discord community: https://chat.nhcarrigan.com
-
-Thank you again for your engagement with our community.
-
-Warm regards,
-```
-
-#### 2.3.7. Contact Form - Approval Email Template
-
-```md
-Hello [Contact's Name],
-
-Thank you for reaching out to us through our contact form. We have received your message regarding [brief topic summary].
-
-We appreciate you taking the time to contact us and are pleased to confirm that we have received your inquiry. [Insert specific response or next steps here, such as:]
-
- We will review your request and respond within [timeframe]
- A team member will be in touch shortly
- We have scheduled a follow-up [meeting/call/response] for [date/time]
-
-If you have any urgent questions or need immediate assistance, please don't hesitate to reach out in our Discord community: https://chat.nhcarrigan.com
-
-We look forward to connecting with you!
-
-Best regards,
-```
-
-#### 2.3.8. Contact Form - Rejection Email Template
-
-```md
-Hello [Contact's Name],
-
-Thank you for reaching out to us through our contact form. We have received your message regarding [brief topic summary].
-
-After reviewing your inquiry, we are unable to assist with your request at this time. This may be due to factors such as scope of services, current capacity, or alignment with our mission and values.
-
-Please note that due to the volume of inquiries we receive, we are unable to provide detailed feedback on every declined request.
-
-If you have questions about our services or policies, we encourage you to review our documentation at https://docs.nhcarrigan.com or join our Discord community: https://chat.nhcarrigan.com
-
-Thank you for your understanding.
-
-Best regards,
-```
-
-#### 2.3.9. Development Review Requests Form - Approval Email Template
-
-```md
-Hello [Requester's Name],
-
-Thank you for your development review request! We have reviewed your submission and are pleased to accept your request for review of [project/repository name or description].
-
-**Review Details:**
- Review Type: [Code Review/Project Review/Architecture Review/etc.]
- Materials to be Reviewed: [list of materials]
- Expected Timeline: [timeline for review completion]
-
-**Next Steps:**
- Our team will begin reviewing your materials
- You will receive detailed feedback via [communication method]
- We will provide constructive suggestions for improvement
-
-Please note that development reviews are provided as free services to active community members, and feedback is provided in good faith based on our expertise and best practices.
-
-If you have any questions or need to provide additional materials, please don't hesitate to reach out.
-
-We look forward to reviewing your work!
-
-Best regards,
-```
-
-#### 2.3.10. Development Review Requests Form - Rejection Email Template
-
-```md
-Hello [Requester's Name],
-
-Thank you for your interest in receiving a development review. We appreciate you taking the time to submit your request.
-
-After careful review, we have decided not to proceed with your development review request at this time. This decision may be based on factors such as:
- Current review capacity and workload
- Alignment with our review services and expertise
- Community membership and engagement requirements
- Project scope or complexity
-
-Please note that development reviews are provided as free services exclusively to active members of our community. If you are not currently an active community member, we encourage you to join our Discord community at https://chat.nhcarrigan.com and become an active participant.
-
-If you have questions about our development review services or would like to resubmit in the future, please reach out in our Discord community: https://chat.nhcarrigan.com
-
-Thank you for your understanding.
-
-Best regards,
-```
-
-#### 2.3.11. Events Form - Approval Email Template
-
-```md
-Hello [Event Organiser's Name],
-
-Thank you for your event request! We are excited about your proposed event: [Event Name].
-
-We have reviewed your submission and are pleased to approve your event request. We look forward to supporting and promoting this event within our community.
-
-**Event Details:**
- Event Name: [Event Name]
- Proposed Date: [Date]
- Event Type: [Type of event]
-
-**Next Steps:**
- [Insert specific next steps, such as scheduling, promotion, or coordination details]
- We will work with you to finalise event details
- Event promotion will begin [timeline]
-
-If you have any questions or need to make changes to your event details, please don't hesitate to reach out to us.
-
-Thank you for contributing to our community through this event!
-
-Best regards,
-```
-
-#### 2.3.12. Events Form - Rejection Email Template
-
-```md
-Hello [Event Organiser's Name],
-
-Thank you for your interest in organising an event with our community. We appreciate you taking the time to submit your event request: [Event Name].
-
-After careful review, we have decided not to proceed with your event request at this time. This decision may be based on factors such as:
- Current event calendar and capacity
- Alignment with our community values and mission
- Resource availability and support requirements
- Event scope or logistics
-
-Please note that due to the volume of event requests we receive, we are unable to provide detailed feedback on every declined request.
-
-We encourage you to stay engaged with our community and consider submitting future event proposals. If you have questions about our event policies or would like to discuss alternative event formats, please reach out in our Discord community: https://chat.nhcarrigan.com
-
-Thank you for your understanding and continued engagement with our community.
-
-Best regards,
-```
-
-#### 2.3.13. Mock Interview Requests Form - Approval Email Template
-
-```md
-Hello [Requester's Name],
-
-Thank you for your mock interview request! We have reviewed your submission and are pleased to accept your request for a [technical/behavioural/combined] mock interview.
-
-**Interview Details:**
- Interview Type: [Type]
- Target Role: [Role if provided]
- Interview Format: [Format]
-
-**Next Steps:**
- We will coordinate with you to schedule your mock interview session
- Mock interviews are typically conducted via [video call/voice call]
- Sessions typically last between 30-60 minutes
- You will receive preparation materials and session details via [communication method]
-
-Please note that mock interviews are provided as free services exclusively to active members of our community. We look forward to helping you prepare for your upcoming interview!
-
-If you have any questions or need to reschedule, please don't hesitate to reach out to us.
-
-Best regards,
-```
-
-#### 2.3.14. Mock Interview Requests Form - Rejection Email Template
-
-```md
-Hello [Requester's Name],
-
-Thank you for your interest in receiving a mock interview. We appreciate you taking the time to submit your request.
-
-After careful review, we have decided not to proceed with your mock interview request at this time. This decision may be based on factors such as:
- Current interview capacity and availability
- Community membership and engagement requirements
- Interview type or scope alignment with our services
- Scheduling constraints
-
-**IMPORTANT**: Mock interviews are provided as free services EXCLUSIVELY to active members of our community. These services are NOT available to the general public. To be eligible, you MUST be an active, engaged member of our community with demonstrated participation and engagement.
-
-If you are not currently an active community member, we encourage you to join our Discord community at https://chat.nhcarrigan.com and become an active participant. Once you have established active community membership through regular participation and engagement, you will be eligible to request mock interview services.
-
-If you have questions about our mock interview services or community membership, please reach out in our Discord community: https://chat.nhcarrigan.com
-
-Thank you for your understanding.
-
-Best regards,
-```
-
-#### 2.3.15. Portfolio Review Requests Form - Approval Email Template
-
-```md
-Hello [Requester's Name],
-
-Thank you for your portfolio review request! We have reviewed your submission and are pleased to accept your request for review of your [resume/LinkedIn profile/GitHub profile/portfolio website].
-
-**Review Details:**
- Review Type: [Resume/LinkedIn/GitHub/Portfolio Review]
- Materials to be Reviewed: [list of materials or links]
-
-**Next Steps:**
- Our team will begin reviewing your materials
- You will receive detailed feedback via [communication method]
- We will provide constructive suggestions for improvement based on industry best practices
-
-Please note that portfolio reviews are provided as free services to active community members, and feedback is provided in good faith based on our expertise and professional standards.
-
-If you have any questions or need to provide additional materials, please don't hesitate to reach out.
-
-We look forward to reviewing your materials and helping you improve your professional presentation!
-
-Best regards,
-```
-
-#### 2.3.16. Portfolio Review Requests Form - Rejection Email Template
-
-```md
-Hello [Requester's Name],
-
-Thank you for your interest in receiving a portfolio review. We appreciate you taking the time to submit your request.
-
-After careful review, we have decided not to proceed with your portfolio review request at this time. This decision may be based on factors such as:
- Current review capacity and workload
- Community membership and engagement requirements
- Material accessibility or completeness
- Review type alignment with our services
-
-**IMPORTANT**: Portfolio reviews are provided as free services EXCLUSIVELY to active members of our community. These services are NOT available to the general public. To be eligible, you MUST be an active, engaged member of our community with demonstrated participation and engagement.
-
-If you are not currently an active community member, we encourage you to join our Discord community at https://chat.nhcarrigan.com and become an active participant. Once you have established active community membership through regular participation and engagement, you will be eligible to request portfolio review services.
-
-If you have questions about our portfolio review services or community membership, please reach out in our Discord community: https://chat.nhcarrigan.com
-
-Thank you for your understanding.
-
-Best regards,
-```
-
-#### 2.3.17. Recommendations Form - Approval Email Template
-
-```md
-Hello [Requester's Name],
-
-Thank you for your recommendation request! We have reviewed your submission and are pleased to accept your request for a recommendation.
-
-**Recommendation Details:**
- Recommendation Type: [LinkedIn Recommendation/General Recommendation/etc.]
- Context: [Brief context if provided]
-
-**Next Steps:**
- We will prepare your recommendation based on our relationship and your contributions
- Recommendations are typically provided via [LinkedIn/email/etc.]
- You will receive a copy of the recommendation once it is completed
- Expected completion: [timeline]
-
-Please note that recommendations are provided as free services in good faith, based on our relationship and knowledge of your work. We provide honest, accurate recommendations based on our direct experience with you.
-
-If you have any questions or need to provide additional context, please don't hesitate to reach out.
-
-We are happy to support you in your professional journey!
-
-Best regards,
-```
-
-#### 2.3.18. Recommendations Form - Rejection Email Template
-
-```md
-Hello [Requester's Name],
-
-Thank you for your interest in receiving a recommendation. We appreciate you taking the time to submit your request.
-
-After careful review, we have decided not to proceed with your recommendation request at this time. This decision may be based on factors such as:
- Insufficient direct working relationship or interaction
- Lack of sufficient context or experience to provide an accurate recommendation
- Timeline constraints or capacity limitations
- Alignment with our recommendation policy and standards
-
-Please note that we can only provide recommendations when we have sufficient direct experience and relationship with the requester to provide an honest, accurate, and meaningful recommendation.
-
-If you believe there has been an error or would like to discuss your request further, please reach out in our Discord community: https://chat.nhcarrigan.com
-
-Thank you for your understanding.
-
-Best regards,
-```
-
-#### 2.3.19. Staff Applications Form - Approval Email Template
-
-```md
-Dear [Applicant's Name],
-
-Thank you so much for taking the time to apply for a volunteer role with NHCarrigan. We truly appreciate your interest in contributing your time and energy to our community.
-
-After carefully reviewing your application, we are excited to inform you that we would like to move forward with your candidacy! We were impressed by [specific aspects of their application] and believe you would be a valuable addition to our team.
-
-**Next Steps:**
- You will receive a separate email with your contract and onboarding materials
- Please review the contract carefully and reach out with any questions or concerns
- You can reach out to us on Discord (https://chat.nhcarrigan.com) or reply to this email if you have any questions or concerns
-
-We are thrilled about the possibility of working with you and look forward to welcoming you to our team. Thank you again for your interest and enthusiasm!
-
-Warm regards,
-```
-
-#### 2.3.20. Staff Applications Form - Onboarding Email Template
-
-```md
-Dear [New Staff Member's Name],
-
-Welcome to the NHCarrigan team! We are thrilled to have you join us and are excited to begin working together.
-
-**Getting Started:**
-
-1. **Join Our Discord Server:**
-   - Please join our Discord community at: https://chat.nhcarrigan.com
-   - This is where most of our team communication and collaboration happens
-
-2. **Access Credentials:**
-   - **Email:**
-     - Address: 
-     - Password:
-     - Can access email via web at https://mail.nhcarrigan.com/mail or through any email client/app. A reminder that this is only for work-related use. Please do not spam people and get our mail server blocked (I do have logs).
-   - **Gitea:** https://git.nhcarrigan.com
-     - Username:
-     - Password: 
-
-3. **Complete Your Training:**
-   - Please complete the policy assessment form for training: https://forms.nhcarrigan.com/o/docs/forms/nxaJyKBuKH9nrt3m5VC98w/4
-   - This is an important step to ensure you are familiar with our policies and procedures
-
-**Next Steps:**
- Our team will be in touch shortly to discuss your role-specific responsibilities
- Feel free to explore our documentation at https://docs.nhcarrigan.com
-
-If you have any questions or need assistance getting set up, please don't hesitate to reach out to us on Discord or reply to this email.
-
-We are excited to have you on board and look forward to working with you!
-
-Warm regards,
-```
-
-#### 2.3.21. Staff Applications Form - Rejection Email Template
-
-```md
-Dear [Applicant's Name],
-
-Thank you so much for taking the time to apply for a volunteer role with NHCarrigan. We truly appreciate your interest in contributing your time and energy to our community.
-
-After carefully reviewing your application, we've decided not to move forward with your candidacy for this volunteer position at this time. Please don't take this as a reflection of your value or potential—our selection process is highly competitive, and we often have to make very difficult decisions.
-
-Please note that due to the large volume of applications we receive, we are unable to provide personalised feedback. Here are some common application issues we see:
-
-1. Low-effort Application: Please ensure you are taking the time to provide detailed, well-thought responses. The more effort you put in, the more likely we will be able to accept your application.
-2. Invalid Discord ID: Applications require you to provide your unique Discord ID - this is a 16 to 19 digit number that uniquely identifies your Discord account. If this is incorrect, we are unable to accept an application. If you need help finding yours, please refer to https://dis.gd/findid
-3. Concerning Responses: If your responses to any of the application questions raise red flags, we decline your application. Remember that you want to paint yourself in the best light here.
-
-We still encourage you to stay engaged with our community spaces, events, and projects. There are always opportunities to connect, learn, and grow together, and we would love to see you continue to participate.
-
-We encourage you to take the time to consider these common points of failure, and would welcome a resubmission from you in the future.
-
-Thank you again for your interest and enthusiasm. We wish you the very best in all your endeavors and hope our paths cross again in the future.
-
-Warm regards,
-```
-
-#### 2.3.22. Testimonials Form - Approval Email Template
-
-```md
-Hello [Contributor's Name],
-
-Thank you for sharing your testimonial with us! We have reviewed your submission and are pleased to accept it for publication.
-
-**Testimonial Details:**
- Your testimonial will be reviewed and may be featured on our website, social media, or other promotional materials
- We may edit your testimonial for length, clarity, or formatting whilst preserving your message and intent
- You will be credited as [name/handle as provided]
-
-**Next Steps:**
- Your testimonial will be added to our review queue
- We will notify you when it is published (if applicable)
- Thank you for helping others learn about our community and services!
-
-Your words help us build trust and connect with others who might benefit from our community. We truly appreciate you taking the time to share your experience.
-
-If you have any questions or would like to make changes to your testimonial, please don't hesitate to reach out.
-
-Best regards,
-```
-
-#### 2.3.23. Testimonials Form - Rejection Email Template
-
-```md
-Hello [Contributor's Name],
-
-Thank you for taking the time to submit a testimonial. We appreciate your interest in sharing your experience with our community.
-
-After careful review, we have decided not to publish your testimonial at this time. This decision may be based on factors such as:
- Content alignment with our community values and standards
- Formatting or clarity requirements
- Current testimonial collection needs
- Verification or authenticity concerns
-
-Please note that due to the volume of testimonials we receive, we are unable to provide detailed feedback on every declined submission.
-
-We encourage you to stay engaged with our community and consider submitting a testimonial in the future if your experience changes or if you have additional feedback to share.
-
-If you have questions about our testimonial process, please reach out in our Discord community: https://chat.nhcarrigan.com
-
-Thank you for your understanding and continued engagement with our community.
-
-Best regards,
-```
-
-### 2.4. Form Components
-
-#### 2.4.1. Form Consent for Email Communications
-
-Description:
-
-```
-At NHCarrigan, we are fully committed to respecting and protecting your privacy. We strictly adhere to a policy of non-disclosure regarding your personal data; we do not sell, trade, or transfer your information to outside parties. The contact details you provide will be used exclusively for the purpose of responding to your inquiry or addressing the subject of this form. For a complete overview of our data practices, please review our [Privacy Policy](https://docs.nhcarrigan.com/legal/privacy/).
-```
-
-Question: 
-
-```
-I agree to be contacted via email, solely for the purpose of addressing this submission.
-```
-
-#### 2.4.2. Form Image Header
-
-```html
-<div style="width: 100%; text-align: center"><img src="https://cdn.nhcarrigan.com/logo.png" style="width: 250px; height: 250px"></div>
-```
-
-#### 2.4.3. Form Confirmation
-
-Add this at the end of any form specific text.
-
-```
-If you'd like to stay up to date on everything we do, come hang out in our server! https://chat.nhcarrigan.com
-```
-
-### 2.5. Community & Communication Templates
-
-#### 2.5.1. Discord Server Introduction Template
-
-```md
-Hello~! I'm Naomi, a 34 year old transfem software engineer and community manager based in Washington. All of my work (and therefore most of my life) is spent online, so I'm always looking for new spaces and people to vibe with. Remote work can feel dreadfully isolating, and this is my attempt to combat that feeling.
-
-<insert bit about community here>
-``` 
-
-#### 2.5.2. freeCodeCamp Contributor Sprint Template
-
-```md
-## This issue is part of Naomi's sprint initiatives.
-
-If you are interested in working on this issue, [join our Discord](https://chat.freecodecamp.org) and ping Naomi!
-
-### Action Items
-
- [ ] Prototype created and PRed to https://github.com/freeCodeCamp/curriculumexpansion
- [ ] Prototype reviewed + approved + merged by staff
- [ ] Break prototype down into steps (if workshop) or individual "step" (if lab) - write description, hint text **only** (no tests yet), and seed code. Refer to https://contribute.freecodecamp.org/how-to-work-on-coding-challenges
- [ ] DRAFT PR opened on https://github.com/freeCodeCamp/freeCodeCamp
- [ ] Team + Naomi review your steps, confirm the breakdown + user stories look good
- [ ] Begin writing the actual test logic, refer to https://contribute.freecodecamp.org/curriculum-help/#basic-usage-pattern for how to write tests for Python challenges
- [ ] Mark PR as not a draft, team reviews + approves + merges
- [ ] YOU DID IT GO CELEBRATE!
-
-### Other Details
-
- Remember to keep an eye on your PRs and respond to review comments and suggestions
- For workshops, refer to: https://contribute.freecodecamp.org/how-to-work-on-coding-challenges/
- For labs, refer to: https://contribute.freecodecamp.org/how-to-work-on-labs/
-
-### Questions
-
-Ping Naomi in the sprint channel on Discord
-```
-
-### 2.6. Gaming Templates
-
-#### 2.6.1. Guild Wars 2 Recruitment Advertisement Template
-
-This has to be sent in two chat messages because of the length.
-
-```
-Hiya friends~! Naomi's Newbies is a new guild that is really focused on helping newer players come to love the game, and supporting casual players who have busy schedules.
-```
-
-```
-We have no activity requirement, no rep requirement, a Discord community, and more! If you are interested, please whisper me and I will gladly invite you!
-```
-
-### 2.7. Donation Templates
-
-#### 2.7.1. Discord Bot Donation Copy Template
-
-These go in the bot SKUs:
-
-##### 2.7.1.1. Subscription Name
-
-```
-Sponsor Naomi
-```
-
-##### 2.7.1.2. Subscription Description
-
-```
-**How Your Support Makes a Difference**
-
-1. Creating Free Software
-  - Develop open-source tools accessible to everyone
-  - Design Discord bots for community management and safe spaces
-  - Create learning resources and accessibility-focused web applications
-
-2. Building Inclusive Communities
-  - Manage welcoming online spaces where diverse voices are celebrated
-  - Organise virtual events, workshops, and mentorship programmes
-  - Implement inclusive community guidelines
-
-3. Guiding Others in Tech
-  - Provide mentorship to aspiring technologists from underrepresented groups
-  - Create educational content (tutorials, blog posts, videos)
-  - Offer career advice and emotional support
-
-4. Your Contribution's Ripple Effect:
-  - Challenges the status quo of the tech industry
-  - Creates opportunities for underrepresented individuals in STEM
-  - Fosters innovation through diverse perspectives
-  - Builds a tech community that reflects and serves all of society
-
-Every donation, regardless of size, contributes to this mission. Together, we're creating a more inclusive, accessible, and diverse future for technology.
-Thank you for considering a donation and being part of this important journey.
-```
-
-##### 2.7.1.3. Benefit Name
-
-```
-Your donation:
-```
-
-##### 2.7.1.4. Benefit Description
-
-```
-Helps a transfemme technology witch create free software, build inclusive communities, and guide others on their journey in tech.
-```
-
-##### 2.7.1.5. Notes
-
- Use my avatar for subscription
- Use pentatrans for benefit
-
-### 2.8. freeCodeCamp Templates
-
-#### 2.8.1. freeCodeCamp Sprint Issue Template
-
-```md
-**Type:** Workshop/Lab/????  
-**Summary:**
-
-**User Stories**
-1. 
-2.
-3.
-
-**Technical Notes**
- 
-
-
-
-## This issue is part of Naomi's sprint initiatives.
-
-If you are interested in working on this issue, [join our Discord](https://chat.freecodecamp.org) and ping Naomi!
-
-### Action Items
-
- [ ] Prototype created and PRed to https://github.com/freeCodeCamp/curriculumexpansion
- [ ] Prototype reviewed + approved + merged by staff
- [ ] Break prototype down into steps (if workshop) or individual "step" (if lab) - write description, hint text **only** (no tests yet), and seed code.
- [ ] DRAFT PR opened on https://github.com/freeCodeCamp/freeCodeCamp
- [ ] Team + Naomi review your steps, confirm the breakdown + user stories look good
- [ ] Begin writing the actual test logic, refer to https://contribute.freecodecamp.org/curriculum-help/#js-helper for how to write tests for JS challenges
- [ ] Mark PR as not a draft, team reviews + approves + merges
- [ ] YOU DID IT GO CELEBRATE!
-
-### Other Details
-
- Remember to keep an eye on your PRs and respond to review comments and suggestions
- For workshops, refer to: https://contribute.freecodecamp.org/how-to-work-on-coding-challenges/
- For labs, refer to: https://contribute.freecodecamp.org/how-to-work-on-labs/
-
-### Questions
-
-Ping Naomi in the sprint channel on Discord
-```
-
-#### 2.8.2. freeCodeCamp Sprint Progress Update
-
-```md
-**Progress Update - <date>**
-
-<summarise what contributor said>
-```
-
-## 3. DISCLAIMERS AND USAGE REQUIREMENTS
-
-### 3.1. Reference to Comprehensive Liability Framework
-
-**IMPORTANT: Comprehensive liability limitations, damage exclusions, and maximum liability caps are set forth in our Limitation of Liability and Indemnification Policy, which is incorporated herein by reference.**
-
-### 3.2. Template Usage Disclaimer
-
-These templates are provided for informational purposes only. Our organisation:
-
- Does not provide legal advice or guarantee the legal effectiveness of these templates
- Does not warrant that these templates will meet specific legal, regulatory, or contextual requirements
- Recommends that users consult with qualified legal counsel when using these templates for legal matters
- Assumes no responsibility for outcomes resulting from the use of these templates
-
-### 3.3. Customisation Requirements
-
-Users are responsible for:
-
- Customising templates to meet their specific needs and requirements
- Ensuring compliance with applicable laws, regulations, and organisational policies
- Verifying the accuracy and appropriateness of template content for their specific use case
- Obtaining appropriate legal review when necessary
-
-## 4. CONCLUSION
-
-This Templates Documentation provides standardised templates and forms for use throughout our organisation. All users are responsible for ensuring that their use of these templates complies with applicable laws, regulations, and organisational requirements.
-
---
-
-*For questions about template usage or to suggest improvements, please contact appropriate organisational leadership through designated communication channels.*
@@ -165,7 +165,7 @@ Your Discord bot requires the following Gateway Intents:

 Create a `.env` file in the project root with the following variables:

-```env
+```sh
 # Discord Bot Configuration
 TOKEN=your_discord_bot_token

@@ -64,7 +64,7 @@ This section is for those interested in running their own instance of the Applic
   ```

 4. Edit `.env` with your configuration:
-   ```env
+   ```sh
   DISCORD_TOKEN="your-discord-bot-token"
   SENTRY_DSN="your-sentry-dsn"
   DEBUG_HOOK="your-discord-webhook-url"
@@ -363,7 +363,7 @@ For questions or support:

 ### 4.10. Issue Reporting

-Please report bugs in the #bug-reports forum channel and feature requests in the #feature-requests forum channel on our Discord community.
+Please report bugs in the [Bug Reports](https://support.nhcarrigan.com/c/bug-reports/6) category and feature requests in the [Feature Requests](https://support.nhcarrigan.com/c/feature-requests/7) category on our support forum.

 Include:
 - Clear description of the issue or feature
@@ -76,8 +76,8 @@ Cordelia has a distinctive personality:

 ### Support and Feedback

- **Bug Reports**: Post in the #bug-reports forum channel on our Discord community
- **Feature Requests**: Post in the #feature-requests forum channel on our Discord community
+- **Bug Reports**: Post in the [Bug Reports](https://support.nhcarrigan.com/c/bug-reports/6) category on our support forum
+- **Feature Requests**: Post in the [Feature Requests](https://support.nhcarrigan.com/c/feature-requests/7) category on our support forum
 - **General Support**: Visit the [chat server](https://chat.nhcarrigan.com)
 - **Contact**: Email `contact@nhcarrigan.com`

@@ -264,7 +264,7 @@ src/

 ### Contribution Process

-1. **Issue Creation**: Post detailed bug reports or feature requests in the appropriate Discord forum channel (#bug-reports or #feature-requests)
+1. **Issue Creation**: Post detailed bug reports or feature requests in the appropriate support forum category ([Bug Reports](https://support.nhcarrigan.com/c/bug-reports/6) or [Feature Requests](https://support.nhcarrigan.com/c/feature-requests/7))
 2. **Discussion**: Discuss approach before starting work
 3. **Implementation**: Follow coding standards and patterns
 4. **Testing**: Test thoroughly in development environment
@@ -647,7 +647,7 @@ When contributing, keep security in mind:

 If you need help contributing:

- Post in the #bug-reports or #feature-requests forum channels on our Discord community
+- Post in the [Bug Reports](https://support.nhcarrigan.com/c/bug-reports/6) or [Feature Requests](https://support.nhcarrigan.com/c/feature-requests/7) categories on our support forum
 - Join the [Chat Server](https://chat.nhcarrigan.com)
 - Email: `contact@nhcarrigan.com`

@@ -114,7 +114,7 @@ npm install

 Create a `prod.env` file in the root directory with the following variables:

-```env
+```sh
 DISCORD_TOKEN=your_discord_bot_token
 AI_TOKEN=your_anthropic_api_key
 LOG_TOKEN=your_logging_token (optional)
@@ -199,7 +199,7 @@ pnpm install

 Create a `prod.env` file with the following variables:

-```env
+```sh
 DISCORD_TOKEN=your_discord_bot_token
 MONGO_URI=your_mongodb_connection_string
 LOG_TOKEN=your_logging_service_token
@@ -225,7 +225,7 @@ If you encounter bugs or have feature requests:
 - Chat Server: [https://chat.nhcarrigan.com](https://chat.nhcarrigan.com)
 - Email: contact@nhcarrigan.com
 - Repository: [https://git.nhcarrigan.com/nhcarrigan/logger](https://git.nhcarrigan.com/NHCarrigan/logger)
- Issues: Post in the #bug-reports or #feature-requests forum channels on our Discord community
+- Issues: Post in the [Bug Reports](https://support.nhcarrigan.com/c/bug-reports/6) or [Feature Requests](https://support.nhcarrigan.com/c/feature-requests/7) categories on our support forum

 ### Package Information

@@ -136,7 +136,7 @@ The Application is built with the following technologies:

 Create a `prod.env` file in the project root with the following variables:

-```env
+```sh
 # Required: Anthropic API key for Claude AI
 ANTHROPIC_API_KEY=your_anthropic_api_key_here

@@ -50,7 +50,7 @@ Rosalia Nightsong is built using:

 The application requires the following environment variables:

-```env
+```sh
 MATRIX_ACCESS_TOKEN="matrix_access_token"
 MATRIX_ROOM_ID="matrix_room_id"
 API_AUTH="api_authentication_token"
@@ -218,7 +218,7 @@ This section is for those interested in running their own instance of the Applic
 4. **Set up environment variables:**

   Create a `.env` file with required credentials:
-   ```env
+   ```sh
   # Crowdin (for translation scripts)
   CROWDIN_PROJECT_ID=your_project_id
   CROWDIN_API_URL=https://api.crowdin.com/api/v2
@@ -24,7 +24,9 @@ Our community operates across various platforms including:

 **(e)** **Documentation Sites**: Knowledge bases, policies, guides;

-**(f)** **Other Platforms**: Emerging technologies and specialised tools.
+**(f)** **Support Forum**: Structured support requests, bug reports, feature requests at support.nhcarrigan.com;
+
+**(g)** **Other Platforms**: Emerging technologies and specialised tools.

 ### 1.3. Integration with Existing Policies

@@ -136,6 +138,29 @@ This training operates within our policy framework:
 - Competitive and cooperative balance
 - Fun and entertainment emphasis

+### 3.4. Support Forum
+
+#### 3.4.1. Unique Characteristics
+- Structured, categorised support system
+- Asynchronous, persistent discussions
+- Searchable knowledge base functionality
+- Topic-based organisation and threading
+- Solution marking and resolution tracking
+
+#### 3.4.2. Moderation Considerations
+- **Category Management**: Ensure posts are in appropriate categories
+- **Thread Organisation**: Maintain clear, searchable thread titles
+- **Solution Tracking**: Mark resolved issues for future reference
+- **Privacy Protection**: Redact sensitive information from public posts
+- **Knowledge Curation**: Build searchable solutions database
+
+#### 3.4.3. Community Culture
+- Professional, solution-focused communication
+- Detailed problem descriptions and responses
+- Knowledge sharing and documentation emphasis
+- Patient, thorough assistance approach
+- Long-form, comprehensive discussions
+
 ## 4. COORDINATION STRATEGIES AND BEST PRACTICES

 ### 4.1. Information Sharing Across Platforms
@@ -322,6 +347,22 @@ This training operates within our policy framework:
 - **Crisis Communication**: Handle public relations during difficult situations
 - **Growth Strategies**: Support community growth and member acquisition

+### 6.4. Support Forum Responsibilities
+
+#### 6.4.1. Thread Management
+- Monitor new posts and ensure proper categorisation
+- Merge duplicate threads while preserving context
+- Mark solutions when issues are resolved
+- Pin important announcements and guides
+- Archive outdated or resolved discussions
+
+#### 6.4.2. Knowledge Base Development
+- **Content Curation**: Build comprehensive solution documentation
+- **FAQ Maintenance**: Update frequently asked questions regularly
+- **Category Organisation**: Maintain logical, searchable structure
+- **Cross-Reference**: Link related topics and solutions
+- **Quality Control**: Ensure accuracy of technical information
+
 ## 7. COORDINATION CHALLENGES AND SOLUTIONS

 ### 7.1. Common Coordination Problems
@@ -0,0 +1,337 @@
+---
+title: Support Forum Moderation Training for Staff
+---
+
+**ESSENTIAL TRAINING FOR FORUM MODERATION TEAM**
+
+## 1. INTRODUCTION AND SCOPE
+
+### 1.1. Purpose of This Training
+
+This training document provides comprehensive guidance for Team members responsible for moderating our Support Forum at [support.nhcarrigan.com](https://support.nhcarrigan.com). The Support Forum serves as our primary platform for structured support requests, bug reports, feature requests, and community feedback.
+
+### 1.2. Forum Structure and Categories
+
+Our Support Forum is organised into the following categories:
+
+**(a)** **Technical Support** (ID: 5): Platform and product assistance;
+
+**(b)** **Bug Reports** (ID: 6): Software issues and defect reporting;
+
+**(c)** **Feature Requests** (ID: 7): Enhancement suggestions and new features;
+
+**(d)** **Community Feedback** (ID: 8): General community input and suggestions;
+
+**(e)** **Policy Ideation** (ID: 9): Policy suggestions and governance input;
+
+**(f)** **Accessibility Feedback** (ID: 10): Accessibility barriers and improvements;
+
+**(g)** **Partnership Requests** (ID: 11): Collaboration and partnership proposals;
+
+**(h)** **Legal Notices** (ID: 12): Legal communications and formal notices;
+
+**(i)** **Billing Questions** (ID: 13): Payment and subscription inquiries;
+
+**(j)** **Press Inquiries** (ID: 14): Media and press communications;
+
+**(k)** **Marketing Proposals** (ID: 15): Marketing collaborations and proposals.
+
+### 1.3. Integration with Existing Policies
+
+Forum moderation operates within our comprehensive policy framework:
+
+**(a)** **Content and Moderation Policy**: Primary content standards and enforcement;
+
+**(b)** **Community Code of Conduct**: Universal behavioural expectations;
+
+**(c)** **Community Support Policy**: Guidelines for support interactions;
+
+**(d)** **Privacy Policy**: Handling of sensitive information in forum posts;
+
+**(e)** **Accessibility Policy**: Ensuring forum accessibility for all users.
+
+## 2. FORUM-SPECIFIC MODERATION CONSIDERATIONS
+
+### 2.1. Unique Characteristics of Forum Moderation
+
+#### 2.1.1. Asynchronous Communication
+
+**Key Differences from Real-Time Platforms:**
+- Extended response timeframes are acceptable and expected
+- Conversations develop over days or weeks rather than minutes
+- Users expect more thoughtful, detailed responses
+- Documentation and searchability are primary concerns
+
+#### 2.1.2. Persistent Content
+
+**Long-Term Visibility:**
+- Forum posts remain searchable indefinitely
+- Content serves as knowledge base for future users
+- Higher standards for accuracy and completeness
+- Regular review and updating of outdated information
+
+#### 2.1.3. Structured Support
+
+**Organised Communication:**
+- Clear categorisation enables efficient routing
+- Topic-based organisation aids in knowledge management
+- Threaded discussions maintain context
+- Solution marking helps future users
+
+### 2.2. Forum Moderation Best Practices
+
+#### 2.2.1. Thread Management
+
+**Effective Thread Moderation:**
+- **Title Clarity**: Ensure thread titles accurately describe the issue
+- **Categorisation**: Move threads to appropriate categories when needed
+- **Duplicate Management**: Merge duplicate threads while preserving context
+- **Solution Marking**: Identify and mark solved threads
+- **Pinning**: Pin important announcements or frequently referenced threads
+
+#### 2.2.2. Response Standards
+
+**Quality Expectations:**
+- Comprehensive initial responses that address all aspects
+- Professional tone maintaining community warmth
+- Clear action items or next steps
+- Appropriate escalation when needed
+- Follow-up on unresolved threads
+
+## 3. CATEGORY-SPECIFIC GUIDELINES
+
+### 3.1. Technical Support
+
+**Moderation Focus:**
+- Verify sufficient system information is provided
+- Request clarification on reproduction steps
+- Tag technical team members when appropriate
+- Ensure privacy (no passwords, API keys, etc.)
+- Mark solutions when issues are resolved
+
+### 3.2. Bug Reports
+
+**Moderation Requirements:**
+- Confirm reports include reproduction steps
+- Check for duplicate reports before allowing
+- Apply appropriate priority labels
+- Link to tracking systems when applicable
+- Update thread status as bugs are addressed
+
+### 3.3. Feature Requests
+
+**Management Approach:**
+- Encourage detailed use case descriptions
+- Facilitate community discussion on proposals
+- Consolidate similar requests
+- Communicate feasibility assessments
+- Update on implementation progress
+
+### 3.4. Community Feedback
+
+**Engagement Standards:**
+- Acknowledge all feedback respectfully
+- Encourage constructive criticism
+- Synthesise feedback for leadership review
+- Communicate how feedback influences decisions
+- Create feedback summary reports
+
+### 3.5. Policy Ideation
+
+**Special Considerations:**
+- Ensure proposals align with community values
+- Facilitate inclusive discussion
+- Document consensus and dissent
+- Forward viable proposals to governance team
+- Communicate policy development progress
+
+### 3.6. Accessibility Feedback
+
+**Priority Handling:**
+- Treat accessibility issues with urgency
+- Ensure reports include assistive technology details
+- Coordinate with accessibility team
+- Track resolution progress
+- Verify fixes with reporting users
+
+### 3.7. Partnership Requests
+
+**Professional Standards:**
+- Maintain confidentiality as requested
+- Verify legitimacy of proposals
+- Route to appropriate decision-makers
+- Facilitate initial discussions
+- Document partnership criteria clearly
+
+### 3.8. Legal Notices
+
+**Critical Procedures:**
+- Immediate escalation to legal team
+- Preserve all original content
+- Document receipt timestamps
+- Maintain strict confidentiality
+- Follow legal response protocols
+
+### 3.9. Billing Questions
+
+**Sensitive Information Handling:**
+- Never request payment details in public threads
+- Offer private thread conversion for sensitive matters
+- Verify account ownership before discussing specifics
+- Coordinate with billing team for resolutions
+- Document common issues for FAQ development
+
+### 3.10. Press Inquiries
+
+**Media Relations:**
+- Verify journalist credentials when appropriate
+- Coordinate with communications team
+- Maintain professional brand representation
+- Facilitate interview scheduling
+- Track press engagement metrics
+
+### 3.11. Marketing Proposals
+
+**Evaluation Criteria:**
+- Assess alignment with brand values
+- Check for spam or low-quality proposals
+- Facilitate community input when appropriate
+- Route serious proposals to marketing team
+- Maintain proposal tracking system
+
+## 4. MODERATION TOOLS AND FEATURES
+
+### 4.1. Forum-Specific Tools
+
+#### 4.1.1. Thread Management Tools
+- **Move Thread**: Relocate to appropriate category
+- **Merge Threads**: Combine duplicate discussions
+- **Split Thread**: Separate off-topic discussions
+- **Pin/Unpin**: Control thread visibility priority
+- **Lock Thread**: Prevent further replies when needed
+- **Mark Solution**: Identify resolved issues
+
+#### 4.1.2. User Management Tools
+- **Trust Levels**: Understand user permission tiers
+- **User Notes**: Document moderation history
+- **Warnings**: Issue formal warnings when needed
+- **Suspensions**: Temporary access restrictions
+- **Thread Permissions**: Control individual thread access
+
+### 4.2. Content Moderation Features
+
+#### 4.2.1. Automated Moderation
+- **Spam Filters**: Automatic spam detection
+- **Trust Level Restrictions**: New user limitations
+- **Flag Queue**: Community-reported content review
+- **Word Filters**: Prohibited content blocking
+- **Link Restrictions**: External link moderation
+
+#### 4.2.2. Manual Moderation Actions
+- **Edit Posts**: Correct or redact content
+- **Delete Posts**: Remove policy violations
+- **Hide Posts**: Temporary removal pending review
+- **Restore Posts**: Reinstate incorrectly removed content
+- **Revision History**: Track all content changes
+
+## 5. COMMON SCENARIOS AND RESPONSES
+
+### 5.1. Scenario: Duplicate Bug Report
+
+**Appropriate Response:**
+1. Search for existing reports
+2. Link to original thread
+3. Merge valuable additional information
+4. Close duplicate with explanation
+5. Guide user to original discussion
+
+### 5.2. Scenario: Vague Support Request
+
+**Effective Approach:**
+1. Request specific information needed
+2. Provide template for details
+3. Offer examples of good reports
+4. Remain patient and helpful
+5. Follow up if no response
+
+### 5.3. Scenario: Heated Feature Request Debate
+
+**De-escalation Strategy:**
+1. Remind participants of community standards
+2. Refocus on constructive discussion
+3. Separate technical merit from personal attacks
+4. Issue warnings if necessary
+5. Lock thread if situation escalates
+
+### 5.4. Scenario: Sensitive Information Posted
+
+**Immediate Actions:**
+1. Edit post to remove sensitive data
+2. Private message user about removal
+3. Educate on security best practices
+4. Document incident for patterns
+5. Review similar posts for exposure
+
+## 6. FORUM COMMUNITY BUILDING
+
+### 6.1. Encouraging Participation
+
+**Engagement Strategies:**
+- Welcome new users warmly
+- Recognise helpful community members
+- Create regular discussion topics
+- Showcase community solutions
+- Celebrate milestones and achievements
+
+### 6.2. Knowledge Base Development
+
+**Content Curation:**
+- Identify frequently asked questions
+- Create comprehensive guides
+- Maintain solution database
+- Update outdated information
+- Cross-reference related topics
+
+## 7. METRICS AND REPORTING
+
+### 7.1. Key Performance Indicators
+
+**Forum Health Metrics:**
+- Response time to new threads
+- Resolution rate for support requests
+- User satisfaction indicators
+- Community engagement levels
+- Moderator action frequency
+
+### 7.2. Regular Reporting
+
+**Documentation Requirements:**
+- Weekly moderation summaries
+- Category-specific activity reports
+- Escalation tracking
+- Community feedback synthesis
+- Improvement recommendations
+
+## 8. CONTINUOUS IMPROVEMENT
+
+### 8.1. Feedback Integration
+
+**Process Improvement:**
+- Regular community surveys
+- Moderator experience sharing
+- Policy effectiveness review
+- Tool and feature requests
+- Best practice documentation
+
+### 8.2. Professional Development
+
+**Ongoing Training:**
+- Forum software updates
+- New moderation techniques
+- Community management trends
+- Accessibility improvements
+- Cross-platform coordination
+
+---
+
+*This Forum Moderation Training provides comprehensive guidance for moderating our Support Forum. For questions about forum moderation procedures or to report issues with the forum platform, please contact the Moderation Team Lead through the designated staff channels.*
@@ -1,8 +1,22 @@
-@font-face {
-    font-family: "Vampyr";
-    src: url("https://cdn.nhcarrigan.com/fonts/vampyr.ttf") format("truetype");
+@import url('https://fonts.googleapis.com/css2?family=Kalam:wght@300;400;700&family=Creepster&family=Griffy&family=Henny+Penny&display=swap');
+
+body {
+    font-family: "Kalam", cursive !important;
 }

-* {
-    font-family: "Vampyr", monospace !important;
-}
+h1,
+h2,
+h3,
+h4,
+h5,
+h6 {
+    font-family: "Griffy", cursive !important;
+}
+
+.witchy-accent {
+    font-family: "Creepster", cursive;
+}
+
+.mystical-text {
+    font-family: "Henny Penny", cursive;
+}
@@ -1,13 +1,50 @@
 :root {
-  --primary-color: #8F2447;
-  --background-color: #E1F6F9DC;
-  --sl-color-text-accent: #8F2447;
+  /* Witch color palette */
+  --witch-purple: #2b1b3d;
+  --witch-purple-translucent: hsla(267, 40%, 17%, 0.85);
+  --witch-plum: #44275a;
+  --witch-rose: #a8577e;
+  --witch-mauve: #d4a5c7;
+  --witch-lavender: #e8d5e8;
+  --witch-black: #0a0009;
+  --witch-silver: #c0c0c0;
+  --witch-moon: #f5f5f5;
+  --witch-shadow: rgba(10, 0, 9, 0.7);
+
+  /* Light theme uses lighter colors for background, darker for text */
+  --primary-color: var(--witch-purple);
+  --background-color: var(--witch-lavender) DC;
+  --sl-color-text-accent: var(--witch-purple);
+
+  /* Additional Starlight overrides */
+  --sl-color-gray-1: var(--witch-moon);
+  --sl-color-gray-2: var(--witch-lavender);
+  --sl-color-gray-3: var(--witch-mauve);
+  --sl-color-gray-4: var(--witch-rose);
+  --sl-color-gray-5: var(--witch-plum);
+  --sl-color-gray-6: var(--witch-purple);
+
+  /* Translucent background */
+  --content-bg: rgba(181, 185, 187, 0.85);
+  --content-blur: 8px;
 }

 html[data-theme="dark"] {
-  --primary-color: #E1F6F9;
-  --background-color: #8F2447ee;
-  --sl-color-text-accent: #E1F6F9;
+  /* Dark theme uses darker colors for background, lighter for text */
+
+  .page {
+    --background-color: transparent;
+  }
+  --primary-color: var(--witch-lavender);
+  --sl-color-text-accent: var(--witch-lavender);
+
+  /* Additional Starlight overrides for dark theme */
+  --sl-color-gray-1: var(--witch-purple);
+  --sl-color-gray-2: var(--witch-plum);
+  --sl-color-gray-3: var(--witch-rose);
+  --sl-color-gray-4: var(--witch-mauve);
+  --sl-color-gray-5: var(--witch-lavender);
+  --sl-color-gray-6: var(--witch-moon);
 }

 .main-frame::before {
@@ -33,11 +70,15 @@ html[data-theme="dark"] {
 }

 .sidebar-pane,
-.right-sidebar-panel {
+.right-sidebar {
  background-color: var(--background-color);
  color: var(--primary-color);
 }

+.right-sidebar-panel {
+  color: var(--primary-color);
+}
+
 h1,
 h2,
 h3,
@@ -48,14 +89,31 @@ a {
  color: var(--primary-color) !important;
 }

+.page {
+  background: var(--content-bg);
+  backdrop-filter: var(--content-blur);
+}
+
+html[data-theme="dark"] .page {
+  background: var(--witch-purple-translucent);
+}
+
 a[aria-current="page"] {
  color: var(--background-color) !important;
-  background-color: var(--primary-color) !important;
+  background-color: var(--witch-rose) !important;
+}
+
+html[data-theme="dark"] a[aria-current="page"] {
+  color: var(--witch-moon) !important;
 }

 header {
  color: var(--primary-color) !important;
-  background-color: var(--background-color) !important;
+  background-color: var(--witch-lavender) !important;
+}
+
+html[data-theme="dark"] header {
+  background-color: var(--witch-purple) !important;
 }

 .large {
@@ -67,8 +125,8 @@ header {
 }

 .right-sidebar-panel :where(a):hover {
-  color: var(--background-color) !important;
-  background-color: var(--primary-color) !important;
+  color: var(--witch-moon) !important;
+  background-color: var(--witch-rose) !important;
 }

 footer > div > a,
@@ -77,10 +135,26 @@ footer > div > p {
  color: var(--primary-color) !important;
 }

-starlight-theme-select, starlight-theme-select > label {
+starlight-theme-select,
+starlight-theme-select > label {
  color: var(--primary-color) !important;
 }

+starlight-theme-select select {
+  color: var(--primary-color) !important;
+  background-color: var(--background-color) !important;
+}
+
+starlight-theme-select select option {
+  color: var(--primary-color);
+  background-color: var(--background-color);
+}
+
+html[data-theme="dark"] starlight-theme-select select option {
+  color: var(--witch-purple) !important;
+  background-color: var(--witch-lavender) !important;
+}
+
 .social-icons::after {
  display: none;
 }
@@ -94,13 +168,42 @@ starlight-theme-select, starlight-theme-select > label {
 }

 .pagination-links > a:hover {
-  color: var(--background-color) !important;
-  background-color: var(--primary-color) !important;
+  color: var(--witch-moon) !important;
+  background-color: var(--witch-plum) !important;
 }

 .pagination-links > a:hover > span > .link-title {
-  color: var(--background-color) !important;
-  background-color: var(--primary-color) !important;
+  color: var(--witch-moon) !important;
+  background-color: var(--witch-plum) !important;
+}
+
+.hero .tagline {
+  color: var(--primary-color) !important;
+}
+
+site-search button[data-open-modal] {
+  color: var(--primary-color) !important;
+}
+
+site-search button[data-open-modal] kbd {
+  color: var(--primary-color) !important;
+  background-color: var(--background-color) !important;
+  border-color: var(--primary-color) !important;
+}
+
+#starlight__search {
+  --pagefind-ui-text: var(--primary-color);
+  --pagefind-ui-primary: var(--witch-rose);
+}
+
+#starlight__search input::placeholder {
+  color: var(--primary-color) !important;
+  opacity: 0.8;
+}
+
+.pagefind-ui__result-excerpt {
+  color: var(--primary-color) !important;
+  opacity: 0.9;
 }

 #extra-footer-content {
@@ -2,62 +2,61 @@
 	"$schema": "vscode://schemas/color-theme",
 	"type": "dark",
 	"colors": {
-		"activityBar.background": "#3a0d22",
-		"activityBar.foreground": "#ffb6c1",
-		"activityBarBadge.background": "#ff69b4",
-		"activityBarBadge.foreground": "#000000",
-		"button.background": "#ff69b4",
-		"button.foreground": "#000000",
-		"dropdown.background": "#4a112a",
-		"dropdown.foreground": "#ffb6c1",
-		"editor.background": "#2a0a18",
-		"editor.foreground": "#ffb6c1",
-		"editor.lineHighlightBackground": "#1073cf2d",
-		"editor.lineHighlightBorder": "#9fced11f",
-		"editor.selectionBackground": "#e35a8f",
-		"editor.selectionHighlightBackground": "#e35a8f80",
-		"editor.wordHighlightBackground": "#e35a8f80",
-		"editorCursor.foreground": "#ff69b4",
-		"editorGroupHeader.tabsBackground": "#3a0d22",
-		"editorWhitespace.foreground": "#4a112a",
-		"focusBorder": "#ff69b4",
-		"input.background": "#3a0d22",
-		"input.foreground": "#ffb6c1",
-		"input.placeholderForeground": "#e35a8f",
-		"list.activeSelectionBackground": "#4a112a",
-		"list.activeSelectionForeground": "#ffb6c1",
-		"list.hoverBackground": "#3a0d22",
-		"list.hoverForeground": "#ffb6c1",
-		"sideBar.background": "#3a0d22",
-		"sideBar.foreground": "#ffb6c1",
-		"sideBarTitle.foreground": "#ff69b4",
-		"statusBar.background": "#4a112a",
-		"statusBar.foreground": "#ffb6c1",
-		"statusBar.noFolderBackground": "#2a0a18",
-		"tab.activeBackground": "#3a0d22",
-		"tab.activeForeground": "#ffb6c1",
-		"tab.inactiveBackground": "#4a112a",
-		"tab.inactiveForeground": "#e35a8f",
-		"terminal.ansiBlack": "#4a112a",
-		"terminal.ansiBlue": "#c96385",
-		"terminal.ansiBrightBlack": "#3a0d22",
-		"terminal.ansiBrightBlue": "#d87093",
-		"terminal.ansiBrightCyan": "#ffafc5",
-		"terminal.ansiBrightGreen": "#ff77a8",
-		"terminal.ansiBrightMagenta": "#ff85a2",
-		"terminal.ansiBrightRed": "#ff1493",
-		"terminal.ansiBrightWhite": "#fff5f7",
-		"terminal.ansiBrightYellow": "#ffb6c1",
-		"terminal.ansiCyan": "#ff9aac",
-		"terminal.ansiGreen": "#e35a8f",
-		"terminal.ansiMagenta": "#e35a8f",
-		"terminal.ansiRed": "#ff69b4",
-		"terminal.ansiWhite": "#ffd1dc",
-		"terminal.ansiYellow": "#d45a88",
-		"terminal.background": "#2a0a18",
-		"terminal.foreground": "#ffb6c1",
-		"titleBar.activeBackground": "#4a112a",
-		"titleBar.activeForeground": "#ffb6c1"
+		"activityBar.background": "#150a1e",
+		"activityBar.foreground": "#e8d5e8",
+		"activityBarBadge.background": "#a8577e",
+		"activityBarBadge.foreground": "#f5f5f5",
+		"button.background": "#44275a",
+		"button.foreground": "#e8d5e8",
+		"dropdown.background": "#2b1b3d",
+		"dropdown.foreground": "#e8d5e8",
+		"editor.background": "#0a0009",
+		"editor.foreground": "#e8d5e8",
+		"editor.lineHighlightBackground": "#2b1b3d",
+		"editor.selectionBackground": "#a8577e",
+		"editor.selectionHighlightBackground": "#a8577e50",
+		"editor.wordHighlightBackground": "#a8577e40",
+		"editorCursor.foreground": "#a8577e",
+		"editorGroupHeader.tabsBackground": "#150a1e",
+		"editorWhitespace.foreground": "#44275a",
+		"focusBorder": "#a8577e",
+		"input.background": "#150a1e",
+		"input.foreground": "#e8d5e8",
+		"input.placeholderForeground": "#d4a5c7",
+		"list.activeSelectionBackground": "#44275a",
+		"list.activeSelectionForeground": "#e8d5e8",
+		"list.hoverBackground": "#2b1b3d",
+		"list.hoverForeground": "#e8d5e8",
+		"sideBar.background": "#150a1e",
+		"sideBar.foreground": "#e8d5e8",
+		"sideBarTitle.foreground": "#d4a5c7",
+		"statusBar.background": "#44275a",
+		"statusBar.foreground": "#e8d5e8",
+		"statusBar.noFolderBackground": "#0a0009",
+		"tab.activeBackground": "#2b1b3d",
+		"tab.activeForeground": "#e8d5e8",
+		"tab.inactiveBackground": "#150a1e",
+		"tab.inactiveForeground": "#d4a5c7",
+		"terminal.ansiBlack": "#2b1b3d",
+		"terminal.ansiBlue": "#7b5ea8",
+		"terminal.ansiBrightBlack": "#44275a",
+		"terminal.ansiBrightBlue": "#9b7ec8",
+		"terminal.ansiBrightCyan": "#d0b8e8",
+		"terminal.ansiBrightGreen": "#a898c0",
+		"terminal.ansiBrightMagenta": "#d4a5c7",
+		"terminal.ansiBrightRed": "#c96b8e",
+		"terminal.ansiBrightWhite": "#f5f5f5",
+		"terminal.ansiBrightYellow": "#e8d5e8",
+		"terminal.ansiCyan": "#b8a0d0",
+		"terminal.ansiGreen": "#8a7a9e",
+		"terminal.ansiMagenta": "#a8577e",
+		"terminal.ansiRed": "#a8577e",
+		"terminal.ansiWhite": "#d4a5c7",
+		"terminal.ansiYellow": "#d4a5c7",
+		"terminal.background": "#0a0009",
+		"terminal.foreground": "#e8d5e8",
+		"titleBar.activeBackground": "#2b1b3d",
+		"titleBar.activeForeground": "#e8d5e8"
 	},
 	"tokenColors": [
 		{
@@ -66,7 +65,7 @@
 				"punctuation.definition.comment"
 			],
 			"settings": {
-				"foreground": "#E5A3B5",
+				"foreground": "#7A5A8A",
 				"fontStyle": "italic"
 			}
 		},
@@ -81,7 +80,7 @@
 				"constant.other.symbol"
 			],
 			"settings": {
-				"foreground": "#FF69B4"
+				"foreground": "#D4A5C7"
 			}
 		},
 		{
@@ -93,7 +92,7 @@
 				"support.constant"
 			],
 			"settings": {
-				"foreground": "#C96385"
+				"foreground": "#C88FA8"
 			}
 		},
 		{
@@ -105,7 +104,7 @@
 				"variable.object.property"
 			],
 			"settings": {
-				"foreground": "#D87093"
+				"foreground": "#E8D5E8"
 			}
 		},
 		{
@@ -119,7 +118,7 @@
 				"punctuation.decorator"
 			],
 			"settings": {
-				"foreground": "#E35A8F"
+				"foreground": "#A8577E"
 			}
 		},
 		{
@@ -132,7 +131,7 @@
 				"meta.function.dart"
 			],
 			"settings": {
-				"foreground": "#D45A88"
+				"foreground": "#C070A0"
 			}
 		},
 		{
@@ -149,7 +148,7 @@
 				"meta.return-type"
 			],
 			"settings": {
-				"foreground": "#FF77A8",
+				"foreground": "#D4A5C7",
 				"fontStyle": "bold"
 			}
 		},
@@ -160,7 +159,7 @@
 				"punctuation.definition.annotation"
 			],
 			"settings": {
-				"foreground": "#C96385"
+				"foreground": "#9B5878"
 			}
 		},
 		{
@@ -169,7 +168,7 @@
 				"punctuation.definition.tag"
 			],
 			"settings": {
-				"foreground": "#E35A8F"
+				"foreground": "#A8577E"
 			}
 		},
 		{
@@ -181,7 +180,7 @@
 				"entity.other.attribute-name.class"
 			],
 			"settings": {
-				"foreground": "#FF77A8"
+				"foreground": "#D4A5C7"
 			}
 		},
 		{
@@ -194,7 +193,7 @@
 				"support.type.primitive.dart"
 			],
 			"settings": {
-				"foreground": "#FF77A8"
+				"foreground": "#D4A5C7"
 			}
 		},
 		{
@@ -203,7 +202,7 @@
 				"constant.character.escape.regex"
 			],
 			"settings": {
-				"foreground": "#FF69B4"
+				"foreground": "#D4A5C7"
 			}
 		},
 		{
@@ -212,7 +211,7 @@
 				"entity.name.section"
 			],
 			"settings": {
-				"foreground": "#D45A88",
+				"foreground": "#A8577E",
 				"fontStyle": "bold"
 			}
 		},
@@ -239,7 +238,7 @@
 				"markup.raw"
 			],
 			"settings": {
-				"foreground": "#FF69B4"
+				"foreground": "#D4A5C7"
 			}
 		},
 		{
@@ -248,7 +247,7 @@
 				"support.type.property-name.jsonc"
 			],
 			"settings": {
-				"foreground": "#FF77A8"
+				"foreground": "#D4A5C7"
 			}
 		},
 		{
@@ -262,7 +261,7 @@
 				"keyword.operator.logical"
 			],
 			"settings": {
-				"foreground": "#E35A8F"
+				"foreground": "#CF8FAE"
 			}
 		},
 		{
@@ -272,7 +271,7 @@
 				"meta.template.expression"
 			],
 			"settings": {
-				"foreground": "#D87093"
+				"foreground": "#E8D5E8"
 			}
 		},
 		{
@@ -283,7 +282,7 @@
 				"variable.other.object.property"
 			],
 			"settings": {
-				"foreground": "#FF77A8"
+				"foreground": "#D4A5C7"
 			}
 		},
 		{
@@ -293,7 +292,7 @@
 				"support.variable.object.node"
 			],
 			"settings": {
-				"foreground": "#FF77A8"
+				"foreground": "#D4A5C7"
 			}
 		},
 		{
@@ -303,7 +302,7 @@
 				"source.rust entity.name.type.struct.rust"
 			],
 			"settings": {
-				"foreground": "#FF77A8"
+				"foreground": "#D4A5C7"
 			}
 		},
 		{
@@ -313,7 +312,7 @@
 				"source.rust keyword.operator.logical"
 			],
 			"settings": {
-				"foreground": "#E35A8F"
+				"foreground": "#CF8FAE"
 			}
 		},
 		{
@@ -322,7 +321,7 @@
 				"source.python support.function.builtin.python"
 			],
 			"settings": {
-				"foreground": "#D45A88"
+				"foreground": "#C070A0"
 			}
 		},
 		{
@@ -331,7 +330,7 @@
 				"source.cs storage.type.cs"
 			],
 			"settings": {
-				"foreground": "#FF77A8"
+				"foreground": "#D4A5C7"
 			}
 		},
 		{
@@ -340,7 +339,7 @@
 				"source.dart support.type.dart"
 			],
 			"settings": {
-				"foreground": "#FF77A8"
+				"foreground": "#D4A5C7"
 			}
 		},
 		{
@@ -350,7 +349,7 @@
 				"source.prisma keyword.type"
 			],
 			"settings": {
-				"foreground": "#E35A8F"
+				"foreground": "#A8577E"
 			}
 		},
 		{
@@ -359,7 +358,7 @@
 				"source.graphql constant.character"
 			],
 			"settings": {
-				"foreground": "#FF77A8"
+				"foreground": "#D4A5C7"
 			}
 		},
 		{
@@ -368,7 +367,7 @@
 				"source.sql storage.type"
 			],
 			"settings": {
-				"foreground": "#E35A8F"
+				"foreground": "#A8577E"
 			}
 		},
 		{
@@ -378,7 +377,7 @@
 				"meta.embedded.block.jsx"
 			],
 			"settings": {
-				"foreground": "#D87093"
+				"foreground": "#E8D5E8"
 			}
 		},
 		{
@@ -388,13 +387,101 @@
 				"meta.decorator.angular"
 			],
 			"settings": {
-				"foreground": "#C96385"
+				"foreground": "#9B5878"
 			}
 		},
 		{
-			"scope": "ref.matchtext",
+			"scope": [
+				"entity.name.tag.yaml",
+				"string.unquoted.plain.out.yaml"
+			],
 			"settings": {
-				"foreground": "#FFFFFF"
+				"foreground": "#D4A5C7"
+			}
+		},
+		{
+			"scope": [
+				"support.type.property-name.toml",
+				"entity.name.tag.toml"
+			],
+			"settings": {
+				"foreground": "#D4A5C7"
+			}
+		},
+		{
+			"scope": [
+				"markup.underline.link",
+				"string.other.link.title.markdown",
+				"meta.link.inline.markdown"
+			],
+			"settings": {
+				"foreground": "#A8577E"
+			}
+		},
+		{
+			"scope": [
+				"markup.quote"
+			],
+			"settings": {
+				"foreground": "#7A5A8A",
+				"fontStyle": "italic"
+			}
+		},
+		{
+			"scope": [
+				"punctuation.definition.list.begin.markdown",
+				"beginning.punctuation.definition.list.markdown"
+			],
+			"settings": {
+				"foreground": "#A8577E"
+			}
+		},
+		{
+			"scope": [
+				"variable.css",
+				"variable.other.custom-property.css",
+				"support.type.custom-property.css"
+			],
+			"settings": {
+				"foreground": "#CF8FAE"
+			}
+		},
+		{
+			"scope": [
+				"support.macro.rust",
+				"entity.name.function.macro.rust",
+				"meta.macro.rust entity.name.function.rust"
+			],
+			"settings": {
+				"foreground": "#C070A0"
+			}
+		},
+		{
+			"scope": [
+				"storage.modifier.lifetime.rust",
+				"entity.name.lifetime.rust",
+				"punctuation.definition.lifetime.rust"
+			],
+			"settings": {
+				"foreground": "#9B5878"
+			}
+		},
+		{
+			"scope": [
+				"entity.name.package.go"
+			],
+			"settings": {
+				"foreground": "#C88FA8"
+			}
+		},
+		{
+			"scope": [
+				"entity.name.package.java",
+				"support.other.package.java",
+				"entity.name.package.kotlin"
+			],
+			"settings": {
+				"foreground": "#C88FA8"
 			}
 		},
 		{
@@ -2,62 +2,61 @@
 	"$schema": "vscode://schemas/color-theme",
 	"type": "light",
 	"colors": {
-		"activityBar.background": "#ffd6e0",
-		"activityBar.foreground": "#d87093",
-		"activityBarBadge.background": "#ff69b4",
-		"activityBarBadge.foreground": "#ffffff",
-		"button.background": "#ff69b4",
-		"button.foreground": "#ffffff",
-		"dropdown.background": "#fff0f5",
-		"dropdown.foreground": "#d87093",
-		"editor.background": "#ffefef",
-		"editor.foreground": "#d87093",
-		"editor.lineHighlightBackground": "#1073cf2d",
-		"editor.lineHighlightBorder": "#9fced11f",
-		"editor.selectionBackground": "#ffb6c1",
-		"editor.selectionHighlightBackground": "#ffb6c180",
-		"editor.wordHighlightBackground": "#ffb6c180",
-		"editorCursor.foreground": "#ff69b4",
-		"editorGroupHeader.tabsBackground": "#ffe4e8",
-		"editorWhitespace.foreground": "#ffe4e8",
-		"focusBorder": "#ff69b4",
-		"input.background": "#fff0f5",
-		"input.foreground": "#d87093",
-		"input.placeholderForeground": "#ff77a8",
-		"list.activeSelectionBackground": "#ffefef",
-		"list.activeSelectionForeground": "#d87093",
-		"list.hoverBackground": "#fff0f5",
-		"list.hoverForeground": "#d87093",
-		"sideBar.background": "#fff0f5",
-		"sideBar.foreground": "#d87093",
-		"sideBarTitle.foreground": "#ff69b4",
-		"statusBar.background": "#ffd6e0",
-		"statusBar.foreground": "#d87093",
-		"statusBar.noFolderBackground": "#ffefef",
-		"tab.activeBackground": "#ffefef",
-		"tab.activeForeground": "#d87093",
-		"tab.inactiveBackground": "#ffd6e0",
-		"tab.inactiveForeground": "#ff77a8",
-		"terminal.ansiBlack": "#ffe4e8",
-		"terminal.ansiBlue": "#db7093",
-		"terminal.ansiBrightBlack": "#ffefef",
-		"terminal.ansiBrightBlue": "#f08080",
-		"terminal.ansiBrightCyan": "#ffc0cb",
-		"terminal.ansiBrightGreen": "#ff77a8",
-		"terminal.ansiBrightMagenta": "#ff9aac",
-		"terminal.ansiBrightRed": "#ff0066",
-		"terminal.ansiBrightWhite": "#fff5f7",
-		"terminal.ansiBrightYellow": "#ffa6c9",
-		"terminal.ansiCyan": "#ffafc5",
-		"terminal.ansiGreen": "#ff69b4",
-		"terminal.ansiMagenta": "#ff85a2",
-		"terminal.ansiRed": "#ff1493",
-		"terminal.ansiWhite": "#ffd1dc",
-		"terminal.ansiYellow": "#ffb6c1",
-		"terminal.background": "#ffefef",
-		"terminal.foreground": "#d87093",
-		"titleBar.activeBackground": "#ffd6e0",
-    "titleBar.activeForeground": "#d87093"
+		"activityBar.background": "#e8d5e8",
+		"activityBar.foreground": "#2b1b3d",
+		"activityBarBadge.background": "#a8577e",
+		"activityBarBadge.foreground": "#f5f5f5",
+		"button.background": "#a8577e",
+		"button.foreground": "#f5f5f5",
+		"dropdown.background": "#e8d5e8",
+		"dropdown.foreground": "#2b1b3d",
+		"editor.background": "#f5f5f5",
+		"editor.foreground": "#2b1b3d",
+		"editor.lineHighlightBackground": "#d4a5c740",
+		"editor.selectionBackground": "#d4a5c7",
+		"editor.selectionHighlightBackground": "#d4a5c750",
+		"editor.wordHighlightBackground": "#d4a5c740",
+		"editorCursor.foreground": "#a8577e",
+		"editorGroupHeader.tabsBackground": "#e8d5e8",
+		"editorWhitespace.foreground": "#d4a5c7",
+		"focusBorder": "#a8577e",
+		"input.background": "#f5f5f5",
+		"input.foreground": "#2b1b3d",
+		"input.placeholderForeground": "#a8577e",
+		"list.activeSelectionBackground": "#d4a5c7",
+		"list.activeSelectionForeground": "#2b1b3d",
+		"list.hoverBackground": "#e8d5e8",
+		"list.hoverForeground": "#2b1b3d",
+		"sideBar.background": "#e8d5e8",
+		"sideBar.foreground": "#2b1b3d",
+		"sideBarTitle.foreground": "#a8577e",
+		"statusBar.background": "#a8577e",
+		"statusBar.foreground": "#f5f5f5",
+		"statusBar.noFolderBackground": "#f5f5f5",
+		"tab.activeBackground": "#f5f5f5",
+		"tab.activeForeground": "#2b1b3d",
+		"tab.inactiveBackground": "#e8d5e8",
+		"tab.inactiveForeground": "#44275a",
+		"terminal.ansiBlack": "#2b1b3d",
+		"terminal.ansiBlue": "#7b5ea8",
+		"terminal.ansiBrightBlack": "#44275a",
+		"terminal.ansiBrightBlue": "#9b7ec8",
+		"terminal.ansiBrightCyan": "#d0b8e8",
+		"terminal.ansiBrightGreen": "#a898c0",
+		"terminal.ansiBrightMagenta": "#d4a5c7",
+		"terminal.ansiBrightRed": "#c96b8e",
+		"terminal.ansiBrightWhite": "#f5f5f5",
+		"terminal.ansiBrightYellow": "#e8d5e8",
+		"terminal.ansiCyan": "#b8a0d0",
+		"terminal.ansiGreen": "#8a7a9e",
+		"terminal.ansiMagenta": "#a8577e",
+		"terminal.ansiRed": "#a8577e",
+		"terminal.ansiWhite": "#d4a5c7",
+		"terminal.ansiYellow": "#d4a5c7",
+		"terminal.background": "#f5f5f5",
+		"terminal.foreground": "#2b1b3d",
+		"titleBar.activeBackground": "#e8d5e8",
+		"titleBar.activeForeground": "#2b1b3d"
 	},
 	"tokenColors": [
 		{
@@ -66,7 +65,7 @@
 				"punctuation.definition.comment"
 			],
 			"settings": {
-				"foreground": "#E5A3B5",
+				"foreground": "#7A5A8A",
 				"fontStyle": "italic"
 			}
 		},
@@ -81,7 +80,7 @@
 				"constant.other.symbol"
 			],
 			"settings": {
-				"foreground": "#FF69B4"
+				"foreground": "#9B5878"
 			}
 		},
 		{
@@ -93,7 +92,7 @@
 				"support.constant"
 			],
 			"settings": {
-				"foreground": "#C96385"
+				"foreground": "#9B5878"
 			}
 		},
 		{
@@ -105,7 +104,7 @@
 				"variable.object.property"
 			],
 			"settings": {
-				"foreground": "#D87093"
+				"foreground": "#44275a"
 			}
 		},
 		{
@@ -119,7 +118,7 @@
 				"punctuation.decorator"
 			],
 			"settings": {
-				"foreground": "#E35A8F"
+				"foreground": "#A8577E"
 			}
 		},
 		{
@@ -132,7 +131,7 @@
 				"meta.function.dart"
 			],
 			"settings": {
-				"foreground": "#D45A88"
+				"foreground": "#C070A0"
 			}
 		},
 		{
@@ -149,7 +148,7 @@
 				"meta.return-type"
 			],
 			"settings": {
-				"foreground": "#FF77A8",
+				"foreground": "#9B5878",
 				"fontStyle": "bold"
 			}
 		},
@@ -160,7 +159,7 @@
 				"punctuation.definition.annotation"
 			],
 			"settings": {
-				"foreground": "#C96385"
+				"foreground": "#9B5878"
 			}
 		},
 		{
@@ -169,7 +168,7 @@
 				"punctuation.definition.tag"
 			],
 			"settings": {
-				"foreground": "#E35A8F"
+				"foreground": "#A8577E"
 			}
 		},
 		{
@@ -181,7 +180,7 @@
 				"entity.other.attribute-name.class"
 			],
 			"settings": {
-				"foreground": "#FF77A8"
+				"foreground": "#9B5878"
 			}
 		},
 		{
@@ -194,7 +193,7 @@
 				"support.type.primitive.dart"
 			],
 			"settings": {
-				"foreground": "#FF77A8"
+				"foreground": "#9B5878"
 			}
 		},
 		{
@@ -203,7 +202,7 @@
 				"constant.character.escape.regex"
 			],
 			"settings": {
-				"foreground": "#FF69B4"
+				"foreground": "#9B5878"
 			}
 		},
 		{
@@ -212,7 +211,7 @@
 				"entity.name.section"
 			],
 			"settings": {
-				"foreground": "#D45A88",
+				"foreground": "#A8577E",
 				"fontStyle": "bold"
 			}
 		},
@@ -239,7 +238,7 @@
 				"markup.raw"
 			],
 			"settings": {
-				"foreground": "#FF69B4"
+				"foreground": "#9B5878"
 			}
 		},
 		{
@@ -248,7 +247,7 @@
 				"support.type.property-name.jsonc"
 			],
 			"settings": {
-				"foreground": "#FF77A8"
+				"foreground": "#9B5878"
 			}
 		},
 		{
@@ -262,7 +261,7 @@
 				"keyword.operator.logical"
 			],
 			"settings": {
-				"foreground": "#E35A8F"
+				"foreground": "#A8577E"
 			}
 		},
 		{
@@ -272,7 +271,7 @@
 				"meta.template.expression"
 			],
 			"settings": {
-				"foreground": "#D87093"
+				"foreground": "#44275a"
 			}
 		},
 		{
@@ -283,7 +282,7 @@
 				"variable.other.object.property"
 			],
 			"settings": {
-				"foreground": "#FF77A8"
+				"foreground": "#9B5878"
 			}
 		},
 		{
@@ -293,7 +292,7 @@
 				"support.variable.object.node"
 			],
 			"settings": {
-				"foreground": "#FF77A8"
+				"foreground": "#9B5878"
 			}
 		},
 		{
@@ -303,7 +302,7 @@
 				"source.rust entity.name.type.struct.rust"
 			],
 			"settings": {
-				"foreground": "#FF77A8"
+				"foreground": "#9B5878"
 			}
 		},
 		{
@@ -313,7 +312,7 @@
 				"source.rust keyword.operator.logical"
 			],
 			"settings": {
-				"foreground": "#E35A8F"
+				"foreground": "#A8577E"
 			}
 		},
 		{
@@ -322,7 +321,7 @@
 				"source.python support.function.builtin.python"
 			],
 			"settings": {
-				"foreground": "#D45A88"
+				"foreground": "#C070A0"
 			}
 		},
 		{
@@ -331,7 +330,7 @@
 				"source.cs storage.type.cs"
 			],
 			"settings": {
-				"foreground": "#FF77A8"
+				"foreground": "#9B5878"
 			}
 		},
 		{
@@ -340,7 +339,7 @@
 				"source.dart support.type.dart"
 			],
 			"settings": {
-				"foreground": "#FF77A8"
+				"foreground": "#9B5878"
 			}
 		},
 		{
@@ -350,7 +349,7 @@
 				"source.prisma keyword.type"
 			],
 			"settings": {
-				"foreground": "#E35A8F"
+				"foreground": "#A8577E"
 			}
 		},
 		{
@@ -359,7 +358,7 @@
 				"source.graphql constant.character"
 			],
 			"settings": {
-				"foreground": "#FF77A8"
+				"foreground": "#9B5878"
 			}
 		},
 		{
@@ -368,7 +367,7 @@
 				"source.sql storage.type"
 			],
 			"settings": {
-				"foreground": "#E35A8F"
+				"foreground": "#A8577E"
 			}
 		},
 		{
@@ -378,7 +377,7 @@
 				"meta.embedded.block.jsx"
 			],
 			"settings": {
-				"foreground": "#D87093"
+				"foreground": "#44275a"
 			}
 		},
 		{
@@ -388,13 +387,107 @@
 				"meta.decorator.angular"
 			],
 			"settings": {
-				"foreground": "#C96385"
+				"foreground": "#9B5878"
+			}
+		},
+		{
+			"scope": [
+				"entity.name.tag.yaml",
+				"string.unquoted.plain.out.yaml"
+			],
+			"settings": {
+				"foreground": "#9B5878"
+			}
+		},
+		{
+			"scope": [
+				"support.type.property-name.toml",
+				"entity.name.tag.toml"
+			],
+			"settings": {
+				"foreground": "#9B5878"
+			}
+		},
+		{
+			"scope": [
+				"markup.underline.link",
+				"string.other.link.title.markdown",
+				"meta.link.inline.markdown"
+			],
+			"settings": {
+				"foreground": "#A8577E"
+			}
+		},
+		{
+			"scope": [
+				"markup.quote"
+			],
+			"settings": {
+				"foreground": "#7A5A8A",
+				"fontStyle": "italic"
+			}
+		},
+		{
+			"scope": [
+				"punctuation.definition.list.begin.markdown",
+				"beginning.punctuation.definition.list.markdown"
+			],
+			"settings": {
+				"foreground": "#A8577E"
+			}
+		},
+		{
+			"scope": [
+				"variable.css",
+				"variable.other.custom-property.css",
+				"support.type.custom-property.css"
+			],
+			"settings": {
+				"foreground": "#A8577E"
+			}
+		},
+		{
+			"scope": [
+				"support.macro.rust",
+				"entity.name.function.macro.rust",
+				"meta.macro.rust entity.name.function.rust"
+			],
+			"settings": {
+				"foreground": "#C070A0"
+			}
+		},
+		{
+			"scope": [
+				"storage.modifier.lifetime.rust",
+				"entity.name.lifetime.rust",
+				"punctuation.definition.lifetime.rust"
+			],
+			"settings": {
+				"foreground": "#9B5878"
+			}
+		},
+		{
+			"scope": [
+				"entity.name.package.go"
+			],
+			"settings": {
+				"foreground": "#9B5878"
+			}
+		},
+		{
+			"scope": [
+				"entity.name.package.java",
+				"support.other.package.java",
+				"entity.name.package.kotlin"
+			],
+			"settings": {
+				"foreground": "#9B5878"
 			}
 		},
 		{
 			"scope": "token.info-token",
 			"settings": {
-				"foreground": "#316BCD"
+				"foreground": "#6796E6"
 			}
 		},
 		{
@@ -406,13 +499,13 @@
 		{
 			"scope": "token.error-token",
 			"settings": {
-				"foreground": "#CD3131"
+				"foreground": "#F44747"
 			}
 		},
 		{
 			"scope": "token.debug-token",
 			"settings": {
-				"foreground": "#800080"
+				"foreground": "#B267E6"
 			}
 		}
 	]
Author	SHA1	Message	Date
ilenia	59741cc61e	fix: rollback vite to 6.1.0 and pin nanoid for trust policy Node.js CI / CI (pull_request) Failing after 29s Details Security Scan and Upload / Security & DefectDojo Upload (pull_request) Successful in 1m17s Details	2026-06-30 20:15:26 +02:00
hikari	c8f7f701b4	docs(mentorship): add programme sunset callout to all pages (#32 ) Node.js CI / CI (push) Successful in 59s Details Security Scan and Upload / Security & DefectDojo Upload (push) Successful in 1m29s Details ## Summary The open Mentorship Programme is being closed. This PR adds a `:::caution[Programme Sunset]` aside to the top of every page under `src/content/docs/mentorship/` (and the nested `resources/` subdirectory) so anyone landing on these pages immediately understands the current state of the programme. The callout: - States that the open programme has been sunset and is no longer accepting new participants - Notes that the pages remain available as reference material - Describes the new private, invite-only personalised development programme - Clarifies that there is no application process - Directs interested readers to the Discord community as the route to being noticed for an invite ## Files changed - 11 main mentorship pages (`00-faq` through `10-graduation`) - 10 resource pages under `mentorship/resources/` - 21 files total, 168 insertions, 0 deletions ## Test plan - [x] `pnpm lint` passes (0 cspell issues across 176 files) - [x] `pnpm build` succeeds (177 pages built, no Starlight aside errors) - [x] Spot-checked rendered placement on `00-faq.md` and `resources/career-prep.md` - [ ] Visual confirmation in deployed preview ## Notes While working on this, I noticed one pre-existing em-dash in `mentorship/07-writing-code.md` (line 184, in the body content, not the callout). Out of scope for this PR but worth a future cleanup pass to bring those legacy docs in line with your tone guide. Reviewed-on: #32 Co-authored-by: Hikari <hikari@nhcarrigan.com> Co-committed-by: Hikari <hikari@nhcarrigan.com>	2026-05-26 11:20:55 -07:00
hikari	3789116d1f	style: apply style guide fonts, colours, and readability fixes (#31 ) Node.js CI / CI (push) Successful in 1m52s Details Security Scan and Upload / Security & DefectDojo Upload (push) Successful in 3m13s Details ## Summary - Replaces custom "Vampyr" font with style guide fonts (Griffy, Kalam, Creepster, Henny Penny) - Fixes illegible tagline, search placeholder, search results, shortcut badge, theme dropdown, and active sidebar item across light and dark modes - Applies witchy code themes for light and dark mode - Fixes invalid `env` language in code blocks (replaced with `sh`) - Fixes invalid `message` aside icon in contact page (replaced with `star`) ✨ This PR was created with help from Hikari~ 🌸 Co-authored-by: Naomi Carrigan <commits@nhcarrigan.com> Reviewed-on: #31 Co-authored-by: Hikari <hikari@nhcarrigan.com> Co-committed-by: Hikari <hikari@nhcarrigan.com>	2026-03-03 17:54:53 -08:00
hikari	6bfcd6b98b	chore: replace .npmrc with pnpm-workspace.yaml Node.js CI / CI (push) Successful in 1m5s Details Security Scan and Upload / Security & DefectDojo Upload (push) Successful in 1m28s Details	2026-03-02 16:26:38 -08:00
hikari	7ecdac40db	docs(mentorship): update Discord channel names Node.js CI / CI (push) Successful in 59s Details Security Scan and Upload / Security & DefectDojo Upload (push) Successful in 1m5s Details Renames mentorship programme channels to reflect current server structure: - #mentee-chat → #⚗️│alchemy-lab - #goal-setting → #🎯│oaths - #project-plan → #🗺️│quest-board	2026-03-02 15:44:17 -08:00
hikari	7f311fd7b5	chore: migrate personal reference pages to private notes Node.js CI / CI (push) Successful in 59s Details Security Scan and Upload / Security & DefectDojo Upload (push) Successful in 1m4s Details Removes templates, music, AI prompts, server setup, and VTubing setup from the public docs site. These pages have been migrated to Naomi's private SilverBullet notes instance where they belong. The server setup doc has been rewritten as a personal runbook rather than staff-facing documentation.	2026-03-02 13:18:01 -08:00
hikari	b6b3ef01ad	docs(mentorship): clarify style guide and IP ownership for flagship projects (#30 ) Node.js CI / CI (push) Successful in 56s Details Security Scan and Upload / Security & DefectDojo Upload (push) Successful in 1m55s Details ## Summary Mentorship programme participants were confused about whether NHCarrigan's style guide (including copyright headers and Naomi's Public Licence) applied to their own flagship projects. This PR adds clear clarifications in the relevant docs: - `dev/style.md`: Tightened scope language to "NHCarrigan-maintained repositories" and added an explicit note for mentorship participants that the style guide (including Section 2.1 copyright/licensing) does not apply to their flagship projects - `mentorship/07-writing-code.md`: Updated the scope note to remove Style Guide and Contributor Covenant requirements; replaced with a clear statement that participants must follow the [Community Code of Conduct](/community/coc) and [Community Guidelines](/community/guide), and must not use their repository for illegal, harmful, discriminatory, or bigoted content; added Section 7.3 explicitly stating that NHCarrigan makes no IP claim over flagship projects and participants are free to choose their own licence and style standards ✨ This PR was created with help from Hikari~ 🌸 Reviewed-on: #30 Co-authored-by: Hikari <hikari@nhcarrigan.com> Co-committed-by: Hikari <hikari@nhcarrigan.com>	2026-02-27 14:24:16 -08:00
rain	8a811b87c3	fix(readable-background): add a translucent background to main content (#23 ) Node.js CI / CI (push) Successful in 58s Details Security Scan and Upload / Security & DefectDojo Upload (push) Successful in 2m5s Details ### Explanation This makes the main content area readable. ![Screenshot 2026-02-03 at 12.10.01 PM.png](/attachments/5103926c-17a1-49b5-8594-2f985b6bb23d) ### Issue 22 ### Attestations - [x] I have read and agree to the [Code of Conduct](https://docs.nhcarrigan.com/community/coc/) - [x] I have read and agree to the [Community Guidelines](https://docs.nhcarrigan.com/community/guide/). - [x] My contribution complies with the [Contributor Covenant](https://docs.nhcarrigan.com/dev/covenant/). ### Dependencies - [x] I have pinned the dependencies to a specific patch version. ### Style - [x] I have run the linter and resolved any errors. - [x] My pull request uses an appropriate title, matching the conventional commit standards. - [x] My scope of feat/fix/chore/etc. correctly matches the nature of changes in my pull request. ### Tests - [x] My contribution adds new code, and I have added tests to cover it. - [x] My contribution modifies existing code, and I have updated the tests to reflect these changes. - [x] All new and existing tests pass locally with my changes. - [x] Code coverage remains at or above the configured threshold. ### Documentation I have made the following PR to update the documentation site by adding a translucent background to main content sections to improve text readability against the background artwork. ### Versioning Minor - My pull request introduces a new non-breaking feature. Co-authored-by: Rain <rainkalugdan@gmail.com> Reviewed-on: #23 Co-authored-by: rain <rain@nhcarrigan.com> Co-committed-by: rain <rain@nhcarrigan.com>	2026-02-06 16:46:52 -08:00
naomi	ddaeb72638	feat: new theme Node.js CI / CI (push) Successful in 1m40s Details Security Scan and Upload / Security & DefectDojo Upload (push) Successful in 1m46s Details	2026-01-29 17:35:10 -08:00
naomi	0ece797eee	feat: add documentation for our support forum (#21 ) Security Scan and Upload / Security & DefectDojo Upload (push) Successful in 1m45s Details Node.js CI / CI (push) Successful in 1m50s Details ### Explanation _No response_ ### Issue _No response_ ### Attestations - [ ] I have read and agree to the [Code of Conduct](https://docs.nhcarrigan.com/community/coc/) - [ ] I have read and agree to the [Community Guidelines](https://docs.nhcarrigan.com/community/guide/). - [ ] My contribution complies with the [Contributor Covenant](https://docs.nhcarrigan.com/dev/covenant/). ### Dependencies - [ ] I have pinned the dependencies to a specific patch version. ### Style - [ ] I have run the linter and resolved any errors. - [ ] My pull request uses an appropriate title, matching the conventional commit standards. - [ ] My scope of feat/fix/chore/etc. correctly matches the nature of changes in my pull request. ### Tests - [ ] My contribution adds new code, and I have added tests to cover it. - [ ] My contribution modifies existing code, and I have updated the tests to reflect these changes. - [ ] All new and existing tests pass locally with my changes. - [ ] Code coverage remains at or above the configured threshold. ### Documentation _No response_ ### Versioning _No response_ Reviewed-on: #21 Co-authored-by: Naomi Carrigan <commits@nhcarrigan.com> Co-committed-by: Naomi Carrigan <commits@nhcarrigan.com>	2026-01-26 13:50:28 -08:00
hikari	caffb14deb	docs: update README to standard template Node.js CI / CI (push) Failing after 23s Details Security Scan and Upload / Security & DefectDojo Upload (push) Successful in 1m3s Details	2026-01-26 12:42:36 -08:00
naomi	9bdd7b8fa9	feat: add fan art policy Node.js CI / CI (push) Failing after 20s Details Security Scan and Upload / Security & DefectDojo Upload (push) Successful in 1m36s Details	2025-12-30 16:51:06 -08:00
naomi	5116bca086	feat: automated upload of .gitea/workflows/ci.yml Node.js CI / CI (push) Successful in 1m0s Details Security Scan and Upload / Security & DefectDojo Upload (push) Successful in 1m1s Details	2025-12-22 19:41:36 +01:00
naomi	cc28f94a7a	feat: automated upload of .gitea/workflows/ci.yml Node.js CI / CI (push) Failing after 9s Details Security Scan and Upload / Security & DefectDojo Upload (push) Successful in 1m10s Details	2025-12-22 19:35:05 +01:00
naomi	9013d181b4	feat: automated upload of .gitea/workflows/ci.yml Node.js CI / Lint and Test (push) Failing after 2s Details Security Scan and Upload / Security & DefectDojo Upload (push) Successful in 1m0s Details	2025-12-22 19:24:57 +01:00
naomi	c2e25035e2	feat: automated upload of .npmrc Node.js CI / Lint and Test (push) Successful in 58s Details Security Scan and Upload / Security & DefectDojo Upload (push) Successful in 1m6s Details	2025-12-22 19:15:54 +01:00
naomi	c5a329d104	feat: we do even more things (#20 ) Node.js CI / Lint and Test (push) Successful in 57s Details Security Scan and Upload / Security & DefectDojo Upload (push) Successful in 1m23s Details ### Explanation _No response_ ### Issue Closes #18 ### Attestations - [ ] I have read and agree to the [Code of Conduct](https://docs.nhcarrigan.com/community/coc/) - [ ] I have read and agree to the [Community Guidelines](https://docs.nhcarrigan.com/community/guide/). - [ ] My contribution complies with the [Contributor Covenant](https://docs.nhcarrigan.com/dev/covenant/). ### Dependencies - [ ] I have pinned the dependencies to a specific patch version. ### Style - [ ] I have run the linter and resolved any errors. - [ ] My pull request uses an appropriate title, matching the conventional commit standards. - [ ] My scope of feat/fix/chore/etc. correctly matches the nature of changes in my pull request. ### Tests - [ ] My contribution adds new code, and I have added tests to cover it. - [ ] My contribution modifies existing code, and I have updated the tests to reflect these changes. - [ ] All new and existing tests pass locally with my changes. - [ ] Code coverage remains at or above the configured threshold. ### Documentation _No response_ ### Versioning _No response_ Reviewed-on: #20 Co-authored-by: Naomi Carrigan <commits@nhcarrigan.com> Co-committed-by: Naomi Carrigan <commits@nhcarrigan.com>	2025-12-18 05:21:22 +01:00
naomi	d0401ad611	feat: automated upload of .gitea/workflows/security.yml Node.js CI / Lint and Test (push) Successful in 1m0s Details Security Scan and Upload / Security & DefectDojo Upload (push) Successful in 1m23s Details	2025-12-18 03:07:49 +01:00
naomi	6b55719c04	feat: automated upload of .gitea/workflows/security.yml Node.js CI / Lint and Test (push) Successful in 1m12s Details Security Scan and Upload / Security & DefectDojo Upload (push) Successful in 1m17s Details	2025-12-17 23:25:47 +01:00