Weblog Worklog


See this for more on worklogs.

Project motivation

Web develoment was how I first got into programming, many years ago. My ISP served every user’s home directory- something like http://myisp.com/~mylogin/ - and I would FTP files up to it. PHP was my first “production-grade”1 programming language, after Logo; some of my first projects were on a LAMP stack.

The Web has changed a lot since those days. Encrypted connections are standard, client-side and server-side dynamic content, and cheap-to-free hosting from all sorts of companies (including my employer). The industry has an increased understanding of how to design for [accessibility], and there’s a plethora of tools for analyzing all sorts of site attributes. Importantly, there’s lots of resources for learning how to build for the modern web - including building outside of any particular platform.

As my career (and interests) have taken me towards the “back end” of computer systems, my site hasn’t kept up with the modern web. I’ve held on to cceckman.com as a placeholder - reserving my usual handle in the DNS, but serving only unstyled, handwritten HTML.2 That’s been mostly fine- the site has done what I wanted it to do.

But over the last few weeks-to-months, I’ve realized that I want more of a web presence, for a few reasons:

Website worklog

So, with all that said: here’s the worklog for this site.

Platform and tools

Had heard of Hugo; seems to fit the bill:

Work items

  1. In the sense of “used in production” and “not designed for education”. There are plenty of reasons why one might avoid PHP. ↩︎

  2. I won’t claim this site is great on accessibility yet- but I did change the color scheme from the original red on green to this more legible contrast. Please forgive me; I was very young and very foolish. ↩︎

  3. There seems to be more writing on “why and how to make your own website” at IndieWeb. Link is not endorsement; I haven’t been through much of that site, just am aware of its applicability here. ↩︎