Editorial Policy

Antler's documentation is written by reading public repositories and writing original prose, diagrams, and architectural analysis in our own voice. We do not copy upstream README or documentation text wholesale. Short code excerpts (interfaces, signatures, examples) are clearly attributed and are governed by the relevant upstream license.

Every project page states its source repository, the tracked branch, a pinned commit, and a "last reviewed" date. Documentation is fact-checked against that pinned commit; when upstream changes, we re-review and update the pinned commit and date.

Antler is an independent showcase. The teams behind documented projects have not reviewed or endorsed this content, and every page carries a third-party documentation notice. We never imply an "official" relationship.

We report each project's license as stated in its repository (for example, BUSL-1.1 for source-available projects) and describe source-available projects as such rather than as open source.

Every documentation module includes a "Report an error" link that opens the upstream repository's issue tracker with the module pre-referenced. Reported errors are reviewed and, when confirmed, corrected in the documentation.

The "Ask Antler" assistant answers only from Antler's published documentation, cites its sources, and is instructed not to invent answers. It can still be wrong — answers should be verified against the cited modules. User questions are not used to rewrite documentation.

Sponsored listings are disclosed on the Sponsorship Disclosure page. Sponsorship does not change the editorial standard described here.