How was the site made?

It was made by hand, with absolutely no AI (Artificial Idiot) used anywhere.

I've studied the specifications for writing HTML and CSS, and written the pages accordingly, using a simple, plain text, editor, that does exactly what I tell it to (true WYSIWYG). After that, I use the “HTML tidy” program to neaten up the HTML that I've typed—neat source code makes it easier for checking errors by eye, as well as for future editing. Any pages that use graphics are composed by hand.

I've yet to find any automatic editor that does a good job of authoring pages, and works in the way that I want to. It becomes a fight to get them to do the right thing, not create pages filled with lots of unnecessary code, figure out their peculiarities, and to overcome their limitations. It's much easier to just do the job properly, yourself, in the first place.

The site doesn't use cookies. And I used to have no scripts that run on your browser, but now there is one in the auto-indexer (*). This site should work well on all browsers, and no differently on those web browsers that disable those things (because they're sick of being attacked by bad websites that keep using them against their visitors).

HTTPS is not required to access this site, since the site doesn't do anything that requires the exchange of financial or other confidential information. It can be accessed using HTTP or HTTPS, as desired.

I run an Apache webserver on one of my own computers for testing purposes, before publishing on an outside WWW server (I don't serve the public version of the site directly from one of my own computers). I use SSI to include common menus, etc., across a multitude of pages. It's easier to produce them, that way. And you don't have to update every page when you add more content.

Unfortunately, the current service that hosts my website runs the LiteSpeed webserver instead of Apache, and it is not the drop-in replacement for Apache that it claims to be. It is missing many of the features that Apache has. You are dependent on additional software to provide any of that functionality.

I double-check pages for HTML and CSS errors using validator programs designed for the job. I check for browser behaviour, as well, but don't use them as error checkers (none of them are suitable for that job). Since MSIE isn't available for my computer operating system, and is really bad anyway, I don't test against it very often. (Yes, I'm aware it can be run through emulators, but I'm not interested in doing so.)

All the above is done using one of the free Linux computer operating systems, with free software running on it. Though it can, also, be done using other systems, this is my preference. I have a primer about website authoring in the computing section, which those considering dabbling with website creation might want to look through, to find out what they're in for.

And what does all that mean? It means that the site should (*) work on any browser, on any computer or other device, be quick and problem-free.

NB: Mobile devices (phones and tablets) can be a bit problematic, though. There's the obvious issue of a small screen, and the difficulties of following the right link when there's a cluster of them near each other. Not helped by the way mobile browsers like to play games with font sizing, shrinking things down by ridiculous amounts to fit everything in the screen, instead of letting you scroll around. And other crazy things. It can be a battle to stop them doing that, and then they change their rules and you have to figure out a new way how to win that battle again. One common solution is a simpler and dumber site for mobile devices, and forcing people to do a search for what they want. I try to avoid that.