diff --git a/.github/workflows/pages.yml b/.github/workflows/pages.yml
index f3e2794..d2bb421 100644
--- a/.github/workflows/pages.yml
+++ b/.github/workflows/pages.yml
@@ -5,6 +5,7 @@ on:
     branches: [main]
     paths:
       - "docs/**"
+      - "wiki/**"
   workflow_dispatch:
 
 permissions:
diff --git a/docs/index.html b/docs/index.html
index 48ae599..4c2083a 100644
--- a/docs/index.html
+++ b/docs/index.html
@@ -369,34 +369,41 @@ <h3>Support</h3>
   <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>
-    const PAGES = [
-      'Home',
-      'Installation',
-      'Configuration',
-      'Commands-Reference',
-      'Writing-Good-Snippets',
-      'Error-Reference',
-      'Contributing'
-    ];
-
-    const pageCache = {};
+    // 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)",
+
+      '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.",
+
+      '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.",
+
+      '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.",
+
+      '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.",
+
+      '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."
+    };
+
+    var PAGE_NAMES = Object.keys(PAGES);
 
     // Configure marked to use highlight.js for code blocks
     marked.use({
       renderer: {
         code(token) {
-          const lang = token.lang || '';
-          const text = token.text;
+          var lang = token.lang || '';
+          var text = token.text;
           if (lang && hljs.getLanguage(lang)) {
-            const highlighted = hljs.highlight(text, { language: lang }).value;
+            var highlighted = hljs.highlight(text, { language: lang }).value;
             return '<pre><code class="hljs language-' + lang + '">' + highlighted + '</code></pre>';
           }
-          const escaped = text.replace(/&/g,'&amp;').replace(/</g,'&lt;').replace(/>/g,'&gt;');
+          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) {
-          const raw = token.raw || token.text;
+          var raw = token.raw || token.text;
           return raw.replace(/\[\[([^\]]+)\]\]/g, function(match, page) {
             return '<a href="#' + page + '">' + page.replace(/-/g, ' ') + '</a>';
           });
@@ -404,33 +411,19 @@ <h3>Support</h3>
       }
     });
 
-    async function loadPage(page) {
-      const contentEl = document.getElementById('content');
+    function loadPage(page) {
+      var contentEl = document.getElementById('content');
+      var md = PAGES[page];
 
-      if (pageCache[page]) {
-        renderPage(page, pageCache[page]);
-        return;
-      }
-
-      contentEl.innerHTML = '<div class="loading">Loading...</div>';
-
-      try {
-        const response = await fetch('wiki/' + page + '.md');
-        if (!response.ok) throw new Error('Page not found');
-        const md = await response.text();
-        pageCache[page] = md;
-        renderPage(page, md);
-      } catch (e) {
+      if (!md) {
         contentEl.innerHTML =
           '<h1>Page Not Found</h1>' +
           '<p>The page <strong>' + page + '</strong> could not be loaded.</p>' +
           '<p><a href="#Home">Return to Home</a></p>';
+        return;
       }
-    }
 
-    function renderPage(page, md) {
-      const contentEl = document.getElementById('content');
-      const html = marked.parse(md);
+      var html = marked.parse(md);
       contentEl.innerHTML = html +
         '<div class="page-footer">' +
           '<span>Source: <a href="https://github.com/kickash/python-snacks/blob/main/wiki/' + page + '.md">' + page + '.md</a></span>' +
@@ -460,27 +453,14 @@ <h3>Support</h3>
     // Hash-based routing
     function route() {
       var page = location.hash.slice(1) || 'Home';
-      if (PAGES.indexOf(page) === -1) page = 'Home';
+      if (PAGE_NAMES.indexOf(page) === -1) page = 'Home';
       loadPage(page);
     }
 
     window.addEventListener('hashchange', route);
 
-    // Preload all pages in the background
-    function preloadPages() {
-      PAGES.forEach(function(page) {
-        if (!pageCache[page]) {
-          fetch('wiki/' + page + '.md')
-            .then(function(r) { return r.ok ? r.text() : null; })
-            .then(function(text) { if (text) pageCache[page] = text; });
-        }
-      });
-    }
-
     // Initial load
     route();
-    // Start preloading after a short delay
-    setTimeout(preloadPages, 500);
   </script>
 </body>
 </html>