I like static websites.

Databases are my friends, too, I admit. And automation, scripting and all that - well, what kind of ERP expert would I be if they weren’t bread and butter?

But websites mostly don’t need to be clever.

Fast, clean and informative - yes.

So we’ve gone static here.

What IS a static website?

Back in the old days of the web, everything was fixed. When you called up a page in your browser, that page existed somewhere on a server, just as if you’d opened a Word document.

These days, mostly the page is created on the fly as you need it depending what you’ve asked for, who you are and what some system thinks you want or might be persuaded by.

Which is a) overkill for most of us, and b) quite inefficient.

Because it’s inefficient, in fact, the best systems go to some trouble to find out what you’re most likely to want and store it ahead of time.

A static website cuts out all that, and goes back to simply storing all the pages you might want.

The cleverness is in the system that generates it in the first place. (This website uses one called Hugo). Once it’s all out there, it’s as simple as it can be.

It should be fast. Is it?

It would be nice to know how you find it.

And if there are any problems, down to spelling mistakes. Let us know.