About
Author: Barry Johnson
I retired from the World Bank in February 2012, having worked there for 28 years on its financial systems. I led the data warehouse function in the Bank’s Treasury operations for the last decade of that time. More recently, I was also responsible for technical architecture strategies. Before moving to that job in 1984, I consulted with government departments in two Australian states on their land information systems. My work in Victoria became part of its initial Landata state-wide land information system. (I’m sure it has evolved and changed a bit since the early-1980s!)
Contact me via the form on this site.
Acknowledgements
This web site was originally created with Drupal. I spent some time looking at the implementation of it and the more obvious alternatives, and decided I preferred it technically at that time.
And then I spent several years “battling” the Comments that were posted. I opted for them to be moderated from the outset. I also added modules and tweaked all the knobs I could find to try to reduce the spam commentary, but was never able to stem it completely. In the end, it just wasn’t worth it. (There was also not a single worthwhile comment at the time, so nothing made it out of moderation. I’d like to think that’s only because of the obscurity of my little corner of the web, but maybe not …)
In addition, I’d not found the time to master Drupal’s complexity
power.
In the meantime, new options had appeared, and older ones evolved. The option that ultimately appealed, based on what I see as sufficient for now, was regenerating the site as static pages. Of the options of that type, I settled on Markdown-based content, with Hugo as the generation tool.
Initially I tried to keep the original look and feel of the site to a degree. Within my limited HTML+CSS coding skills. Supported by lots of web searching for help. But over time, bit by bit, that has changed. I have even made it more “friendly” (I hope) on smaller screens.
Additional notes about the site and its contents:
I started with browser-based Search using Javascript based on Client side searching for Hugo.io with Fuse.js. I have since switched to a search field that sends the input to a site search via DuckDuckGo on a separate page. Unfortunately the example on that site (at the time of writing at least) uses an HTML
iframefield. I ultimately drew on the results of some searching (and, particularly, previously-linked web pages that seem to be no longer available) to construct the current mechanism. (I may return to something self-hosted, guided by the Hugo documentation, at some point in the future.)The contact form is adapted from Building Sites With Hugo.
The feed icon is courtesy of Feed Icon, but copied to my site and served from there. Other icons are drawn directly from Unicode.
For fonts, the stylesheet uses the generic “sans-serif” and “monospace”. Many web browsers allow the user to select a locally-installed font to the user’s liking for each of these. This might mean I lose some control of formatting, but I decided it was more important for the reader of my web site to be able to pick something they find readable. Because fonts don’t need to be downloaded along with the content, it also makes for more responsive web pages. (For a time I self-hosted fonts, drawn from OpenSans for sans-serif and Hack for monospace. I backed off from that for the reasons cited.)
I also use relative font sizes for different components (headings, captions, …). Again, many browsers allow the user to select a base text size suited to their need, and I want to respect that.
I review content as well as formatting changes (albeit not comprehensively, page-by-page) in:
I have set my desktop browsers’ san-serif font to Arial on the assumption it’s most commonly the default used by viewers of this site.
The change to use DuckDuckGo-based search returns my pages to containing nothing but my content. Including no cookies. (If you find any coming from my site, please let me know.)