More Pablo

About (this site)

The cobbler’s children have no shoes. This site, like many of my projects, is a bit of an embarassment for a Professional In Software. That said, I spent far too long on this iteration of it so I’ll write it up here.

Content

The repo for the site is hosted on GitHub here. It’s a generated static site, a la Jekyll or Octopress. I’m using Frog, for a few reasons:

I used Jekyll previously, but its original author heinously mismanaged GitHub and was a petulant little asshole about his deservedly shameful exit. I’ll follow Julie’s advice and not associate with him or his work if I can help it.

I’ve written before about various other blogging engines and approaches I’ve used over the years, and while I think my preference is for a self-hosted out-of-the-box system like Ghost, its generally not worth the trouble of migrating at this point 😛

Hosting

I used to do something ridiculous, which was host this on Google Cloud (my old team!) using Kubernetes. I did this mostly because this site is a safe sandbox to futz around with things I want to learn, and I had no experience with containers. Prior to that it was on a Linode; I left after they were supremely embarassing about security. I used CloudFlare for easy SSL. There might be drawbacks to this, however.

Nowadays, I use a full AWS stack of S3, CloudFront, and Route 53. A decent guide to do this is here.

Styles

I read the CSS book by the authors way back in 2006, when blue beanies were a thing and web standards was still something of a fight (such was my perception, anyways). Which is to say, I knew what CSS looked like and float was probably the most advanced thing that I remembered (that, and that to center something dynamically, was margin: 10px auto;).

So when I was rebuilding this, I was looking at other sources and more or less losing my mind. Has science gone too far? What is this text-rendering property? vh as a length descriptor?!?

I can’t say I’ve really learned this deeply, and you can now see how well I did. After a bit of bonking my head, I got through this basic process:

I found this guide (part two here) a pretty great read on these topics, too.

Perf

If you run a site, there’s a good chance you can find something you didn’t know by running it through Google’s PageSpeed Insights and Google’s Mobile-Friendly Test. You should also consider running any PNG’s through Zopfli or something similar (PNG compression described very well here).

One of my favorite people in the space of site performance is Ilya Grigorik, so I highly recommend checking out his stuff.

This, as the previous section, is massive overengineering for this pathetic little site, but then you may just smile a bit wider when you look in the mirror in the morning 😄

Accessibility

I’m pretty new to this, but it’s a good idea to run your sites through something like a11y, AChecker, or WAVE. a11y Project has some great resources as well.

In Conclusion

Use Squarespace.