Export Your WordPress Blog to Jekyll with One Click

jekyll

Jekyll fans are fond of the Ruby-powered static blogging software due to its ease of use and support for Markdown and the Liquid templating engine. With no database to maintain and no comments to moderate, Jekyll radically simplifies blogging. It’s also the software that powers blogging on Github Pages.

Moving content from WordPress to Jekyll is super easy, thanks to the Jekyll Exporter plugin created by Ben Balter. His Jekyll-powered blog is hosted on GitHub, along with his exporter plugin, which has been in development for more than a year. It was recently updated to be even easier to use and is now available on WordPress.org.

The one-click plugin converts all posts, pages, taxonomies, metadata, and settings to Markdown and YAML, which can be dropped right into Jekyll.

Who Needs a Jekyll Exporter?

I think WordPress is the best blogging software out there, but there are some bloggers who don’t want the hassle of comment moderation and all the maintenance that WordPress requires. This plugin is perfect for conveniently transitioning to Jekyll.

It’s also useful if you have created a bunch of documentation for a project on your WordPress site but decide to move the docs to a freely hosted Jekyll-powered site on GitHub Pages. This allows you to manage your documentation with version control and makes it easy for others to contribute.

I have not found Jekyll terribly easy to set up when I’ve worked with it in the past. That’s why this exporter plugin is a huge time saver – it basically does everything for you:

  • Converts all posts, pages, and settings from WordPress for use in Jekyll
  • Export what your users see, not what the database stores (runs post content through the_content filter prior to export, allowing third-party plugins to modify the output)
  • Converts all post_content to Markdown Extra (using Markdownify)
  • Converts all post_meta and fields within the wp_posts table to YAML front matter for parsing by Jekyll
  • Generates a _config.yml with all settings in the wp_options table
  • Outputs a single zip file with _config.yml, pages, and _posts folder containing .md files for each post in the proper Jekyll naming convention

The Jekyll Exporter plugin has no settings to configure. Just click the button and you’ll have all your content exported into the correct format for Jekyll and organized into the right structure.

If you’re having trouble with your server timing out on the export, Balter has ensured that the plugin is compatible with WP-CLI. You can run this command, which also has support for sites where wp-content isn’t in the traditional location:

wp jekyll-export > export.zip

Currently, the Jekyll Exporter is the only one of its kind in the WordPress.org plugin directory. Fortunately, it was created by a reputable developer who knows the ins and outs of using Jekyll after WordPress.

Would you like to write for WP Tavern? We are always accepting guest posts from the community and are looking for new contributors. Get in touch with us and let's discuss your ideas.

4 Comments


  1. With no database to maintain and no comments to moderate, Jekyll radically simplifies blogging.

    First off, how dare you write an article explaining how to move away from WordPress! Secondly, I’m packing my bags and leaving for Jekyll. No comments to moderate? You didn’t have to ask me twice! :D

    Report


  2. I reckon that something along these lines will feature heavily in the future of blogging – use a local copy of WordPress (or other CMS) to write posts and sync it to a static, publicly-accessible version on Cloudfront or whatever. Quite a few people are already doing this, but I think there are several strong arguments for this approach becoming mainstream.

    Report


  3. As a low-frequency-hobbiest-blogger I have often thought about switching to static site. No database management, offline text-editor based writing, no security, no server maintenance, and it’s free.

    There is beating plethora of WordPress theme and plugin and its modularity which brings me back to it.

    My questions is are their any good options to make WordPress more offline friendly?

    Report


  4. Hmmm, first of all, you need Ruby, and I will stop right there. I have no time to learn another language, or find another hosting company supporting Ruby.

    Secondly, no comments to moderate? It’s misleading. They use third-party to handle comments, right? Don’t you need to moderate those comments?

    Thirdly, I don’t think it is easy to use. A regular John/Jan Doe will find hard time to write a post in a text editor, then send it to server for compilation.

    If someone just want to write, don’t want to worry about security and database stuff, wouldn’t WordPress.com be a good option?

    I will stay with WordPress, but thank you for sharing the information about Jekyll.

    Report

Comments are closed.