How we put a guide together.

Start with the original source

For software behaviour, units, standards or security guidance, we prefer official product documentation, standards bodies, and public agencies. Each guide links its relevant sources so you can check a version-specific detail yourself.

We write original explanations and examples. We do not copy whole source articles or publish lightly rewritten product listings. A source can establish how a feature works; it does not prove that a product is best for every reader.

Be specific about evidence

Documentation-based guides explain published behaviour. They are not evidence that we personally used every device or application described. If we publish a hands-on review later, it should identify the device or software version, the testing method, the conditions, and any relevant limitations.

Illustrations on the site are original explanatory artwork. They are not photographs of products we claim to have tested. Example subscription prices are labelled and editable; they are not live offers.

Show how a tool reaches its answer

Calculators publish their assumptions and formulas. We check representative calculations, unit conversions, edge cases and invalid inputs before release. Browser and device differences can still affect interactive features.

The image compressor reports the actual exported file type and size. It does not promise a fixed saving, forensic metadata removal, or lossless results when a lossy output is selected.

Keep dates meaningful

A publication or update date means a page was created or substantively changed. It is not a promise that every third-party interface or price will remain the same. We aim to correct discovered problems rather than silently refresh dates.

Corrections and assistance

AI and other software may assist with drafting and code, but claims and calculations still need an identifiable basis. We do not use automation to invent experiences, qualifications or consensus.

To report a correction, use the contact page with a page URL, the issue, and an official reference or reproducible example. Do not send passwords, private files, or account credentials.