Editorial policy
Evidence and sources
Official documentation is the preferred reference for product identity, features, pricing, licensing, privacy, and availability. A provider’s marketing claim is not independent evidence that a tool performs well. Follow source links and check the terms that apply to your account and region.
The migrated archive is undergoing an editorial review. A source link alone does not mean every statement in an article has been independently verified. Where live verification is pending, tool overviews avoid current prices, performance scores, and unsupported recommendations.
Internet feedback
Public reviews and discussions can help identify issues to investigate. Before attributing feedback, record its source URL, date, relevant product version, and whether it describes firsthand use. Attribute opinions to the people who expressed them; do not present a few comments as a representative survey. Unverified feedback is not used to invent ratings or a consensus.
Examples and product testing
An illustrative worked example explains a method and is labeled as such. It is not a captured AI response, a benchmark, or proof of hands-on testing. A future product test should identify the date, tool and model, account tier, input, observed output, and limitations so a reader can assess the result.
AI assistance and human judgment
AI assistance is used in preparing this migration and drafting guidance. Generated text is not a source of evidence. Readers should check factual claims and retain responsibility for decisions, especially where health, safety, legal requirements, private data, or money are involved.
Updates and corrections
Publication dates come from the original WordPress posts. An updated date records a substantive editorial change, not a rebuild or a claim that every linked product was retested. Errors should be corrected in the article and its sources; material corrections should explain what changed. The remaining archive review is tracked separately from completed article updates.