Files
gregWiki/docs/reference/wiki-mapping.md
Marvin e2839584f4 Merge Docusaurus site: all content under docs/, align with gregFramework split layout
- Move markdown and wiki-import tree into docs/; keep app shell at repo root
- Point docusaurus docs path to docs/; edit links to mleem97/gregWiki
- Sync and i18n scripts use gregWiki root and ../.wiki under gregFramework
- Sidebars: workspace layout from root docs ids; plugins under mods/extensions
- Fix redirects, module catalog URLs, release note paths, and wiki-import category keys
- Update repo inventory for split repos; Dockerfile for single-repo context

Made-with: Cursor
2026-04-09 23:39:32 +02:00

27 lines
866 B
Markdown

---
id: wiki-mapping
title: Wiki to Docusaurus Mapping
slug: /reference/wiki-mapping
---
## Why this mapping exists
The repository currently stores canonical docs in `.wiki/`. This page defines how those pages are grouped in Docusaurus.
## Audience buckets
- **Newbies**: install/update/troubleshooting, legal basics
- **Intermediates**: hooking, bridge usage, mod config, workflows
- **Pros**: architecture, runtime internals, release system, roadmap
## Suggested migration order
1. Start with onboarding pages (`Home`, End-User, Mod-Developer).
2. Migrate runtime references (`Architecture`, `FFI-Bridge-Reference`, `Web-UI-Bridge`).
3. Migrate governance pages (`Contributors`, Roadmap, Tasklist).
4. Keep bilingual mirrors where needed.
## Sync strategy
Use `npm run wiki:sync` to copy `.wiki/*.md` into a generated docs area for review-based migration.