Editorial Policy and How Pages Are Tested
How plainjs.com chooses sources, tests every code block in a browser before publishing, dates support claims, keeps the directory honest and corrects mistakes.
This page explains how the pages on plainjs.com are researched, tested, published and corrected.
Sources
Every claim about what a browser does is traceable to a source listed at the end of the page that makes it. Sources are used in this order of preference:
- MDN Web Docs, for the API and its Baseline support status.
- The specification (WHATWG, W3C or ECMA), where the behaviour is in question.
- caniuse, for support in a particular browser version.
- The jQuery API documentation, for what the replaced jQuery call does.
- A library’s own repository, documentation and package registry entry, for facts about that library.
Wikipedia, forums and other tutorial sites are used to find leads, never as the cited source for a fact. A claim that cannot be verified is left out.
Tested before published
Every code block on a rewritten page is run in a headless Chromium browser by the site’s own test harness before the page can be published. The blocks run in the order they appear on the page, against the example markup the page shows. A block that throws an error, rejects a promise or logs an error fails the test, and a page that fails does not publish. The output comments in the code, such as // "hello", are not checked by the harness; a person checks that they are true.
The foot of each tested page says when it was last reviewed and in which browser version the harness ran. Pages are reviewed again twice a year, and after a browser change that affects them; the date changes when they are.
Browser support, dated
A page does not say “works in all modern browsers”. It quotes the Baseline date from MDN for the API it uses, which is the month the last of the major browsers shipped it, with a link to the MDN page. Where a page shows an older way of doing the same thing for browsers before that date, it says so and keeps the older code under the test as well.
The 2015 pages
Fifty pages date from the site’s start in 2015. They are rewritten one by one at their original addresses. Until a page is rewritten, the original is shown with a notice at the top that says what it is. Its code is of its time: it ran in Internet Explorer and does not use what browsers have gained since. Such a page carries no “tested” line, its examples cannot be run on the page, and its date is the 2015 date. The rewrite replaces it in place.
The directory
The facts on a library’s page (size, licence, dependencies, last release, stars, types, CDN use) are fetched from GitHub, npm, jsDelivr and deps.dev by a script, and each page shows the date they were fetched. The script runs monthly. Five gates, applied by the script and not by hand, decide the “No-build verified” badge; the libraries page states them. The one sentence of editorial text on an entry is the only thing a person writes. Listing is free, there is no paid placement, and a sponsored row, if the site ever carries one, will be marked and will not change the facts shown or the gates passed.
What the site does not do
- It does not publish code it has not run.
- It does not invent numbers, dates or browser versions.
- It does not mock jQuery or the people who use it.
- It does not accept payment for coverage.
Use of software and AI tools
Pages carry the byline plainJS editors, which is the editorial byline of the plainjs.com team at the publisher, Webhaus LLC, rather than one person’s name. Research, drafting and checking are done with the help of AI writing and research tools under the direction of that team. Every page is built from the cited sources, run through the test harness, reviewed against the sources by a person, and edited by a person before publication. Webhaus LLC is responsible for everything published.
Corrections
Errors are corrected as soon as they are confirmed, and the page’s reviewed date changes. To report one, use the contact page and name the page, the browser and version if the code fails, and the source that contradicts a claim.