WordPress to Jekyll Exporter
One-click WordPress plugin that converts all posts, pages, taxonomies, metadata, and settings to Markdown and YAML which can be dropped into Jekyll.
Many shared hosts may use PHP 5.2 by default. WordPress to Jekyll Export requires PHP 5.3 or greater.
If you get an error message that looks like
unexpected T_STRING or
expecting T_CONSTANT_ENCAPSED_STRING, you need to update your PHP version. In a shared hosting environment, you should be able to change the version of PHP used by simply toggling the setting in the host's control panel.
PHP 5.2 lost support from the PHP project itself more than three years ago. You'll need to be running at least PHP 5.3 which adds namespace support (the reason it's breaking), but I'd recommend at least 5.4 (or the latest your host supports) as it's the oldest supported version: https://en.wikipedia.org/wiki/PHP#Release_history
- 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_contentfilter prior to export, allowing third-party plugins to modify the output)
- Converts all
post_contentto Markdown Extra (using Markdownify)
- Converts all
post_metaand fields within the
wp_poststable to YAML front matter for parsing by Jekyll
- Generates a
_config.ymlwith all settings in the
- Outputs a single zip file with
_config.yml, pages, and
.mdfiles for each post in the proper Jekyll naming convention
- No settings. Just a single click.
- Place plugin in
- Activate plugin in WordPress dashboard
Export to Jekyllfrom the
If you're having trouble with your web server timing out before the export is complete, or if you just like terminal better, you may enjoy the command-line tool.
It works just like the plugin, but produces the zipfile on STDOUT:
php jekyll-export-cli.php > jekyll-export.zip
Alternatively, if you have WP-CLI installed, you can run:
wp jekyll-export > export.zip
The WP-CLI version will provide greater compatibility for alternate WordPress environments, such as when
wp-content isn't in the usual location.
The project is licensed under the GPLv3 or later