Editorial standards

These standards guide source-linked content by Toools maintainers. Older imported listings may contain less detail; source review dates appear only where a documentation review has been recorded.

Policy updated .

Prefer primary sources

For capability, deployment, pricing, and licensing claims, use provider documentation, official pricing pages, and the project's repository or license. A maker submission or imported directory listing is a lead for review, not independent verification.

Separate facts from recommendations

Capability summaries cite their documentation. “When to choose” guidance is an editorial judgment about a task and its constraints. A recommendation is not a benchmark or a promise of results. Hands-on findings should only be labeled as such when the test and its conditions are recorded.

Explain the decision criteria

Evaluate task fit, deployment requirements, maintenance work, data portability, licensing, and cost at intended usage. A tool's stars, votes, or visits are popularity signals; they do not establish quality or suitability.

Make alternatives meaningful

Curated alternatives explain the need each option addresses. Automatically selected products from the same category are labeled as more tools in that category, rather than equivalent replacements.

Use dates honestly

A documentation review date identifies the reference review for that guidance. It does not imply a full product test or continuous monitoring. Visits and outbound clicks are activity counters, not content updates. When no reliable content modification date exists, the sitemap omits it.

Treat prices and licenses as conditions

Check current prices and terms at the provider. A free allowance can differ from production cost, and source-available software is not automatically open source. Where a guide does not verify an exact amount, it uses budgeting questions rather than a fixed total.

Disclose commercial influence

Any paid placement, affiliate relationship, or sponsored recommendation should be disclosed on the affected content. A featured badge indicates an editorial selection and does not by itself substantiate a performance claim.

Corrections

Open a GitHub issue with the page URL, the disputed claim, and an official source. Accepted corrections should update the relevant text and its review record.