Fact-Checking Policy

Technical publishing fails in a specific way: instructions that were true once, repeated long after they stopped being true. This policy is how we try not to do that.

Source hierarchy

When we make a factual claim we source it, in this order of preference:

  1. Primary project material — the Joomla project’s release notes, security announcements, official documentation and public issue tracker.
  2. The authoritative vulnerability record — the CVE entry and NVD record for any security issue, plus the vendor’s own advisory.
  3. Vendor documentation and changelogs for third-party extensions and templates.
  4. Our own testing — where no published source settles the question, we test it and say that is what we did.

Secondary coverage — other blogs, forum posts, aggregators — is used to find leads, never as the sole basis for a claim.

Verification before publication

Every technical instruction is executed on a real installation before publication. Every version number, price, and compatibility claim is checked against the vendor’s own current material on the day of publication. Every outbound link is followed and confirmed to resolve to what we say it does.

Where a claim cannot be verified, we either leave it out or state plainly that it is unverified and why.

Version stamping

Guides are written against a specific Joomla version, which is displayed on the article. This is not decoration: instructions that work on Joomla 5 frequently do not work on Joomla 3, and we would rather tell you which one we tested than let you find out.

Ongoing review

Articles carry a “verified” date. We re-check content on a rolling basis, prioritising:

  • Anything covering a Joomla version that has just had a major or security release.
  • Security content, which is re-checked whenever the underlying advisory is updated.
  • Reviews and comparisons where a covered product has shipped a major version.
  • High-traffic guides, on a twelve-month cycle at minimum.

When we get it wrong

Report an error to editorial@joomlaxtc.com. We check it against the sources above, and if it stands we fix the article and append a dated correction note explaining what was wrong. We do not silently edit a material error out of existence, and we do not delete the evidence.