Editorial Policy

Last updated: August 2026

Yangworks is an independent developer-tools publication run by one person. It has no editorial board, so the policy below exists to make the standard explicit and to make failures visible when they happen.

Every claim is labeled by its source

Technical articles mix three very different kinds of statement, and readers deserve to know which one they are reading:

• Official. Something the vendor states in its own documentation, pricing page, changelog, or announcement. Cited with a URL and the date it was checked.
• Third-party. Something reported by another publication, a community thread, or an aggregate rating. Attributed to whoever said it, and never restated as if Yangworks had verified it independently.
• Author judgment. An opinion, a tradeoff call, or a recommendation. Marked as judgment so it can be disagreed with on its merits.

Where a claim's category is not obvious from context, the article says which it is.

Nothing is published without evidence

Articles move from draft to published only after passing the evidence gate described in the review methodology. In short: hands-on articles have to be backed by something a reader could inspect, and research articles have to say plainly that they are research.

Yangworks does not publish invented numbers. Performance figures, uptime, cost savings, revenue, traffic, rankings, and "I used this for six months" narratives appear only when they actually happened and can be evidenced. When a number cannot be evidenced, the article omits it rather than estimating one.

No conclusion is for sale

• Yangworks does not accept payment to change, soften, or remove a conclusion.
• Yangworks does not sell sponsored posts, paid reviews, link insertions, or guest posts.
• Affiliate relationships are disclosed on the affiliate disclosure page and inside every article that contains a referral link. They do not affect scope, verdict, or ordering.
• Vendors get no advance review of drafts and no approval rights. They are welcome to dispute facts after publication, like anyone else.
• Coverage decisions are driven by what is actually being used or researched here, not by which programs pay.

Independence of infrastructure choices

Yangworks runs on Cloudflare and writes about Cloudflare. That is a real conflict of interest in the ordinary sense: familiarity biases judgment. It is handled by saying so in the articles, by publishing the limits of what was tested, and by not joining an affiliate program for the infrastructure being reviewed. Articles about Cloudflare products on this site carry no commission.

Corrections

Corrections are treated as routine maintenance, not embarrassment. Report an error via Contact with the URL and the contradicting evidence. Verified errors are fixed in the article body, the Updated date changes, and a correction that changes a conclusion is noted in the article with its date. Sources that go dead or stop supporting a claim are replaced or the claim is withdrawn.

AI use

Articles are researched, drafted, and edited with AI assistance, and every published sentence is reviewed by a human before it ships. AI is not used to mass-produce pages, to fabricate test results, or to translate the handbook without human review — each language version of the handbook is checked by a person before its source file enters the build. Facts are verified against primary sources regardless of how the first draft was produced.

Scope and limits

This is a small publication with a narrow beat: deployment, infrastructure, pricing, and the tooling of one-person software businesses. It does not claim comprehensive market coverage, and an absent product is not an implied verdict. Content on this site is information, not professional advice — see the terms of use.