The author argues that using GitHub wikis for project documentation is an anti-pattern, recommending a /docs folder in the main repository instead. Key reasons include version-controlled docs alongside code, peer review via pull requests, local accessibility, and support for tooling like linting and spellcheck.
Background
GitHub wikis have long been a common choice for project documentation, but many developers prefer keeping docs alongside source code for better maintainability and workflow integration.
- Source
- Lobsters
- Published
- Sep 23, 2026 at 07:48 PM
- Score
- 6.0 / 10