mitchmac

The plugin creates zip files containing posts converted to Markdown. A WP-CLI command exists to handle exporting sites with a large amount of content.
<ul>
<li>Move WordPress content to Gatsby-friendly Markdown.</li>
<li>Customize the export! Remap and restructure exported fields.</li>
<li>CLI: Avoid PHP timeouts by using the command line with WP-CLI.</li>
<li>CLI: Export progress bar (great for large sites)!</li>
</ul>
<blockquote>
Reminder: always keep a backup of the WordPress database and files in case your export doesn’t work as expected!
</blockquote>
<h3>Working with Gatsby</h3>
If you’re just getting started with Gatsby, we recommend experimenting with a Markdown based Gatsby starter like <a href="https://github.com/tinacms/tina-starter-grande" rel="nofollow ugc">Tina Grande</a>. Installation is as easy as:
<pre><code>git clone https://github.com/tinacms/tina-starter-grande.git

cd tina-starter-grande

yarn install && gatsby develop
</code></pre>
Then copy your exported WordPress Markdown into the <code>content</code> directory or point the wp gatsby-markdown-export command at the content directory.
Want to port your WordPress or HTML theme to Gatsby? Checkout <a href="https://www.gatsbyjs.org/docs/porting-an-html-site-to-gatsby/" rel="nofollow ugc">Porting an HTML Site to Gatsby</a> for tips.
<h3>Command Line Usage</h3>
The command line functionality uses WP-CLI to interact with WordPress. <a href="https://wp-cli.org/#installing" rel="nofollow ugc">WP-CLI is easy to install</a> if you haven’t already.
Once it’s installed, you can export content to a directory like this:
<pre><code>wp gatsby-markdown-export --directory=/example/gatsby-starter/src/content
</code></pre>
All CLI arguments are optional.
 Option 
 Description 
 Default value
 <code>--help</code> 
 get help
 <code>--directory=</code> 
 export output directory 
 random temp directory
 <code>--post_types=</code> 
 post types to export, see: https://developer.wordpress.org/reference/classes/wp_query/#post-type-parameters 
 page,post
 <code>--post_status=</code> 
 post status to export, see: https://developer.wordpress.org/reference/classes/wp_query/#status-parameters 
 any
 <code>--fields_to_markdown=</code> 
 fields to convert to Markdown 
 excerpt
 <code>--excluded_front_matter=</code> 
 fields to exclude from front matter
 <code>--post_date_format=</code> 
 format for post publish date, see: https://www.php.net/manual/en/function.date.php 
 c
 <code>--upload_dir=</code> 
 directory in the export to copy WordPress uploads 
 uploads
 <code>--remap_fields=</code> 
 remap front matter field names, example: find1,replace1;find2,replace2
 <code>--fields_to_array=</code> 
 convert single value front matter fields to arrays
 <code>--include_private_fields=</code> 
 private post meta fields to include (they start with _)
 <code>--skip_copy_uploads</code> 
 flag, skips copying WordPress uploads to the export
 <code>--skip_original_images</code> 
 flag, skips the use of original dimension images
 <code>--skip_enforce_charset</code> 
 flag, skips use of blog_charset for the XML charset
 <code>--create_type_directory</code> 
 flag, creates directories based on post type

WP Gatsby Markdown Exporter

Export WordPress content to Markdown for GatsbyJS.

Jason Bahl

Tyler

David Levine

Ryan Kanner

Geoff Taylor

Edwin Cromley

