We want you to be able to tell, for every article, where a claim comes from and how much weight it can bear. So we stick to a few rules.
We try it ourselves
Before we write about a feature, we set it up. For the WordPress import, we built a WordPress site the way agencies typically build them and moved it to EmDash. For the plugin sandbox, we wrote our own test plugin and ran it on a throwaway site on Cloudflare, which we deleted afterwards.
When we haven't tested something ourselves, we say it comes from the docs or from someone else, and we link the source.
Every number has a source
A number in an article is either one we measured ourselves or one with a link to its source. If it has neither, we leave it out, even when an estimate would make the text read more smoothly.
You can see what we tested with
Every article's header shows which EmDash version it was checked against, for example "Checked with EmDash 1.1". EmDash moves fast, and what is true today may be different two releases from now. That label tells you whether an article still fits your version.
Changes are listed in the article
When we change an article after publishing it, because something changed or because we got it wrong, "Changes to this article" at the end says so, with the date. Small fixes such as typos don't go in there.
We aren't neutral, and we say so
We both help maintain EmDash, and we both build websites with WordPress and EmDash for a living. So we have an interest in EmDash being good. That doesn't stop us from writing down what doesn't work. When a bug sits in code one of us wrote, we say so. And when an article involves one of our companies or one of our own plugins, the text says that too.
Who stands behind it
Every article carries the name of the person who wrote it and stands behind it. Before it comes out, the other one of us reads it through.
If something is wrong
Tell us in the comments under the article or by email to hello@theweeklydash.com. We check it, correct the article and note the change at the end.