About these docs
How Lantern's documentation is written, reviewed and kept honest.
Every page has a name on it
“An unowned documentation page rots within a year. Putting a maintainer's name on it is the cheapest accuracy mechanism we have found.”
Lantern's documentation is 240 articles maintained by seven people, each responsible for a named area. Every page carries a last-reviewed date rather than a last-updated one, because 'updated' usually means somebody fixed a typo and tells you nothing about whether the content is still true.
Anything not reviewed in twelve months is flagged automatically and appears on an internal dashboard until someone either confirms it or rewrites it. About a fifth of these articles began as a support reply, on the principle that if a user had to ask, the page was not good enough.
Three rules for the docs
Applied to every page, including the ones nobody reads.
Written as symptoms, not causes
Troubleshooting pages are titled with what the user sees — "401 despite a valid key" — not with our internal explanation of it. People search for what happened to them.
Old versions stay published
Every minor version back to v2.0 remains at its own URL and is never edited after release. A link saved in 2029 still shows what was true then.
Breaking changes get ninety days
Announced at least ninety days ahead, never in a patch release, and we email affected accounts rather than assuming anyone reads the changelog.
Maintainers
Each area has one named owner, listed on every page in it.
Priya Raman
API reference, webhooks
Tomas Lindqvist
Guides, migrations
Amara Osei
Troubleshooting
Dan Whitfield
Getting started, billing
Found something wrong?
Every page has an edit link that opens a pull request. The feedback widget reaches the same maintainer.
Contact support