Lemon Wiki Migration: buckyverse.org
Status: Not started
Category: Different site framework (Wiki.js -> Astro+theme)
Spec: See proggy/docs/superpowers/specs/2026-07-30-lemon-wiki-capability-design.md
Current State
| Attribute | Current | Target |
|---|---|---|
| Wiki root | .wiki/ |
.wiki/ (no change) |
| Site location | None (Wiki.js, not Astro) | public_site/ (fresh scaffold) |
| Site framework | Wiki.js | Astro + @r26d/llm-wiki-theme |
| wiki.config.ts | Does not exist | public_site/wiki.config.ts |
| Skill lineage | nvk/llm-wiki plugin only | Same (no change) |
| schema.md | Missing | Default template |
| Wikilink style | Dual-link ([[slug\|Label]] ([Label](path))) |
Bucket-prefixed single-form ([[bucket/slug\|Label]]) |
| Articles | 434 | Unchanged |
Migration Steps
1. Prerequisites
- Ensure working tree is clean (
git status) - Ensure nvk/llm-wiki plugin is installed globally
- Create a backup branch:
git checkout -b pre-migration-backup && git checkout -
2. Preserve existing Wiki.js site
- Identify existing Wiki.js configuration and site files
- Move Wiki.js site code to a backup directory or branch (do NOT delete)
- Document the backup location here: _______________
3. Scaffold public_site/ (fresh)
The lemon_wiki capability will scaffold public_site/ from scratch since no Astro site exists. This is the cleanest migration path.
- Enable
lemon_wikicapability viaproggy sync -
public_site/will be created with all standard files - Run
cd public_site && npm install && npm run buildto verify
4. Add default schema.md
- Copy the default schema.md template to
.wiki/schema.md - Customize entity types for this project's domain (Buckminster Fuller, geodesic structures, synergetics)
5. Convert wikilinks
- Audit current wikilink style: dual-link
- Run wikilink conversion to bucket-prefixed single-form (
[[bucket/slug|Label]]) - Large corpus (434 articles) — automated conversion essential, manual spot-check a sample
- Generate before/after summary of changed files and link counts
- Verify a representative sample of converted links resolve correctly
6. Standardize raw bucket structure
- Audit existing
.wiki/raw/subdirectories against standard buckets (articles, papers, notes, data, repos) - Create any missing standard bucket directories
- Move existing raw content into appropriate buckets if needed (preserve paths in source references)
7. Verify
-
proggy verifyreportsok -
task wiki:devstarts the dev server -
task wiki:buildbuilds successfully - Spot-check 20+ articles render correctly with the new theme
- Wikilinks resolve in the rendered site
Risks
- 434 articles is the second-largest corpus — wikilink conversion needs thorough testing
- Wiki.js to Astro is a full framework switch — content rendering differences are expected
- Some Wiki.js-specific markdown extensions may not render in Astro+llm-wiki-theme
Content Preservation
The following paths must NOT be modified or deleted during migration:
.wiki/raw/(all subdirectories).wiki/wiki/(all subdirectories).wiki/output/.wiki/config.md.wiki/log.md