Editorial Policy & AI-Assistance Disclosure
How articles on this site are researched, drafted, AI-assisted, fact-checked, and updated — and where you should still verify against the official source.
Last updated: May 2026
Who writes this site
A small editorial team of indie developers and long-time AI-tooling users. Between us we ship side projects across web, mobile, and content — so every tutorial here was first written to solve a problem we actually hit, not to chase a keyword. See the About page for the full team background and contact details.
How a typical article is produced
- Problem first. We start from a real workflow gap — either one we hit ourselves or a recurring question we see in forums, Discords, and search queries.
- Hands-on research. We run the actual tool, prompt, API call, or troubleshooting step on a real account or project. If a step doesn't work in practice, it doesn't ship.
- AI-assisted drafting. We use large-language-model assistants (Claude, ChatGPT, and similar) to help structure outlines, translate between English and Chinese, and turn rough notes into coherent prose.
- Human edit and fact-check. Every draft is reviewed by a human editor before publication. We verify model names, version numbers, pricing, command-line flags, and any quoted policy text against the vendor's official documentation at the time of writing.
- Publish with timestamps. Each article exposes a published date and, when revised, an updated date. The dates are real, not auto-bumped.
Use of generative AI
We disclose this clearly because Google, advertisers, and many of our readers reasonably want to know:
- Drafting assistance. Generative AI is used as a writing partner for outlining, rephrasing, translation, and summarisation. It is not used to fabricate factual claims, benchmarks, prices, or quotes.
- Cover and OG images. Article cover images and social-preview cards are programmatically rendered from article metadata (title, category) using Satori. They are graphical templates, not photo-realistic generations.
- Code samples. Code snippets are tested, or adapted from official documentation and marked accordingly. AI assistance may have produced the first draft; a human verified that the final snippet runs.
- What is not AI-generated. Editorial opinions, recommendations, ranked comparisons, and "we ran into X" anecdotes reflect the editorial team's hands-on experience.
Sourcing and citations
For any factual claim that could change — pricing, model versions, free-tier quotas, platform policy, rate limits — we either link to the vendor's official documentation or note the date the claim was verified. If a vendor's docs disagree with us after publication, the vendor wins; please flag stale content via the email below.
Corrections policy
If you spot an error, email us at liziang1997111@gmail.com. Substantive corrections (anything that changes the meaning of the article, not a typo) are made in-place and the article's updated date is bumped. We do not silently revise published recommendations.
Independence and funding
This site is funded by Google AdSense display ads and a small number of disclosed affiliate partnerships for tools we already use ourselves. Affiliate links are individually marked with an Affiliate badge and follow FTC disclosure rules. We do not accept paid placements that would change a recommendation. See the affiliate disclosure for the full breakdown.
What this site is not
This site is independent and is not affiliated with OpenAI, Anthropic, Google, Apple, Microsoft, or any of the other vendors whose tools we cover. Articles about their products are independent walkthroughs, not official statements. See the disclaimer for category- specific caveats (finance, careers, App Store review, AI-generated media licensing).
Contact
Editorial inquiries, corrections, and feedback: liziang1997111@gmail.com.