---
title: Author a public wiki
description: Structure the Markdown pages and Menu that a published Knowledge Base serves on the web.
owner: markus
last-reviewed: 2026-09-11
---

# Author a public wiki

A public wiki turns your maintained pages into a website with a clear reading order.

Put the public home page at `wiki/README.md`. Other Markdown pages under `wiki/` use lowercase letters and numbers separated by single hyphens in each folder and filename, such as `wiki/getting-started.md` or `wiki/guides/import-files.md`. A folder's `README.md` becomes that folder's page. Choose either `wiki/guides.md` or `wiki/guides/README.md`: they claim the same public address, so a collision prevents both from being published there.

Add `wiki/nav.yaml` to define the Menu. Schema 2 supports ordered sections and nested groups. Page labels come from each page’s `title` frontmatter, so changing a title updates navigation without duplicating it in the manifest. Preview a generated plan with the `generate_nav` MCP tool before explicitly applying it.

Add a `description` string to a page’s frontmatter to choose its summary in search metadata and `llms.txt`. A nonempty authored description is preserved. Otherwise, the reader uses the first substantive public prose paragraph, shortened at a word boundary to at most 200 Unicode characters. Headings, code, tables, HTML, images, and navigation are not summaries; a page without prose has no generated description. Static page metadata identifies the page and its Knowledge Base without inventing authors or publication dates.

Use relative Markdown links between pages. The public reader follows the Menu for **Previous** and **Next**, offers an **On this page** outline on wider screens, and includes **View as Markdown** below the article.

Reference images by their relative path in the same public Knowledge Base. Preserve filename case: `Screen.PNG` and `screen.png` are different paths. The reader serves a thumbnail or medium rendition; it does not publish the original image. External images remain links, and missing or unsupported images must not carry essential instructions on their own. See [Images and other assets](https://atmina.ai/docs/images-and-assets) for upload and preview limits.

Publishing makes the public collection available for anonymous search and reads. It includes published pages and their permitted referenced assets by default; a link to another document does not publish that document. Owners can explicitly include additional folders, but only eligible `wiki/` Markdown becomes website pages. System exclusions, original-Asset restrictions, and media verification still apply. Review [Publish a Knowledge Base](https://atmina.ai/docs/publish-a-knowledge-base) before switching visibility.