Content Standards

The rules every article on this site is written to. They exist because most CMS tutorial content is written to fill a page rather than to solve a problem.

Every article must be usable

A guide is finished when a competent reader can follow it start to finish and reach the stated outcome without needing a second source. That means stating prerequisites and versions up front, showing every step rather than skipping the obvious ones, and saying what success looks like at each stage.

Specificity over padding

• Exact version numbers, not “a recent version”.
• Real file paths, real configuration values, real commands.
• Actual measurements where we make a performance claim, with the method stated.
• No introductory paragraphs explaining what a CMS is to an audience that already runs one.

Structure

Long guides carry a table of contents. Procedures are numbered steps, not prose. Comparisons use tables. Warnings that can cost a reader their site — anything destructive, anything irreversible — are called out in a warning block before the step, not after it.

Honesty about limits

We state what we did not test, where a method has known caveats, and when the honest answer is “it depends”. If an approach we recommended has a failure mode, it goes in the article, not in the comments.

Where a piece of software is the wrong tool for the reader’s problem — including where the right answer is a different CMS — we say so. We are not here to defend Joomla’s honour.

Titles and descriptions

Titles describe what the article delivers. We do not write titles that promise a definitive answer the article does not contain, and we do not inflate scope. Where a guide is version-specific, the title or the badge says so.

Images and media

Screenshots are taken from the version under discussion and are re-taken when the interface changes. Diagrams are original. We caption anything that is not self-explanatory, and we do not use stock photography of people pointing at laptops to fill space.

Language

Plain English, British spelling, technical terms used precisely and defined on first use where the audience may not share them. No manufactured urgency, no superlatives we cannot support.