{"id":1896,"date":"2019-07-01T21:22:05","date_gmt":"2019-07-01T12:22:05","guid":{"rendered":"https:\/\/n8finch2024.local\/?p=1896"},"modified":"2019-10-20T06:41:55","modified_gmt":"2019-10-19T21:41:55","slug":"hello-gatsby-this-blog-is-now-headless-wordpress","status":"publish","type":"post","link":"https:\/\/n8finch2024.local\/hello-gatsby-this-blog-is-now-headless-wordpress\/","title":{"rendered":"Hello Gatsby! This blog is now headless WordPress…"},"content":{"rendered":"\n

Well, I did it. <\/p>\n\n\n\n

I jumped on the Gatsby bandwagon, and it seems pretty great so far!<\/p>\n\n\n\n

Also, there’s been a very nice bump in overall site performance and experience (Chrome Lighthouse audits):<\/p>\n\n\n\n\n\n\n\n

\"\"
Before: Previously using the Atomic Blocks theme, shared hosting environment.<\/figcaption><\/figure><\/div>\n\n\n\n
\"\"
After: Using Gatsby, Gatsby Tabor Theme, Gatsby site hosted on Netlify… and a PWA to boot!<\/figcaption><\/figure><\/div>\n\n\n\n

I’m planning to make a quick video of my experience and update this post with it, but I wanted to share what I did here, for reference. <\/p>\n\n\n\n

Disclaimer: <\/strong>I don’t recommend moving your front-end to Gatsby and using WordPress as an API unless you’re working with a developer. I’m sure that WPAABES (WordPress as a back end service, you heard it here!) will be available with themes to choose from soon. <\/p>\n\n\n\n

Steps I Took to Move to Gatsby<\/h2>\n\n\n\n