What is a colophon?
A colophon has its roots in book publishing, specifically it is a brief statement containing information about the publication of a book such as an "imprint". They are traditionally printed at the end of books.
On a website there is no "end of the book" so it exists as a single page, or often as a section in the footer of the website.
Indieweb has a definition, specific to web:
A colophon is a useful place to share the principles that govern your website. For instance, if you do not track users, or if you have taken specific precautions to protect privacy, you can list these principles on your colophon.
Technology
The website you are looking at is a static website built with a Ruby based static site generator called Middleman. would forward data to some data broker. I do use some Google Fonts and have downloaded those fonts and serve them myself. I host this website on Digital Ocean (referral link), running a Caddy web server. To manage the website source code I use Git, and specifically I store my Git repositories on a self-hosted instance of Forgejo on my tailnet.
Images are served through an imageproxy service that allows me to serve images at different sizes and optimize them for the web. They are cached in a Digital Ocean Spaces object store.
To edit my website source code I use neovim. When I want to do programming work I use a Jetbrains IDE; specifically PHPStorm, RubyMine, GoLand, and WebStorm.
List of tools and services.
Privacy
I do not use Google Analytics or any other analytics collecting on this website.
I do collect web server access logs.
Approach
You are your own worst critic. Designing your own site can be frustrating. I have redesigned and rebuilt this website a dozen times or more over 20 years. That is part of the fun, to be honest.
As I have gotten older, wiser even, more patient, I am learning to live in the chaos and accept the messiness, the gross CSS I have written, the unfinished ideas, have baked pages. I have stopped trying to "design" my website, outside a very minimal set of typography rules and foundations, a set of colors, and spacing rules.
The overall approach can be summed up as one of subtraction. I try to not add any more than necessary. In fact, I would rather try to remove elements until things work simply.
This iteration of the website has survived the longest. That may be because it has been the easiest to mutate and evolve, due to the overall website structure and architecture. Or it could be I am simply more patient.