How sources are chosen
Guides cite sources for claims about third-party products, standards and history. We prefer:
- Primary sources. Standards bodies, specification pages and vendor documentation.
- Maintainers. Project pages and release notes from the people who build the software.
- Neutral references. Documentation hubs such as MDN and registries such as the ICC’s.
We avoid blogs that repeat claims, comparison sites that do not show their method, and competitor tool pages.
How sources are used
- Each claim should be traceable. Guides link the source inline, next to the claim.
- We read the source before citing it. If a source cannot be read by us, for instance a page that needs JavaScript or blocks automated access, the guide says so, and tells you to check it yourself.
- We do not invent numbers. Percentages, version numbers and dates appear only if a source gives them.
- Live tables for changing facts. Browser support is linked to a live compatibility table rather than copied.
- Only listed sources. Guides may cite only sources on the list below. Adding one is a deliberate act, recorded in the Changelog.
Known gaps
Some vendors, notably Adobe and Shopify, publish help pages that automated tools cannot read. In those places guides make no claim and send you to the vendor’s current documentation.
Corrections
If a link is dead or says something different from what we claim, write to contact@gohammer.mobi. See also the Editorial policy.
The list
The full list of sources is rendered below this text, with the publisher and link for each.