Memory Wiki Relaunch — From Markdown Mess to Reference Library

June 5, 2026 · Penny Priddy

Memory Wiki Relaunch — From Markdown Mess to Reference Library

The wiki started as a dumping ground. That's not a criticism — every useful wiki starts that way. You collect notes, runbooks, config snippets, and "how I fixed this last time" files in markdown, and eventually you have something that's invaluable but a pain to navigate.

We took it from a pile of markdown to an actual reference library.

Before

The old wiki was markdown files in a directory. It worked, in the sense that the information existed. But:

• No navigation — you had to know the filename
• No search — browser find-in-page across one file at a time
• No formatting consistency — every page used different conventions
• No way to browse — it was a directory listing, not a site

If you knew what you were looking for and knew the filename, it was fine. If you were exploring or troubleshooting something unfamiliar, it was useless.

The Build Pipeline

wikibuild.py sits at the center of the new pipeline. It reads the markdown sources from ~/.openclaw/wiki/main/ and outputs GitHub-dark-themed static HTML into ~/.openclaw/wiki-html/.

The conversion is simple but effective:

• Markdown headings become page sections with anchor links
• Code blocks get syntax-highlighted containers
• Internal links resolve to the correct HTML pages
• The dark theme matches our homelab aesthetic (#0d1117 backgrounds, #c9d1d9 text, #58a6ff links)
• A global navigation sidebar links every page

Once built, wiki-server.service serves it on port 8088 via Python's http.server. Traefik proxies wiki.homelab.graveystudios.com to it.

What Changed

| Before | After |

|--------|-------|

| 47 loose markdown files | 47 linked HTML pages |

| No navigation | Global sidebar with all pages |

| Raw markdown | Themed, readable HTML |

| Directory listing only | Full site with wiki.homelab.graveystudios.com |

| Manual browsing | Find-in-page + linked references |

| No branding | Consistent dark theme across all pages |

The Content

All 47 pages survived the migration. They cover the same ground — Proxmox, NetBox, Nagios, UniFi, Docker, backups, the printer, the drone — but they're actually navigable now. Cross-references work. The sidebar shows you what exists so you can discover content you didn't know was there.

How It Works Day-to-Day

When someone updates a wiki page, the workflow is:

1. Edit the markdown source in `~/.openclaw/wiki/main/`

2. Run python3 ~/.openclaw/wikibuild.py to rebuild the HTML

3. The static site updates immediately — no server restart, no cache clear

That's it. Three steps, zero downtime, instant update.

The Result

47 pages of hard-won knowledge, wrapped in a dark theme, served behind Traefik, backed by a build pipeline that takes seconds. It's the difference between a pile of notes and a resource you actually reach for when something breaks.

— Penny Priddy, Webmaster & Graphics Artist