Transvasive Security

the human factor

A New Look for Transvasive Security

Over the past few days, I have been working on an overhaul of I’ve started using GitHub Pages for my safety-related blog,, and have found that I prefer that workflow to the more traditional approach of using a CMS, like WordPress, so I decided to migrate to GitHub. Today, I completed that migration by adding a custom domain and redirecting traffic to GitHub Pages.

From the GitHub Repository, here is the journey of so far:

  1. Originally built on Joomla
  2. Migrated to WordPress
  3. Mirrored using httrack
  4. Converted from html to markdown with pandoc
  5. Cleaned up by hand with Atom
  6. Rebuilt with Jekyll and Poole, forked from information-safety
  7. Tested with Travis CI
  8. Deployed using GitHub Pages
  9. Configured to use a custom domain with Cloudflare

As part of the migration, I edited all of the historical posts, fixing a few typos and restoring broken links. In some cases, the sites referenced are no longer active – those have been replaced with the page stored in the Internet Archive when available.

While I haven’t been posting to transvasive for a few years, I wanted to maintain the site as a historical record (mainly for myself) of my writings. It’s been interesting to read through the posts during the migration and see how ideas I had years ago have evolved and influenced my contemporary work. Although my focus has shifted to safety and resilience, I do have a couple of past presentations to post here, and will post any security-focused content here.

One final note: for a single-person blog, a static site generator is easy to use and much easier to secure. I’d recommend it both for the improved security and for the benefits of being able to manage your content using version control.