A case for the simple web

Why a small website sometimes works best as a collection of plain HTML pages.

A small website often has a simple job: show text, a few illustrations and links to other pages. Browsers already provide almost everything that requires. Add extra layers when there is a specific job for them to do.

What a static site offers

HTML holds the structure and content; CSS controls the appearance. An ordinary web server can serve the finished files. Reading a note does not require starting an application, querying a database or waiting for JavaScript.

Moving the site is straightforward: copy the documents and assets. The content remains readable and editable with ordinary text tools.

Simplicity still needs care

A simple setup does not automatically make a site usable. Pages still need readable text, clear navigation, descriptions for meaningful images and a layout that works on narrow screens.

• Links should lead where they promise.
• Navigation should work with a keyboard.
• Images should not get in the way of reading on a slow connection.
• Missing pages need a helpful error page.

When you need more

User accounts, collaborative editing and personalised data require a different architecture. Once there are dozens of articles, a static site generator can keep templates consistent without copying headers by hand.

Start with the content

Write one good page and check it on a phone. Then add navigation and a second piece. Real text reveals design requirements much faster than a collection of empty blocks.