Jens Oliver Meiert

Major updates: latest tech book · latest non-tech book · latest optimization tool · latest defense tool

Why I Don’t Like (and Don’t Recommend) Website Checklists

Published on Nov 18, 2026, filed under , , . (Share this post, e.g., on Mastodon.)

There’s the front-end checklist. There’s the website specification. There are dozens of website-related checklists.

Personally—no offense—I don’t like them.

Why?

Quality Websites Are Bespoke—Checklists Are for Bulk

Checklists are built for assembly lines, not individual craft:

They try to standardize specifics. They’re not tailored. They all contain some advice that doesn’t apply.

For a web development minimalist, website checklists are nonsensical:

They want to solve much but do solve little.

Templates are a great example, as we’ve been there—if we only include what we know for certain every website needs, we end up with a template like this:

<!doctype html>
<title>TITLE</title>
<!-- CONTENT -->

More we just don’t know—and the little we do know is useless.

For checklists, it’s not much different: I’ve dissected the front-end checklist back in 2019 and ended with 41 👎s and 13 ✋s. Not great if you’re using a checklist to do a right thing—you’re probably doing a wrong thing.

Accordingly, as a minimalist, I don’t like checklists, I don’t use checklists, and I don’t recommend checklists, not in this context.

No Checklist Can Replace Understanding

Rather, I suggest learning the craft and being consciously and completely clear about what’s truly needed.

There’s no checklist (or template) for that. We have to understand the problem and know our craft to solve it.

If this resonates with you, you might also enjoy my old booklet on HTML/CSS frameworks (updated edition). At the core of this 2010s philosophy on frameworks is the same idea: No checklist, no template, no framework is worth using if it means doing and shipping work that isn’t needed.

About Me

Portrait sketch of Jens Oliver Meiert.

I’m Jens (long: Jens Oliver Meiert), and I’m an engineering lead, guerrilla philosopher, and indie publisher. I’ve worked as a technical lead and manager at various companies (e.g., Google); I’m an active web and tool developer (code optimization, digital defense), a contributor to web standards (like HTML, CSS, WCAG), and a book author (O’Reilly, dxsrc). You’ll like my work if you value principled, pragmatic problem-solving. Let’s connect.