Wikis vs Docs

Wikis Versus Documentation in the Repository

Every repository can have a wiki, a set of Markdown pages stored in a separate Git 1,932 repository, booknest.wiki.git, editable in the browser by anyone with write access (or, in a public repository, by anyone on GitHub 29 , if the owner allows it). The wiki repository does not exist until someone creates the first page in the browser:

Enabling the wiki, then trying to clone it before its first page existsShell
gh repo edit binarybehemoth/booknest --enable-wiki
git clone https://github.com/binarybehemoth/booknest.wiki.git
Output
✓ Edited repository binarybehemoth/booknest
Cloning into 'booknest.wiki'...
remote: Repository not found.
fatal: repository 'https://github.com/binarybehemoth/booknest.wiki.git/' not found
A wiki compared with documentation kept in the repository
Wiki Docs in the repository
Where it lives booknest.wiki.git, separate history README.md, docs/ in the code's history
How it changes Direct edits, no review Pull requests, reviewed with the code
Versioned with releases No Yes: each tag has matching docs
Search engines Only with 500+ stars and closed editing Indexed; publishable with Pages (Packages, GHCR and Pages)
Best for Team notes, FAQs, meeting notes Anything a user or contributor relies on

BookNest keeps user documentation in the repository, reviewed and tagged with the code, and the wiki for team notes.