From 9b2ba8a9dc0233d8553193736077063fa4ca4bbb Mon Sep 17 00:00:00 2001
From: Claude <noreply@anthropic.com>
Date: Wed, 18 Mar 2026 06:26:56 +0000
Subject: [PATCH] fix loading bug: use script tags for embedded markdown
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The previous approach embedded markdown as JS string literals, but
unescaped quotes in the content caused syntax errors that prevented
the page from rendering. Now uses <script type="text/x-markdown">
tags which avoid all escaping issues — the browser treats the content
as plain text and JS reads it via .textContent.

https://claude.ai/code/session_01BgQZR5yFQxP94gNvDkvavs
---
 docs/index.html | 848 +++++++++++++++++++++++++++++++++++++++++++++---
 1 file changed, 811 insertions(+), 37 deletions(-)

diff --git a/docs/index.html b/docs/index.html
index 4c2083a..311d266 100644
--- a/docs/index.html
+++ b/docs/index.html
@@ -37,7 +37,6 @@
       background: var(--color-bg);
     }
 
-    /* Header */
     .site-header {
       background: var(--color-header-bg);
       color: var(--color-header-text);
@@ -92,14 +91,12 @@
       padding: 4px;
     }
 
-    /* Layout */
     .layout {
       display: flex;
       margin-top: 56px;
       min-height: calc(100vh - 56px);
     }
 
-    /* Sidebar */
     .sidebar {
       width: var(--sidebar-width);
       background: var(--color-sidebar-bg);
@@ -149,7 +146,6 @@
       color: var(--color-link);
     }
 
-    /* Content */
     .content {
       margin-left: var(--sidebar-width);
       flex: 1;
@@ -157,13 +153,6 @@
       padding: 32px 48px;
     }
 
-    .content .loading {
-      color: var(--color-text-secondary);
-      padding: 48px 0;
-      text-align: center;
-    }
-
-    /* Markdown content styles */
     .content h1 {
       font-size: 32px;
       font-weight: 600;
@@ -280,7 +269,6 @@
       font-weight: 600;
     }
 
-    /* Footer */
     .page-footer {
       margin-top: 48px;
       padding-top: 16px;
@@ -301,7 +289,6 @@
       text-decoration: underline;
     }
 
