Skip to content

EM08 / 09

The Making of This Site

People sometimes ask how a site like this one comes together, and the answer is less glamorous than you might hope. There is no studio and no production crew, just a shared document of ideas, a few writers with their own corners of the subject, and a routine we try to stick to. Here is that routine, from the first question to the moment a page goes live and beyond.

It starts with a question

Most of our topics begin with something ordinary. Someone wonders why their morning smoothie never lasts, or how to paint a bedroom without leaving lap marks, or what a sensible first week of home exercise looks like. We collect those questions from our own lives, from friends and from readers who write in. A topic makes it onto the list when we think we can give a genuinely useful, practical answer without pretending to expertise we do not have.

One writer, one draft

Each piece has a single lead writer who knows the area best. That writer reads widely before drafting, starting with public health bodies, consumer safety organizations and manufacturers' own instructions where a product is involved. The draft is written for a reader who is busy and a little tired, so we favor short sections, clear steps and tables where they help.

Checked by a colleague

Before anything is published, another member of the team reads it through with a simple set of questions. Is every step something a beginner can do safely? Have we claimed more than the sources support? Is there a point where the reader should stop and ask a professional, and have we said so plainly? Anything that reads like a promise, such as "this will cure" or "guaranteed results", is rewritten or removed.

Safety notes are not optional

Health articles carry a note about when to see a doctor. Fitness pieces explain when to check with a professional before starting and which symptoms mean stop. Home projects mention ventilation, protective equipment, children and pets, and how to dispose of leftovers responsibly. These notes are part of the article, not small print, because they are often the most important lines on the page.

No numbers we cannot stand behind

We would rather leave a figure out than guess it. You will notice that our guides rarely quote percentages or doses. Where an exact time, quantity or limit matters, such as food storage or product use, we point you to the label or to your local official guidance rather than inventing a rule of thumb.

Publishing and looking after old pages

Once an article is live, it is not finished. We revisit pages when guidance changes, when a reader spots a problem or when we simply find a clearer way to explain something. Corrections are handled as described on our Spotted an Error? page, and you can see the full range of topics on the About page.

Why pen names?

Every byline here is a first name and nothing more. It keeps the focus on the content and protects the privacy of a small team. It also keeps us honest: with no titles to lean on, every article has to earn trust through its clarity and care rather than a set of letters after a name.

Our working habits

Habits that shape each article

  • Reading before writing

    Public guidance and product labels come first; opinions come later, if at all.

  • A second reader

    Another writer checks each draft for overreach, gaps and missing safety notes.

  • Clear boundaries

    Where general reading stops and a professional should take over is stated plainly.

  • Pages that get revisited

    Older guides are reread and refreshed when advice or reader feedback calls for it.

Before we press publish

The questions every draft has to pass

A short list we run through for each new guide.

  • Could a complete beginner follow every step without getting hurt?
  • Is each claim backed by guidance we can point to, with no invented figures?
  • Does the article say clearly when to stop and ask a doctor or a qualified trade?
  • Are fumes, ladders, allergies and other hazards mentioned where they matter?
  • Would we be comfortable if a friend tried this tomorrow?

Spotted a mistake?

A short note is enough.

Write to the team