WPGraphQL is a free, open-source WordPress plugin that provides an extendable GraphQL schema and API for any WordPress site.
Get Started
<ol>
<li>Install WPGraphQL: <code>wp plugin install wp-graphql --activate</code></li>
<li>Try it out: <a href="https://repl.wpgraphql.com" rel="nofollow ugc">Live Demo</a></li>
<li>Read the <a href="https://wpgraphql.com/docs/quick-start" rel="nofollow ugc">Quick Start Guide</a>.</li>
<li>Join the <a href="https://discord.gg/AGVBqqyaUY" rel="nofollow ugc">Community on Discord</a> and <a href="https://github.com/wp-graphql/wp-graphql" rel="nofollow ugc">Star the Repo</a>!</li>
</ol>
Key Features
<ul>
<li>Flexible API: Query posts, pages, custom post types, taxonomies, users, and more.</li>
<li>Extendable Schema: Easily add functionality with WPGraphQL’s API, enabling custom integrations.</li>
<li>Compatible with Modern Frameworks: Works seamlessly with <a href="https://vercel.com/guides/wordpress-with-vercel" rel="nofollow ugc">Next.js</a>, <a href="https://docs.astro.build/en/guides/cms/wordpress/" rel="nofollow ugc">Astro</a>, <a href="https://www.okupter.com/blog/headless-wordpress-graphql-sveltekit" rel="nofollow ugc">SvelteKit</a>, and more.</li>
<li>Optimized Performance: Fetch exactly the data you need in a single query. Boost performance with <a href="https://github.com/wp-graphql/wp-graphql-smart-cache" rel="nofollow ugc">WPGraphQL Smart Cache</a>.</li>
</ul>
WPGraphQL is becoming a <a href="https://wordpress.org/news/2024/10/wpgraphql/" rel="ugc">Canonical Plugin</a> on WordPress.org, ensuring long-term support and a growing community of users and contributors.
<h4>Upgrading</h4>
It is recommended that anytime you want to update WPGraphQL that you get familiar with what’s changed in the release.
WPGraphQL publishes <a href="https://github.com/wp-graphql/wp-graphql/releases" rel="nofollow ugc">release notes on Github</a>.
WPGraphQL has been following Semver practices for a few years. We will continue to follow Semver and let version numbers communicate meaning. The summary of Semver versioning is as follows:
<ul>
<li>MAJOR version when you make incompatible API changes,</li>
<li>MINOR version when you add functionality in a backwards compatible manner, and</li>
<li>PATCH version when you make backwards compatible bug fixes.</li>
</ul>
You can read more about the details of Semver at semver.org
<h3>Privacy Policy</h3>
WPGraphQL uses <a href="https://appsero.com" rel="nofollow ugc">Appsero</a> SDK to collect some telemetry data upon user’s confirmation. This helps us to troubleshoot problems faster and make product improvements.
Appsero SDK does not gather any data by default. The SDK starts gathering basic telemetry data only when a user allows it via the admin notice.
Learn more about how <a href="https://appsero.com/privacy-policy/" rel="nofollow ugc">Appsero collects and uses this data</a>.
Learn more about how <a href="https://appsero.com/privacy-policy/" rel="nofollow ugc">Appsero collects and uses this data</a>.

WPGraphQL


I operate a large blog that uses WordPress as a headless CMS with a Next.JS frontend, which is largely enabled by this plugin. Let me just say first that creating an entire alternative third-party data API is an ambitious undertaking and I appreciate all the work the authors have put into it.



But as a developer I have to throw out a word of caution that this plugin often has major bugs that can have critical impact on your production website. For example after a recent minor update  we discovered a bug where any URL with a special character in it started returning a 404, causing several of our pages to suddenly become unavailable to users and delisted from Google, and this went on for many months before we realized it.



There have been many similar instances. My general approach is to lean more on WordPress's REST API over time which is more reliable since it's maintained by the WordPress team, and only use WPGraphQL when it's necessary.



Also recommend turning off auto-updates and test your website extremely thoroughly after any upgrade.


Unreliable

GraphQL vs. REST API
  10    :     0

Thank you for this plugin. Building my headless application with WPGraphQL is fun. 
The repl interface to test queries is A+.

Speedy

WPGraphQL adds a flexible and powerful GraphQL API to WordPress, enabling efficient querying and interaction with your site's data.

WP Gatsby Markdown Exporter vs WPGraphQL