Repository navigation
Publishing to a GitHub wiki
A github-wiki output writes your Markdown into the repository's own wiki
(<repo>.wiki.git), so the docs show up under the repository's Wiki tab with no site, no
branch and no workflow. It uses your git, like the GitHub Pages output, so there is nothing
to configure beyond the repository.
version: 1
outputs:
- platform: github-wiki
direction: to-platform
repo: owner/name # optional; empty means this workspace's origin
content:
- type: markdown
roots: ["."]
template: defaultGitHub creates a wiki's git repository only when its first page is written. Open the repository's Wiki tab and create the first page (anything; it is replaced), then publish. Without it the publish stops with a message saying so.
- Each Markdown file becomes one wiki page named after its first heading
(
# User guidebecomesUser-guide.md). Two documents with the same title get-2,-3. - The top-level
README.md(orindex.md) becomesHome.md. -
_Sidebar.mdmirrors the page tree, so the nesting rules show in the wiki's sidebar. - Links between documents are rewritten to the wiki page names, keeping
#anchors. Images and linked files are published at their workspace-relative paths, and the links to them follow. - Fenced code blocks are left exactly as written.
A wiki is edited by people too, so LoreMaster never owns the folder. It records the files it
wrote in .lore-master-wiki and, on the next publish, replaces or removes only those. A page
somebody wrote on GitHub survives, unless a document of yours has the same page name, in which
case yours replaces it.
lore-master-engine pages check --output N [--exit-code] # would a publish change anything?
lore-master-engine pages publish --output N
lore-master-engine pages build --out DIR --output N # the pages, into a local folderIn VS Code the same output appears in the Storages and Pages views, Sync publishes it and Check remote status compares it with the published wiki.
- One level of folders only: wiki pages are a flat list, so nesting shows in the sidebar, not in the page addresses.
- There is no per-page status in the Pages view for a wiki, only the whole-wiki check.
- A wiki and a Pages site of the same repository are two separate outputs.
-
LoreMaster documentation
- A documentation agent that follows the LoreMaster structure
- ADR: One Go engine, thin editor shells
- ADR: Vertical feature slices, in Go and TypeScript
- Choosing what goes where
- Command line
- Confluence editions: the facts the design rests on
- Confluence tenant for recorded fixtures
- Generators: pages written from your project's artifacts
- Getting started: syncing a workspace to Confluence
- GitHub Action: the docs site in one step
- Publishing to a GitHub wiki
- The MCP server
- Two-way sync: pull remote edits back, conflict when both sides change
- Using the MCP server
- Watch mode