Since 18 October, I have been slowly working on making my site more perfect. Not perfect from the context we think of, but from a perspective of complete. Over the past few years, I’ve added many posts and pages, and over time, the weight of it has been a bit harder to maintain.
I’ve recently become enamored by some of the works of Ben Balter, who champions open software, open government, etc. As he uses Jekyll and Github pages, I was perusing his blog for signs of best practices.
I happened upon Travis CI (Continuous Integration). “Travis CI is a FOSS, hosted, distributed continuous integration service used to build and test projects hosted at GitHub.” (Wikipedia) I also happened upon HTML-Proofer, which checks for commonly felt HTML issues: links, images and scripts.
Overall, my website comprises 202 files and 697 unique or external links. When I first got Travis/HTML-Proofer working, I had 96 errors. Over the past 21 hours (starting at 22:51 and finishing at 19:55), I have slowly whittled the errors to zero. That means that every hyperlink has a valid destination, every image that should have an alt-tag is properly tagged, and all the scripts are present.
Thanks to Travis, every time I post new content, I will know within a few minutes if everything checks out. In theory, I should never again have a problem with broken links as long as I use Jekyll on GitHub.
So, the Build passes tests, and the product is more perfect than I could have achieved myself.
Closing out a third year of Audible listening, my year was focused on history.
Have you ever had a time when you wanted to just snap from the stress? I have. And I did. What I did next was fun.
How should an author respond in a legal landscape that expects action?