I Built a Site with a “Page Builder” Called Gutenberg

While large swaths of the WordPress community were protesting the arrival of Gutenberg with mixed feelings, I chose to embrace it early and often, but even late into its development, I felt unable to produce the same level of work my clients expected–so it was always back to the old ways: page builders and custom fields. In fall 2018, I finished a project that relied way heavily on custom fields; it was slow and its admin UI was confusing and it made like 150 custom fields per post, but it worked and looked great. After, though, I paused and I asked myself “am I sure I can’t do this with just Gutenberg?” So I set out to try. Spoiler alert: its possible, and I did it.

In this presentation, I’ll show you the old way vs the new way, and explain how I needed to change the way I do and think about things to deliver an identical site while shucking the crutches of page builders and custom fields and custom templates that has propped up my work for so long.

Building Static Sites with WordPress, Gatsby and WPGraphQL

It’s no secret that WordPress is the most popular CMS in the world.

Gatsby is quickly becoming one of the most popular tools to build static sites, using Node and React.

In this talk, we will explore using WordPress as a CMS for static sites generated by Gatsby.

We’ll cover the benefits of static sites, such as:
– performance
– free hosting
– much lower security risk

Then we’ll cover how to build a basic Gatsby site that gets it’s content from WordPress via WPGraphQL.