Read The Functional Manual: But First We Need to Write It
summary
Argues that documentation must show concrete decisions: uses Haddock + stack to generate docs beside code, adds inline comments, examples and doc-tests checked at compile time, and wires search via Hackage/Google Haskell and Stackage snapshots. Demonstrates a live pull request that documents a confusing expressionFromText binding and lands successfully. Categorizes docs as types, names, usage, tutorials, cites contributions to esqueleto and proto-lens, and notes a $5 bounty incentive for small documentation PRs.
AI-written summary · about
chapters (7)
- 0:00Start
- 24:42Code Blocks
- 25:30Hyper Linking
- 26:24Add Headers
- 34:04Documenting via Usage
- 35:48Examples
- 36:58H Matrix
related talks
43mFOSS DOCS 101 (keep it simple, present!)
01h 11mProject Presentations
47mThe Art of Documentation and Readme.md
35mThe Art of Documentation and Readme.md for Open Source Projects
55mRunning Amok: Igniting a Documentation Revolution
01h 08mYour First Kubernetes Contribution: A Hands-on Guide To Documentation…
35mHelping Your Community Contribute to Developer Documentation
50mOpen Source Survival Guide
