Preparing this site for the 2020s

 29th November, 2018

The new design for this website1, the successor to the Belgravia theme I had been using since 2012, which I’m calling Gramercy, and which I hope you will like, goes live this week. But behind the hood quite a lot has changed beyond the design.

In the thirteen years since I started publishing content on this site, I think I’ve measured up to the challenge I identified in my first online article:

I’m also curious to get to grips with the technical aspects. The Internet, for me, has been the realisation of a childhood dream: making every possible bit of information accessible worldwide. I’m keen that this should not be just a one-way process, and to make my own modest contribution to the system. I hope I’ll be up to the challenge.

The web then was a much less polished place than it is now. Since childhood I had been haunted by the difficulty of sharing thoughts in a paper-based world, and had dreamt of a device that would enable me to be permanently connected.

I certainly jumped into the technicity of the Internet with the alacrity of a novice swimmer jumping into the deep end of the pool. Within a few months, I had learnt html and css, and by the end of the decade I was designing my own themes for my CMS of choice, WordPress. This culminated in 2012 when I wrote a custom theme, which I called, Belgravia, from scratch. I wrote every single line of that theme’s code myself. By that stage, I was using an Apache server that I had entirely set up and was maintaining myself, and using the sharpest-end tools to develop and curate my site design and content. I was so pleased with the design that I did not feel the need to update it for six years.

But the Internet is a very fast-moving place — which is precisely what I like about it, with the challenge posed by wanting to use all the shortcuts and tools in modern web development. As the end of the decade approaches, the complexity of designing a website from scratch has increased vastly: in practice, developing a site in this way, certainly for someone like me, is no longer an option. Most developers — and certainly pretty much all designers now use frameworks. So the new design that went into production on this website this week is a completely different kettle of fish from the previous one:

Another major change I’ve implemented is merging the About page with the Home page. For a while now I’ve felt that a home page in a personal website served no useful purpose, other than as an index of one’s site. Keeping a separate About page actually results in ambiguity as to where about me type links should be sent: to the Home page, since the whole site is really about one, or specifically to the About page? Without going to the extreme of making my site a one-page affair, the Home page now has some more serious content. At the same time, the rest of the site is significantly stripped-down, with just two main areas: Articles (rather than blog posts) and Photos. I’ve also removed quite a few old articles, in order to thin out the content.

I promise to write more regularly, on the same variety of subjects as in the past, for now on as I embark on a series of very exciting new personal projects.

  1. The new Home page, which doubles up as the About page. ↩︎

  2. WP Beginner wrote an instructive post outlining the differences between Genesis and Divi. ↩︎

  3. To put this in perspective, designing the previous theme, the Belgravia theme, literally from scratch took me several weeks in 2012. ↩︎

  4. Media Temple is still an exceptionally good web host, especially for developers who want complete control over their working environment and feel comfortable with the command line. Its support team, all based in California, are one of the best in the industry. But it has gone a long way from its nimble beginnings. It was acquired by GoDaddy in 2013, while its hosting is still superb, it hasn’t been in a position to move as fast as the rest of the industry in the last few years. ↩︎

  5. Kinsta has not disappointed me since I made the switch. Their support team are professional, passionate about WordPress and extremely flexible.An excellent alternative to Kinsta, for those preferring a larger structure, is WP Engine, which also specialises in the WordPress niche but has around 800 employees, compared to Kinsta’s thirty-odd. ↩︎

  6. This is very different from traditional shared, VPS, or dedicated infrastructure: it utilises virtual machines in one of Google Cloud Platform’s multiple data centers. Each machine has up to 96 CPUs and hundreds of gigabytes of RAM. Hardware resources (RAM/CPU) are allocated to each site container automatically, as needed. Kinsta utilizes LXD managed hosts and orchestrated LXC software containers for each site. What this means is that every WordPress site is housed in its own isolated container, which has all of the software resources required to run it (Linux, Nginx, PHP, MySQL). The resources are 100% private and are not shared. And MySQL databases are hosted at localhost, not a remote server. This ensures that there is no latency between machines. ↩︎