-    /* Mobile */
     @media (max-width: 768px) {
       .hamburger {
         display: block;
@@ -363,30 +350,824 @@ <h3>Support</h3>
     </main>
   </div>
 
-  <script src="https://cdnjs.cloudflare.com/ajax/libs/marked/12.0.1/marked.min.js"></script>
-  <script src="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/11.9.0/highlight.min.js"></script>
-  <script src="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/11.9.0/languages/python.min.js"></script>
-  <script src="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/11.9.0/languages/bash.min.js"></script>
-  <script src="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/11.9.0/languages/ini.min.js"></script>
-  <script>
-    // Embedded wiki content — no runtime fetch needed
-    var PAGES = {
-      'Home': "# python-snacks\n\nA personal CLI tool for managing a local stash of reusable Python code snippets. Copy snippets in and out of projects with a single command, and manage multiple named stashes.\n\n## Quick Start\n\n```bash\n# Install\npipx install python-snacks\n\n# Create your first stash\nsnack stash create default ~/snack-stash\n\n# Browse what you have\nsnack list\n\n# Pull snippets from a GitHub repo into your stash\nsnack stash add-remote owner/my-snippets\n\n# Copy a snippet into your project\nsnack unpack auth/google_oauth.py\n\n# Copy an improved snippet back into the stash\nsnack pack auth/google_oauth.py\n```\n\n## Pages\n\n- [[Installation]] \u2014 Install via pipx or pip\n- [[Configuration]] \u2014 Named stashes, env var, and config file\n- [[Commands-Reference]] \u2014 Full reference for all commands and flags\n- [[Writing-Good-Snippets]] \u2014 How to write snippets that stay reusable\n- [[Error-Reference]] \u2014 Diagnose and fix common errors\n- [[Contributing]] \u2014 Dev setup, tests, and release process\n\n## Links\n\n- [PyPI \u2014 python-snacks](https://pypi.org/project/python-snacks/)\n- [GitHub Repository](https://github.com/kickash/python-snacks)",
+  <!-- Embedded wiki pages as hidden script blocks (avoids JS string escaping issues) -->
+  <script type="text/x-markdown" id="page-Home"># python-snacks
+
+A personal CLI tool for managing a local stash of reusable Python code snippets. Copy snippets in and out of projects with a single command, and manage multiple named stashes.
+
+## Quick Start
+
+```bash
+# Install
+pipx install python-snacks
+
+# Create your first stash
+snack stash create default ~/snack-stash
+
+# Browse what you have
+snack list
+
+# Pull snippets from a GitHub repo into your stash
+snack stash add-remote owner/my-snippets
+
+# Copy a snippet into your project
+snack unpack auth/google_oauth.py
+
+# Copy an improved snippet back into the stash
+snack pack auth/google_oauth.py
+```
+
+## Pages
+
+- [[Installation]] — Install via pipx or pip
+- [[Configuration]] — Named stashes, env var, and config file
+- [[Commands-Reference]] — Full reference for all commands and flags
+- [[Writing-Good-Snippets]] — How to write snippets that stay reusable
+- [[Error-Reference]] — Diagnose and fix common errors
+- [[Contributing]] — Dev setup, tests, and release process
+
+## Links
+
+- [PyPI — python-snacks](https://pypi.org/project/python-snacks/)
+- [GitHub Repository](https://github.com/kickash/python-snacks)</script>
+
+  <script type="text/x-markdown" id="page-Installation"># Installation
+
+## Requirements
+
+- Python 3.10 or later
+
+## Recommended: pipx
+
+[pipx](https://pipx.pypa.io) installs CLI tools in isolated environments so they don't conflict with your project dependencies.
+
+```bash
+pipx install python-snacks
+```
+
+## Alternative: pip
+
+```bash
+pip install python-snacks
+```
+
+If you want it available globally, use `pip install --user python-snacks` or install inside a virtual environment you always activate.
+
+## Verify
+
+```bash
+snack --help
+```
+
+You should see:
+
+```
+Usage: snack [OPTIONS] COMMAND [ARGS]...
+
+  Manage your personal snack stash of reusable Python snippets.
+
+Commands:
+  unpack  Copy a snippet FROM the stash INTO the current working directory.
+  pack    Copy a snippet FROM the current working directory INTO the stash.
+  list    List all snippets in the stash.
+  search  Search snippet filenames for a keyword.
+  stash   Manage stash directories.
+```
+
+## Upgrading
+
+```bash
+pipx upgrade python-snacks
+# or
+pip install --upgrade python-snacks
+```
+
+New versions are published to PyPI automatically when a `v*` tag is pushed to the repository.
+
+## Next Step
+
+[[Configuration]] — create your first stash and tell the tool where it lives.</script>
+
+  <script type="text/x-markdown" id="page-Configuration"># Configuration
+
+Snack Stash supports multiple named stashes. The active stash is used by all snippet commands (`list`, `search`, `unpack`, `pack`).
+
+## Priority Order
+
+1. `SNACK_STASH` environment variable (overrides everything)
+2. Active stash in `~/.snackstashrc`
+3. Error — nothing is configured
+
+---
+
+## Method 1: Named stashes (recommended)
+
+Use `snack stash create` to register stashes. This is the standard workflow and requires no manual config editing.
+
+```bash
+# Create your first stash (auto-activated)
+snack stash create default ~/snack-stash
+
+# Add a second stash without switching to it
+snack stash create work ~/work-stash --no-activate
+
+# See what's configured
+snack stash list
+#   default  /Users/you/snack-stash  ← active
+#   work     /Users/you/work-stash
+```
+
+This writes `~/.snackstashrc` in INI format:
+
+```ini
+[config]
+active = default
+
+[stash.default]
+path = /Users/you/snack-stash
+
+[stash.work]
+path = /Users/you/work-stash
+```
+
+You can edit this file by hand if needed.
+
+---
+
+## Method 2: Environment variable
+
+Set `SNACK_STASH` to override the config file entirely. Useful for scripts, CI, or quickly switching context.
+
+```bash
+export SNACK_STASH=~/snack-stash
+```
+
+Add to `~/.zshrc` or `~/.bashrc` to make it permanent:
+
+```bash
+echo 'export SNACK_STASH=~/snack-stash' >> ~/.zshrc
+```
+
+When `SNACK_STASH` is set, named stashes in the config file are ignored for all snippet commands. `snack stash list` will still display configured stashes but will note the override.
+
+---
+
+## Stash directory structure
+
+A stash is a plain directory of `.py` files, organized into subdirectories by category. No special files or metadata are required.
+
+```
+~/snack-stash/
+├── auth/
+│   ├── google_oauth_fastapi.py
+│   ├── google_oauth_flask.py
+│   └── jwt_helpers.py
+├── forms/
+│   ├── contact_form.py
+│   └── newsletter_signup.py
+└── email/
+    └── smtp_sender.py
+```
+
+The directory can be managed with Git, Dropbox, or any other sync mechanism independently of this tool. Syncing is outside the scope of `snack` — it only copies files in and out.
+
+---
+
+## Switching the active stash
+
+To change which named stash is active, create a new one with `--activate` or edit `~/.snackstashrc` directly and update the `active` key under `[config]`.
+
+---
+
+## Verifying your configuration
+
+```bash
+snack stash list    # see all stashes and which is active
+snack list          # confirm the active stash has snippets
+```
+
+See [[Error-Reference]] for help with configuration errors.</script>
+
+  <script type="text/x-markdown" id="page-Commands-Reference"># Commands Reference
+
+## Summary
+
+| Command | Description |
+|---|---|
+| `snack list [category]` | List all snippets, optionally filtered by category |
+| `snack search <keyword>` | Search snippet filenames for a keyword |
+| `snack unpack <snippet> [--flat] [--force]` | Copy a snippet from the stash into the current directory |
+| `snack pack <snippet> [--force]` | Copy a snippet from the current directory into the stash |
+| `snack stash create <name> <path>` | Register a new named stash directory |
+| `snack stash list` | List all configured stashes |
+| `snack stash move <name> <new-path>` | Move a stash to a new location |
+| `snack stash add-remote <repo> [--subdir] [--force]` | Copy snippets from a GitHub repo into the active stash |
+
+All commands accept `--help` for inline usage information.
+
+---
+
+## Snippet commands
+
+These commands operate on the **active stash** (set via `snack stash create` or the `SNACK_STASH` env var).
+
+### `snack list`
+
+Lists all `.py` files in the stash, sorted alphabetically.
+
+```bash
+snack list
+```
+
+Output:
+
+```
+auth/google_oauth_fastapi.py
+auth/google_oauth_flask.py
+auth/jwt_helpers.py
+forms/contact_form.py
+forms/newsletter_signup.py
+email/smtp_sender.py
+```
+
+#### Filter by category
+
+Pass a category name (subdirectory) to narrow the output:
+
+```bash
+snack list auth
+```
+
+Output:
+
+```
+auth/google_oauth_fastapi.py
+auth/google_oauth_flask.py
+auth/jwt_helpers.py
+```
+
+---
+
+### `snack search`
+
+Searches snippet filenames (not file contents) for a keyword. Case-insensitive.
+
+```bash
+snack search oauth
+```
+
+Output:
+
+```
+auth/google_oauth_fastapi.py
+auth/google_oauth_flask.py
+```
+
+---
+
+### `snack unpack`
+
+Copies a snippet **from the stash** into the **current working directory**.
+
+```bash
+snack unpack auth/google_oauth_fastapi.py
+```
+
+The path is relative to the stash root. Use `snack list` or `snack search` to find the correct path.
+
+#### Flags
+
+| Flag | Description |
+|---|---|
+| `--flat` | Copy the file directly into the current directory, discarding subdirectory structure |
+| `--force` | Overwrite an existing file without prompting |
+
+#### Default (preserves structure)
+
+```bash
+cd ~/projects/my-app
+snack unpack auth/google_oauth_fastapi.py
+# Creates: ./auth/google_oauth_fastapi.py
+```
+
+#### `--flat`
+
+```bash
+snack unpack auth/google_oauth_fastapi.py --flat
+# Creates: ./google_oauth_fastapi.py
+```
+
+#### Overwrite prompt
+
+If the destination file already exists:
+
+```
+'./auth/google_oauth_fastapi.py' already exists. Overwrite? [y/N]:
+```
+
+Pass `--force` to skip the prompt.
+
+---
+
+### `snack pack`
+
+Copies a file **from the current working directory** into the stash. Use this when you have improved a snippet during a project and want to update the canonical version.
+
+```bash
+snack pack auth/google_oauth_fastapi.py
+```
+
+The path is relative to the current working directory and is used as-is inside the stash.
+
+#### Flags
+
+| Flag | Description |
+|---|---|
+| `--force` | Overwrite an existing stash file without prompting |
+
+---
+
+## Stash management commands
+
+### `snack stash create`
+
+Registers a new named stash directory and creates it on disk if it doesn't already exist.
+
+```bash
+snack stash create default ~/snack-stash
+snack stash create work ~/work-stash
+snack stash create work ~/work-stash --no-activate
+```
+
+The first stash created is automatically set as active. For subsequent stashes, use `--activate` (the default) to switch, or `--no-activate` to add without switching.
+
+#### Flags
+
+| Flag | Default | Description |
+|---|---|---|
+| `--activate` / `--no-activate` | `--activate` | Whether to set this as the active stash |
+
+---
+
+### `snack stash list`
+
+Shows all configured stashes with their paths, marking the active one.
+
+```bash
+snack stash list
+```
+
+Output:
+
+```
+  default  /Users/you/snack-stash  ← active
+  work     /Users/you/work-stash
+```
+
+If a stash path no longer exists on disk, it is flagged:
+
+```
+  default  /Users/you/snack-stash  ← active  [path missing!]
+```
+
+If `SNACK_STASH` env var is set, a note is shown at the bottom indicating it is overriding the active stash.
+
+---
 
-      'Installation': "# Installation\n\n## Requirements\n\n- Python 3.10 or later\n\n## Recommended: pipx\n\n[pipx](https://pipx.pypa.io) installs CLI tools in isolated environments so they don\u2019t conflict with your project dependencies.\n\n```bash\npipx install python-snacks\n```\n\n## Alternative: pip\n\n```bash\npip install python-snacks\n```\n\nIf you want it available globally, use `pip install --user python-snacks` or install inside a virtual environment you always activate.\n\n## Verify\n\n```bash\nsnack --help\n```\n\nYou should see:\n\n```\nUsage: snack [OPTIONS] COMMAND [ARGS]...\n\n  Manage your personal snack stash of reusable Python snippets.\n\nCommands:\n  unpack  Copy a snippet FROM the stash INTO the current working directory.\n  pack    Copy a snippet FROM the current working directory INTO the stash.\n  list    List all snippets in the stash.\n  search  Search snippet filenames for a keyword.\n  stash   Manage stash directories.\n```\n\n## Upgrading\n\n```bash\npipx upgrade python-snacks\n# or\npip install --upgrade python-snacks\n```\n\nNew versions are published to PyPI automatically when a `v*` tag is pushed to the repository.\n\n## Next Step\n\n[[Configuration]] \u2014 create your first stash and tell the tool where it lives.",
+### `snack stash move`
 
-      'Configuration': "# Configuration\n\nSnack Stash supports multiple named stashes. The active stash is used by all snippet commands (`list`, `search`, `unpack`, `pack`).\n\n## Priority Order\n\n1. `SNACK_STASH` environment variable (overrides everything)\n2. Active stash in `~/.snackstashrc`\n3. Error \u2014 nothing is configured\n\n---\n\n## Method 1: Named stashes (recommended)\n\nUse `snack stash create` to register stashes. This is the standard workflow and requires no manual config editing.\n\n```bash\n# Create your first stash (auto-activated)\nsnack stash create default ~/snack-stash\n\n# Add a second stash without switching to it\nsnack stash create work ~/work-stash --no-activate\n\n# See what's configured\nsnack stash list\n#   default  /Users/you/snack-stash  \u2190 active\n#   work     /Users/you/work-stash\n```\n\nThis writes `~/.snackstashrc` in INI format:\n\n```ini\n[config]\nactive = default\n\n[stash.default]\npath = /Users/you/snack-stash\n\n[stash.work]\npath = /Users/you/work-stash\n```\n\nYou can edit this file by hand if needed.\n\n---\n\n## Method 2: Environment variable\n\nSet `SNACK_STASH` to override the config file entirely. Useful for scripts, CI, or quickly switching context.\n\n```bash\nexport SNACK_STASH=~/snack-stash\n```\n\nAdd to `~/.zshrc` or `~/.bashrc` to make it permanent:\n\n```bash\necho 'export SNACK_STASH=~/snack-stash' >> ~/.zshrc\n```\n\nWhen `SNACK_STASH` is set, named stashes in the config file are ignored for all snippet commands. `snack stash list` will still display configured stashes but will note the override.\n\n---\n\n## Stash directory structure\n\nA stash is a plain directory of `.py` files, organized into subdirectories by category. No special files or metadata are required.\n\n```\n~/snack-stash/\n\u251c\u2500\u2500 auth/\n\u2502   \u251c\u2500\u2500 google_oauth_fastapi.py\n\u2502   \u251c\u2500\u2500 google_oauth_flask.py\n\u2502   \u2514\u2500\u2500 jwt_helpers.py\n\u251c\u2500\u2500 forms/\n\u2502   \u251c\u2500\u2500 contact_form.py\n\u2502   \u2514\u2500\u2500 newsletter_signup.py\n\u2514\u2500\u2500 email/\n    \u2514\u2500\u2500 smtp_sender.py\n```\n\nThe directory can be managed with Git, Dropbox, or any other sync mechanism independently of this tool. Syncing is outside the scope of `snack` \u2014 it only copies files in and out.\n\n---\n\n## Switching the active stash\n\nTo change which named stash is active, create a new one with `--activate` or edit `~/.snackstashrc` directly and update the `active` key under `[config]`.\n\n---\n\n## Verifying your configuration\n\n```bash\nsnack stash list    # see all stashes and which is active\nsnack list          # confirm the active stash has snippets\n```\n\nSee [[Error-Reference]] for help with configuration errors.",
+Moves a stash directory to a new location on disk and updates the path in `~/.snackstashrc`.
 
-      'Commands-Reference': "# Commands Reference\n\n## Summary\n\n| Command | Description |\n|---|---|\n| `snack list [category]` | List all snippets, optionally filtered by category |\n| `snack search <keyword>` | Search snippet filenames for a keyword |\n| `snack unpack <snippet> [--flat] [--force]` | Copy a snippet from the stash into the current directory |\n| `snack pack <snippet> [--force]` | Copy a snippet from the current directory into the stash |\n| `snack stash create <name> <path>` | Register a new named stash directory |\n| `snack stash list` | List all configured stashes |\n| `snack stash move <name> <new-path>` | Move a stash to a new location |\n| `snack stash add-remote <repo> [--subdir] [--force]` | Copy snippets from a GitHub repo into the active stash |\n\nAll commands accept `--help` for inline usage information.\n\n---\n\n## Snippet commands\n\nThese commands operate on the **active stash** (set via `snack stash create` or the `SNACK_STASH` env var).\n\n### `snack list`\n\nLists all `.py` files in the stash, sorted alphabetically.\n\n```bash\nsnack list\n```\n\nOutput:\n\n```\nauth/google_oauth_fastapi.py\nauth/google_oauth_flask.py\nauth/jwt_helpers.py\nforms/contact_form.py\nforms/newsletter_signup.py\nemail/smtp_sender.py\n```\n\n#### Filter by category\n\nPass a category name (subdirectory) to narrow the output:\n\n```bash\nsnack list auth\n```\n\nOutput:\n\n```\nauth/google_oauth_fastapi.py\nauth/google_oauth_flask.py\nauth/jwt_helpers.py\n```\n\n---\n\n### `snack search`\n\nSearches snippet filenames (not file contents) for a keyword. Case-insensitive.\n\n```bash\nsnack search oauth\n```\n\nOutput:\n\n```\nauth/google_oauth_fastapi.py\nauth/google_oauth_flask.py\n```\n\n---\n\n### `snack unpack`\n\nCopies a snippet **from the stash** into the **current working directory**.\n\n```bash\nsnack unpack auth/google_oauth_fastapi.py\n```\n\nThe path is relative to the stash root. Use `snack list` or `snack search` to find the correct path.\n\n#### Flags\n\n| Flag | Description |\n|---|---|\n| `--flat` | Copy the file directly into the current directory, discarding subdirectory structure |\n| `--force` | Overwrite an existing file without prompting |\n\n#### Default (preserves structure)\n\n```bash\ncd ~/projects/my-app\nsnack unpack auth/google_oauth_fastapi.py\n# Creates: ./auth/google_oauth_fastapi.py\n```\n\n#### `--flat`\n\n```bash\nsnack unpack auth/google_oauth_fastapi.py --flat\n# Creates: ./google_oauth_fastapi.py\n```\n\n#### Overwrite prompt\n\nIf the destination file already exists:\n\n```\n'./auth/google_oauth_fastapi.py' already exists. Overwrite? [y/N]:\n```\n\nPass `--force` to skip the prompt.\n\n---\n\n### `snack pack`\n\nCopies a file **from the current working directory** into the stash. Use this when you have improved a snippet during a project and want to update the canonical version.\n\n```bash\nsnack pack auth/google_oauth_fastapi.py\n```\n\nThe path is relative to the current working directory and is used as-is inside the stash.\n\n#### Flags\n\n| Flag | Description |\n|---|---|\n| `--force` | Overwrite an existing stash file without prompting |\n\n---\n\n## Stash management commands\n\n### `snack stash create`\n\nRegisters a new named stash directory and creates it on disk if it doesn\u2019t already exist.\n\n```bash\nsnack stash create default ~/snack-stash\nsnack stash create work ~/work-stash\nsnack stash create work ~/work-stash --no-activate\n```\n\nThe first stash created is automatically set as active. For subsequent stashes, use `--activate` (the default) to switch, or `--no-activate` to add without switching.\n\n#### Flags\n\n| Flag | Default | Description |\n|---|---|---|\n| `--activate` / `--no-activate` | `--activate` | Whether to set this as the active stash |\n\n---\n\n### `snack stash list`\n\nShows all configured stashes with their paths, marking the active one.\n\n```bash\nsnack stash list\n```\n\nOutput:\n\n```\n  default  /Users/you/snack-stash  \u2190 active\n  work     /Users/you/work-stash\n```\n\nIf a stash path no longer exists on disk, it is flagged:\n\n```\n  default  /Users/you/snack-stash  \u2190 active  [path missing!]\n```\n\nIf `SNACK_STASH` env var is set, a note is shown at the bottom indicating it is overriding the active stash.\n\n---\n\n### `snack stash move`\n\nMoves a stash directory to a new location on disk and updates the path in `~/.snackstashrc`.\n\n```bash\nsnack stash move default ~/new-location/snack-stash\n```\n\n- The old directory and all its contents are moved to the new path\n- The config is updated automatically\n- If the old path no longer exists on disk, the new directory is created instead\n- Errors if the new path already exists (to prevent accidental overwrites)\n\n---\n\n### `snack stash add-remote`\n\nDownloads a public GitHub repository as a tarball and copies all `.py` files into the active stash, preserving directory structure.\n\n```bash\nsnack stash add-remote owner/repo\nsnack stash add-remote https://github.com/owner/repo\n```\n\n#### Filter by subdirectory\n\nOnly copy files from a specific subdirectory of the repo:\n\n```bash\nsnack stash add-remote owner/repo --subdir auth\n```\n\nThis copies `auth/google_oauth.py` from the repo as `auth/google_oauth.py` in the stash (the full path is preserved).\n\n#### Flags\n\n| Flag | Description |\n|---|---|\n| `--subdir <dir>` | Only copy files under this subdirectory of the repo |\n| `--force` | Overwrite existing stash files without prompting |\n\n#### Accepted repo formats\n\n- `owner/repo`\n- `https://github.com/owner/repo`\n- `https://github.com/owner/repo.git`\n\nNon-Python files (`.md`, `.txt`, etc.) are never copied.",
+```bash
+snack stash move default ~/new-location/snack-stash
+```
 
-      'Writing-Good-Snippets': "# Writing Good Snippets\n\nA snippet is only as useful as it is reusable. These guidelines help you write snippets that are easy to drop into any project and immediately understand.\n\n---\n\n## The core principle: self-containment\n\nA snippet should work correctly after a single `cp` into a new project. That means:\n\n- All imports are explicit and at the top of the file\n- All configuration comes from parameters or environment variables \u2014 never hardcoded values\n- No assumptions about what else exists in the project\n- No side effects at import time (wrap executable code in functions or `if __name__ == \"__main__\"`)\n\nIf unpacking a snippet requires you to also copy another file, refactor until it doesn\u2019t.\n\n---\n\n## Use a standard header\n\nThe single most useful habit is a consistent docstring that captures three things: what the snippet does, what it depends on, and how to use it. Anyone (including future you) can read this without opening the file.\n\n```python\n\"\"\"Send transactional email via SMTP.\n\nDependencies:\n    stdlib only\n\nUsage:\n    from email.smtp_sender import send_email\n    send_email(to=\"user@example.com\", subject=\"Hello\", body=\"<p>World</p>\")\n\nConfig (env vars):\n    SMTP_HOST     \u2014 mail server hostname\n    SMTP_PORT     \u2014 defaults to 587\n    SMTP_USER     \u2014 sender login\n    SMTP_PASSWORD \u2014 sender password\n\"\"\"\n```\n\nKeep it short. The goal is a five-second orientation, not full API documentation.\n\n---\n\n## Name files to be searchable\n\nFilenames are the primary search surface \u2014 `snack search` matches against them. Choose names that are specific and predictable.\n\n**Good:**\n```\nauth/google_oauth_fastapi.py\nauth/google_oauth_flask.py\nforms/contact_form_wtf.py\nemail/smtp_sender.py\nstorage/s3_upload.py\n```\n\n**Avoid:**\n```\nauth/helpers.py       # too vague\nauth/utils.py         # tells you nothing\nauth/new_version.py   # not a meaningful name\n```\n\nWhen a snippet has framework-specific variants, use a suffix: `_fastapi`, `_flask`, `_django`, `_sqlalchemy`. This makes `snack search fastapi` return only what\u2019s relevant.\n\n---\n\n## One file, one job\n\nResist the urge to bundle related utilities into a single file. A snippet called `auth_helpers.py` that contains OAuth, JWT, and session logic will only ever be partially useful. Three focused snippets are more valuable than one large one.\n\nThe right size for a snippet is: \"I need exactly this, and I copy exactly this.\"\n\n---\n\n## Organise by what a project needs, not by technical category\n\nThink about how you reach for snippets when starting a project. Categories like `auth/`, `forms/`, `email/`, `storage/`, `payments/` map to features. Categories like `decorators/` or `metaclasses/` map to implementation details and are harder to browse purposefully.\n\n```\n~/snack-stash/\n\u251c\u2500\u2500 auth/           # authentication and authorisation\n\u251c\u2500\u2500 email/          # sending and templating emails\n\u251c\u2500\u2500 forms/          # form handling and validation\n\u251c\u2500\u2500 payments/       # Stripe, etc.\n\u251c\u2500\u2500 storage/        # file uploads, S3, local disk\n\u2514\u2500\u2500 tasks/          # background jobs, queues\n```\n\n---\n\n## Keep configuration out of the code\n\nConfiguration that varies per-project (API keys, hostnames, feature flags) should be read from environment variables or passed as function arguments. Never commit a snippet with hardcoded credentials or URLs.\n\n```python\n# Good \u2014 caller provides credentials\ndef create_oauth_client(client_id: str, client_secret: str) -> OAuth2Session:\n    ...\n\n# Good \u2014 reads from environment\nSTRIPE_KEY = os.environ[\"STRIPE_SECRET_KEY\"]\n\n# Bad \u2014 hardcoded\nSTRIPE_KEY = \"sk_live_abc123\"\n```\n\n---\n\n## Update the stash when you improve a snippet\n\nThe stash is most valuable when it reflects your current best practice, not the version from two years ago. When you improve a snippet during a project, pack it back:\n\n```bash\nsnack pack auth/google_oauth_fastapi.py\n```\n\nIf you manage your stash as a Git repo, commit the improvement there too. The stash stays useful only if it gets maintained like any other codebase.",
+- The old directory and all its contents are moved to the new path
+- The config is updated automatically
+- If the old path no longer exists on disk, the new directory is created instead
+- Errors if the new path already exists (to prevent accidental overwrites)
 
-      'Error-Reference': "# Error Reference\n\n## Stash not configured\n\n**Message:**\n```\n[error] Snack stash location is not configured.\nCreate a stash with:\n  snack stash create default ~/snack-stash\nOr set the SNACK_STASH environment variable:\n  export SNACK_STASH=~/snack-stash\n```\n\n**Cause:** No stash has been created and `SNACK_STASH` is not set.\n\n**Fix:** Run `snack stash create default ~/snack-stash` to get started. See [[Configuration]] for full details.\n\n---\n\n## Stash path does not exist\n\n**Message:**\n```\n[error] SNACK_STASH is set to '/path/to/stash' but that path does not exist.\n```\n\nor\n\n```\n[error] Active stash 'default' path '/path/to/stash' does not exist.\n```\n\n**Cause:** The configured path is not present on disk. Common reasons:\n- The directory was moved or deleted manually (use `snack stash move` instead)\n- A typo in the path\n- The drive or volume it lives on is not mounted\n\n**Fix:** Either recreate the directory, correct the path in `~/.snackstashrc`, or run `snack stash move` to point the stash to its new location.\n\n---\n\n## Snippet not found in stash (`unpack`)\n\n**Message:**\n```\n[error] 'auth/nope.py' not found in stash (/path/to/stash).\n```\n\n**Cause:** The path passed to `snack unpack` does not exist in the stash.\n\n**Fix:** Use `snack list` or `snack search` to find the correct path:\n\n```bash\nsnack list auth\nsnack search oauth\n```\n\n---\n\n## Source file not found (`pack`)\n\n**Message:**\n```\n[error] 'auth/google_oauth.py' not found in current directory.\n```\n\n**Cause:** The file passed to `snack pack` does not exist relative to the current working directory.\n\n**Fix:** Check your working directory and the path you provided:\n\n```bash\npwd\nls auth/\n```\n\n---\n\n## Overwrite conflict\n\n**Message:**\n```\n'/path/to/file.py' already exists. Overwrite? [y/N]:\n```\n\n**Cause:** The destination file already exists. Applies to `snack unpack`, `snack pack`, and `snack stash add-remote`.\n\n**Fix:**\n- Answer `y` at the prompt to overwrite\n- Answer `n` (or press Enter) to abort\n- Pass `--force` to skip the prompt:\n\n```bash\nsnack unpack auth/google_oauth.py --force\nsnack pack auth/google_oauth.py --force\nsnack stash add-remote owner/repo --force\n```\n\n---\n\n## Stash name already exists (`stash create`)\n\n**Message:**\n```\n[error] A stash named 'default' already exists.\n```\n\n**Cause:** You ran `snack stash create` with a name that is already registered in `~/.snackstashrc`.\n\n**Fix:** Choose a different name, or edit `~/.snackstashrc` directly to remove the existing entry first.\n\n---\n\n## Unknown stash name (`stash move`)\n\n**Message:**\n```\n[error] No stash named 'foo'. Run 'snack stash list' to see available stashes.\n```\n\n**Cause:** The name passed to `snack stash move` is not registered in `~/.snackstashrc`.\n\n**Fix:** Run `snack stash list` to see valid names.\n\n---\n\n## Move target already exists (`stash move`)\n\n**Message:**\n```\n[error] '/new/path' already exists.\n```\n\n**Cause:** The destination path for `snack stash move` is already present on disk.\n\n**Fix:** Choose a different target path, or remove the existing directory first if it is safe to do so.\n\n---\n\n## GitHub repo not found or inaccessible (`stash add-remote`)\n\n**Message:**\n```\n[error] HTTP 404: Not Found\n```\n\n**Cause:** The repository does not exist, is private, or the URL is incorrect.\n\n**Fix:** Check the repo name and ensure it is public. Private repos are not supported without a token (which is not currently a supported feature).\n\n---\n\n## Invalid repo format (`stash add-remote`)\n\n**Message:**\n```\n[error] Invalid repo 'not-a-repo'. Use 'owner/repo' or a full GitHub URL.\n```\n\n**Cause:** The argument passed to `snack stash add-remote` could not be parsed.\n\n**Fix:** Use one of the supported formats:\n\n```bash\nsnack stash add-remote owner/repo\nsnack stash add-remote https://github.com/owner/repo\n```",
+---
 
-      'Contributing': "# Contributing\n\n## Dev Setup\n\nClone the repo and install in editable mode with test dependencies:\n\n```bash\ngit clone https://github.com/kickash/python-snacks.git\ncd python-snacks\npip install -e \".[test]\"\n```\n\nVerify the CLI works:\n\n```bash\nsnack --help\n```\n\n## Running Tests\n\n```bash\npytest tests/ -v\n```\n\nThe test suite has 33 tests across two files:\n\n- `tests/test_commands.py` \u2014 snippet commands (`list`, `search`, `unpack`, `pack`), config resolution, error cases\n- `tests/test_stash_commands.py` \u2014 stash management commands (`create`, `list`, `move`, `add-remote`), including mocked HTTP for `add-remote`\n\nTests never write to `~/.snackstashrc` \u2014 the config path is redirected to a temp file via `monkeypatch`.\n\n## CI\n\nEvery push and pull request to `main` runs the test suite against Python 3.10, 3.11, and 3.12 via GitHub Actions (`.github/workflows/ci.yml`). Pull requests must pass CI before merging.\n\n## Release Process\n\nReleases are fully automated via `.github/workflows/publish.yml`.\n\n1. Update the version in `pyproject.toml`\n2. Commit and push to `main`\n3. Tag the commit with a `v`-prefixed version and push the tag:\n\n```bash\ngit tag v0.2.0\ngit push origin v0.2.0\n```\n\nThe publish workflow will:\n- Run the test suite\n- Build the sdist and wheel\n- Publish to PyPI (via OIDC trusted publishing \u2014 no API token required)\n- Create a GitHub Release with the built artifacts attached\n\n## Project Structure\n\n```\npython-snacks/\n\u251c\u2500\u2500 pyproject.toml              # Package metadata and dependencies\n\u251c\u2500\u2500 snacks/\n\u2502   \u251c\u2500\u2500 main.py                 # Typer app and all command definitions\n\u2502   \u251c\u2500\u2500 config.py               # SnackConfig class, stash path resolution\n\u2502   \u2514\u2500\u2500 ops.py                  # File ops: pack, unpack, add_remote\n\u2514\u2500\u2500 tests/\n    \u251c\u2500\u2500 test_commands.py        # Snippet command tests\n    \u2514\u2500\u2500 test_stash_commands.py  # Stash management tests\n```\n\n## Key design notes\n\n- **Config format:** `~/.snackstashrc` uses INI format (`[stash.<name>]` sections). The old `stash=<path>` sectionless format is still read for backwards compatibility but never written.\n- **`SNACK_STASH` env var:** Always overrides the config file for all snippet commands. Useful for scripts and CI.\n- **`add-remote`:** Uses only stdlib (`urllib`, `tarfile`) \u2014 no additional dependencies beyond Typer.\n- **Test isolation:** `monkeypatch.setattr(config_module, \"CONFIG_PATH\", ...)` redirects the config file to a temp path so tests are hermetic."
-    };
+### `snack stash add-remote`
 
-    var PAGE_NAMES = Object.keys(PAGES);
+Downloads a public GitHub repository as a tarball and copies all `.py` files into the active stash, preserving directory structure.
+
+```bash
+snack stash add-remote owner/repo
+snack stash add-remote https://github.com/owner/repo
+```
+
+#### Filter by subdirectory
+
+Only copy files from a specific subdirectory of the repo:
+
+```bash
+snack stash add-remote owner/repo --subdir auth
+```
+
+This copies `auth/google_oauth.py` from the repo as `auth/google_oauth.py` in the stash (the full path is preserved).
+
+#### Flags
+
+| Flag | Description |
+|---|---|
+| `--subdir <dir>` | Only copy files under this subdirectory of the repo |
+| `--force` | Overwrite existing stash files without prompting |
+
+#### Accepted repo formats
+
+- `owner/repo`
+- `https://github.com/owner/repo`
+- `https://github.com/owner/repo.git`
+
+Non-Python files (`.md`, `.txt`, etc.) are never copied.</script>
+
+  <script type="text/x-markdown" id="page-Writing-Good-Snippets"># Writing Good Snippets
+
+A snippet is only as useful as it is reusable. These guidelines help you write snippets that are easy to drop into any project and immediately understand.
+
+---
+
+## The core principle: self-containment
+
+A snippet should work correctly after a single `cp` into a new project. That means:
+
+- All imports are explicit and at the top of the file
+- All configuration comes from parameters or environment variables — never hardcoded values
+- No assumptions about what else exists in the project
+- No side effects at import time (wrap executable code in functions or `if __name__ == "__main__"`)
+
+If unpacking a snippet requires you to also copy another file, refactor until it doesn't.
+
+---
+
+## Use a standard header
+
+The single most useful habit is a consistent docstring that captures three things: what the snippet does, what it depends on, and how to use it. Anyone (including future you) can read this without opening the file.
+
+```python
+"""Send transactional email via SMTP.
+
+Dependencies:
+    stdlib only
+
+Usage:
+    from email.smtp_sender import send_email
+    send_email(to="user@example.com", subject="Hello", body="<p>World</p>")
+
+Config (env vars):
+    SMTP_HOST     — mail server hostname
+    SMTP_PORT     — defaults to 587
+    SMTP_USER     — sender login
+    SMTP_PASSWORD — sender password
+"""
+```
+
+Keep it short. The goal is a five-second orientation, not full API documentation.
+
+---
+
+## Name files to be searchable
+
+Filenames are the primary search surface — `snack search` matches against them. Choose names that are specific and predictable.
+
+**Good:**
+```
+auth/google_oauth_fastapi.py
+auth/google_oauth_flask.py
+forms/contact_form_wtf.py
+email/smtp_sender.py
+storage/s3_upload.py
+```
+
+**Avoid:**
+```
+auth/helpers.py       # too vague
+auth/utils.py         # tells you nothing
+auth/new_version.py   # not a meaningful name
+```
+
+When a snippet has framework-specific variants, use a suffix: `_fastapi`, `_flask`, `_django`, `_sqlalchemy`. This makes `snack search fastapi` return only what's relevant.
+
+---
+
+## One file, one job
+
+Resist the urge to bundle related utilities into a single file. A snippet called `auth_helpers.py` that contains OAuth, JWT, and session logic will only ever be partially useful. Three focused snippets are more valuable than one large one.
+
+The right size for a snippet is: "I need exactly this, and I copy exactly this."
+
+---
+
+## Organise by what a project needs, not by technical category
+
+Think about how you reach for snippets when starting a project. Categories like `auth/`, `forms/`, `email/`, `storage/`, `payments/` map to features. Categories like `decorators/` or `metaclasses/` map to implementation details and are harder to browse purposefully.
+
+```
+~/snack-stash/
+├── auth/           # authentication and authorisation
+├── email/          # sending and templating emails
+├── forms/          # form handling and validation
+├── payments/       # Stripe, etc.
+├── storage/        # file uploads, S3, local disk
+└── tasks/          # background jobs, queues
+```
+
+---
+
+## Keep configuration out of the code
+
+Configuration that varies per-project (API keys, hostnames, feature flags) should be read from environment variables or passed as function arguments. Never commit a snippet with hardcoded credentials or URLs.
+
+```python
+# Good — caller provides credentials
+def create_oauth_client(client_id: str, client_secret: str) -> OAuth2Session:
+    ...
+
+# Good — reads from environment
+STRIPE_KEY = os.environ["STRIPE_SECRET_KEY"]
+
+# Bad — hardcoded
+STRIPE_KEY = "sk_live_abc123"
+```
+
+---
+
+## Update the stash when you improve a snippet
+
+The stash is most valuable when it reflects your current best practice, not the version from two years ago. When you improve a snippet during a project, pack it back:
+
+```bash
+snack pack auth/google_oauth_fastapi.py
+```
+
+If you manage your stash as a Git repo, commit the improvement there too. The stash stays useful only if it gets maintained like any other codebase.</script>
+
+  <script type="text/x-markdown" id="page-Error-Reference"># Error Reference
+
+## Stash not configured
+
+**Message:**
+```
+[error] Snack stash location is not configured.
+Create a stash with:
+  snack stash create default ~/snack-stash
+Or set the SNACK_STASH environment variable:
+  export SNACK_STASH=~/snack-stash
+```
+
+**Cause:** No stash has been created and `SNACK_STASH` is not set.
+
+**Fix:** Run `snack stash create default ~/snack-stash` to get started. See [[Configuration]] for full details.
+
+---
+
+## Stash path does not exist
+
+**Message:**
+```
+[error] SNACK_STASH is set to '/path/to/stash' but that path does not exist.
+```
+
+or
+
+```
+[error] Active stash 'default' path '/path/to/stash' does not exist.
+```
+
+**Cause:** The configured path is not present on disk. Common reasons:
+- The directory was moved or deleted manually (use `snack stash move` instead)
+- A typo in the path
+- The drive or volume it lives on is not mounted
+
+**Fix:** Either recreate the directory, correct the path in `~/.snackstashrc`, or run `snack stash move` to point the stash to its new location.
+
+---
+
+## Snippet not found in stash (`unpack`)
+
+**Message:**
+```
+[error] 'auth/nope.py' not found in stash (/path/to/stash).
+```
+
+**Cause:** The path passed to `snack unpack` does not exist in the stash.
+
+**Fix:** Use `snack list` or `snack search` to find the correct path:
+
+```bash
+snack list auth
+snack search oauth
+```
+
+---
+
+## Source file not found (`pack`)
+
+**Message:**
+```
+[error] 'auth/google_oauth.py' not found in current directory.
+```
+
+**Cause:** The file passed to `snack pack` does not exist relative to the current working directory.
+
+**Fix:** Check your working directory and the path you provided:
+
+```bash
+pwd
+ls auth/
+```
+
+---
+
+## Overwrite conflict
+
+**Message:**
+```
+'/path/to/file.py' already exists. Overwrite? [y/N]:
+```
+
+**Cause:** The destination file already exists. Applies to `snack unpack`, `snack pack`, and `snack stash add-remote`.
+
+**Fix:**
+- Answer `y` at the prompt to overwrite
+- Answer `n` (or press Enter) to abort
+- Pass `--force` to skip the prompt:
+
+```bash
+snack unpack auth/google_oauth.py --force
+snack pack auth/google_oauth.py --force
+snack stash add-remote owner/repo --force
+```
+
+---
+
+## Stash name already exists (`stash create`)
+
+**Message:**
+```
+[error] A stash named 'default' already exists.
+```
+
+**Cause:** You ran `snack stash create` with a name that is already registered in `~/.snackstashrc`.
+
+**Fix:** Choose a different name, or edit `~/.snackstashrc` directly to remove the existing entry first.
+
+---
+
+## Unknown stash name (`stash move`)
+
+**Message:**
+```
+[error] No stash named 'foo'. Run 'snack stash list' to see available stashes.
+```
+
+**Cause:** The name passed to `snack stash move` is not registered in `~/.snackstashrc`.
+
+**Fix:** Run `snack stash list` to see valid names.
+
+---
+
+## Move target already exists (`stash move`)
+
+**Message:**
+```
+[error] '/new/path' already exists.
+```
+
+**Cause:** The destination path for `snack stash move` is already present on disk.
+
+**Fix:** Choose a different target path, or remove the existing directory first if it is safe to do so.
+
+---
+
+## GitHub repo not found or inaccessible (`stash add-remote`)
+
+**Message:**
+```
+[error] HTTP 404: Not Found
+```
+
+**Cause:** The repository does not exist, is private, or the URL is incorrect.
+
+**Fix:** Check the repo name and ensure it is public. Private repos are not supported without a token (which is not currently a supported feature).
+
+---
+
+## Invalid repo format (`stash add-remote`)
+
+**Message:**
+```
+[error] Invalid repo 'not-a-repo'. Use 'owner/repo' or a full GitHub URL.
+```
+
+**Cause:** The argument passed to `snack stash add-remote` could not be parsed.
+
+**Fix:** Use one of the supported formats:
+
+```bash
+snack stash add-remote owner/repo
+snack stash add-remote https://github.com/owner/repo
+```</script>
+
+  <script type="text/x-markdown" id="page-Contributing"># Contributing
+
+## Dev Setup
+
+Clone the repo and install in editable mode with test dependencies:
+
+```bash
+git clone https://github.com/kickash/python-snacks.git
+cd python-snacks
+pip install -e ".[test]"
+```
+
+Verify the CLI works:
+
+```bash
+snack --help
+```
+
+## Running Tests
+
+```bash
+pytest tests/ -v
+```
+
+The test suite has 33 tests across two files:
+
+- `tests/test_commands.py` — snippet commands (`list`, `search`, `unpack`, `pack`), config resolution, error cases
+- `tests/test_stash_commands.py` — stash management commands (`create`, `list`, `move`, `add-remote`), including mocked HTTP for `add-remote`
+
+Tests never write to `~/.snackstashrc` — the config path is redirected to a temp file via `monkeypatch`.
+
+## CI
+
+Every push and pull request to `main` runs the test suite against Python 3.10, 3.11, and 3.12 via GitHub Actions (`.github/workflows/ci.yml`). Pull requests must pass CI before merging.
+
+## Release Process
+
+Releases are fully automated via `.github/workflows/publish.yml`.
+
+1. Update the version in `pyproject.toml`
+2. Commit and push to `main`
+3. Tag the commit with a `v`-prefixed version and push the tag:
+
+```bash
+git tag v0.2.0
+git push origin v0.2.0
+```
+
+The publish workflow will:
+- Run the test suite
+- Build the sdist and wheel
+- Publish to PyPI (via OIDC trusted publishing — no API token required)
+- Create a GitHub Release with the built artifacts attached
+
+## Project Structure
+
+```
+python-snacks/
+├── pyproject.toml              # Package metadata and dependencies
+├── snacks/
+│   ├── main.py                 # Typer app and all command definitions
+│   ├── config.py               # SnackConfig class, stash path resolution
+│   └── ops.py                  # File ops: pack, unpack, add_remote
+└── tests/
+    ├── test_commands.py        # Snippet command tests
+    └── test_stash_commands.py  # Stash management tests
+```
+
+## Key design notes
+
+- **Config format:** `~/.snackstashrc` uses INI format (`[stash.<name>]` sections). The old `stash=<path>` sectionless format is still read for backwards compatibility but never written.
+- **`SNACK_STASH` env var:** Always overrides the config file for all snippet commands. Useful for scripts and CI.
+- **`add-remote`:** Uses only stdlib (`urllib`, `tarfile`) — no additional dependencies beyond Typer.
+- **Test isolation:** `monkeypatch.setattr(config_module, "CONFIG_PATH", ...)` redirects the config file to a temp path so tests are hermetic.</script>
+
+  <script src="https://cdnjs.cloudflare.com/ajax/libs/marked/12.0.1/marked.min.js"></script>
+  <script src="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/11.9.0/highlight.min.js"></script>
+  <script src="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/11.9.0/languages/python.min.js"></script>
+  <script src="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/11.9.0/languages/bash.min.js"></script>
+  <script src="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/11.9.0/languages/ini.min.js"></script>
+  <script>
+    var PAGE_NAMES = [
+      'Home',
+      'Installation',
+      'Configuration',
+      'Commands-Reference',
+      'Writing-Good-Snippets',
+      'Error-Reference',
+      'Contributing'
+    ];
+
+    // Read embedded markdown from script tags
+    var PAGES = {};
+    PAGE_NAMES.forEach(function(name) {
+      var el = document.getElementById('page-' + name);
+      if (el) PAGES[name] = el.textContent;
+    });
 
     // Configure marked to use highlight.js for code blocks
     marked.use({
@@ -401,7 +1182,6 @@ <h3>Support</h3>
           var escaped = text.replace(/&/g,'&amp;').replace(/</g,'&lt;').replace(/>/g,'&gt;');
           return '<pre><code>' + escaped + '</code></pre>';
         },
-        // Convert [[Page]] wiki-links to hash links
         text(token) {
           var raw = token.raw || token.text;
           return raw.replace(/\[\[([^\]]+)\]\]/g, function(match, page) {
@@ -430,12 +1210,10 @@ <h3>Support</h3>
           '<a href="#Home">Back to Home</a>' +
         '</div>';
 
-      // Update active sidebar link
       document.querySelectorAll('.sidebar a').forEach(function(a) {
         a.classList.toggle('active', a.getAttribute('href') === '#' + page);
       });
 
-      // Scroll to top
       window.scrollTo(0, 0);
     }
 
@@ -443,14 +1221,12 @@ <h3>Support</h3>
       document.getElementById('sidebar').classList.toggle('open');
     }
 
-    // Close sidebar on mobile when a link is clicked
     document.getElementById('sidebar').addEventListener('click', function(e) {
       if (e.target.tagName === 'A' && window.innerWidth <= 768) {
         document.getElementById('sidebar').classList.remove('open');
       }
     });
 
-    // Hash-based routing
     function route() {
       var page = location.hash.slice(1) || 'Home';
       if (PAGE_NAMES.indexOf(page) === -1) page = 'Home';
@@ -458,8 +1234,6 @@ <h3>Support</h3>
     }
 
     window.addEventListener('hashchange', route);
-
-    // Initial load
     route();
   </script>
 </body>