I use the jetpack-markdown WordPress plugin to write my weblog posts in Markdown. Although jetpack-markdown is no longer maintained, it was still available to download using wp-cli. Whilst doing some maintenance on, I discovered this is no longer the case1:

wp plugin install jetpack-markdown --activate
Warning: jetpack-markdown: Plugin not found.
Error: No plugins installed.

With little inclination to research a replacement, I went looking for the source code and was thankful that it’s still online. In addition, the latest version still seems to be available to download2:

wp plugin install
Downloading installation package from                                                   
Unpacking the package...
Installing the plugin...
Plugin installed successfully.
Activating 'jetpack-markdown'...
Plugin 'jetpack-markdown' activated.

  1. From the plugin description: This plugin was closed on April 28, 2019 and is no longer available for download. 
  2. Though who knows how long for? I downloaded the zip and added it to my build process for future use. 

Migrating to WordPress: A brief retrospective

Last year I took the step to migrate content from a Jekyll-powered weblog and a defunct newsletter to a single WordPress-powered instance on

Sharing content on social media platforms is straightforward. I recognised for this initiative to succeed I had to ensure that posting on was just as easy.

To this end, I tailored WordPress to my needs:

  • Removed functionality that was superfluous, a distraction or maintenance burden.
  • Wrote a build script to tear down and rebuild the WordPress instance on Production.
  • Wrote a backup script to create backups of posts and the database.
  • Created a separate repository for the theme, using Vagrant to run the WordPress instance locally. GitLab’s Continuous Integration allows the theme to be updated and deployed to Production automagically.

I’ve been very happy with the results so far.

Separating concerns into three areas: build, backup and theme has worked remarkably well, and though upgrading WordPress and creating backups are currently manual processes, there’s no reason why these tasks couldn’t be automated in the future.

Moving WordPress to a different domain

Your mileage may vary! Please create the necessary backups and test locally before doing anything on Production.

When researching how to migrate WordPress content to, I read the Changing Your Domain_Name and URLs section on the Moving WordPress Codex article but it wasn’t very clear.

Having mentioned this to John, he kindly pointed me in the right direction — here’s what I did:

  1. Install wp-cli on both the old and new WordPress instances (if you haven’t already1).
  2. On the old WordPress instance run wp db export (docs) to export the database as a .sql file (it’ll look something like old_site_wp_database-2018-04-09-bun3e8h.sql).
  3. Transfer aforementioned .sql file to a location on the server running the new WordPress instance.
  4. On the new WordPress instance run wp site empty (docs).
  5. On the new WordPress instance run wp db import /path/to/*.sql (docs).
  6. On the new WordPress instance run wp search-replace (docs).

  1. wp-cli is a really well-designed command-line tool, it made my return to WordPress a great experience. 

Having tested using a stripped down WordPress instance for the past few months, I’ve successfully ported everything over to — though the changes are still propagating across the internet.