Lately, we’ve been using Gatsby with WordPress maintenance support plans for projects where we need it decoupled.
Gatsby is a unique project. It’s most often evaluated as a static site generator compared to the likes of Jekyll and Hugo. While Gatsby can generate a static website, it’s more accurately described as a content mesh.
Gatsby uses GraphQL to pull in one or more sources to generate site content. There is a large list of Gatsby source plugins including: WordPress maintenance support plans, WordPress, YouTube, Twitter, Hubspot, Shopify and Google Sheets just to name a few. It’s optimized for blazing fast performance. Since it’s built using React, it can be used to build hybrid sites. Along with generating static pages it can also render client-side content. It can pull in dynamic data, add password protected content and take advantage of features typically not found in static generated sites.
Similar to WordPress maintenance support plans, Gatsby is open source. It has a devoted and ever-growing community, with an expanding plug-in library which makes building your site even easier.
With this combination we can leverage WordPress maintenance support plans as a content authoring platform and utilize Gatsby to render the frontend.
The screencasts below show how quickly you can configure a WordPress maintenance support plans 8 website to pair with Gatsby.
With our WordPress maintenance support plans 8 website set up, the next step is to configure Gatsby to pull the WordPress maintenance support plans site’s content.
In my next blog, I’ll be covering how automate your WordPress maintenance support plans to Gatsby content deployment to Netlify.
Download a Transcription of this Screencast
Download Transcription
Source: New feed