Photo by Marvin Meyer on Unsplash
We've reached the end of our blog series, so what have we learnt?
- Gatsby has a great starter template that is highly performant (
gatsby new). Whilst it's React based, the organisation of resources (components, images, pages, templates) made it fairly intuitive to edit or create new items. - The build system allows you to get immediate feedback on your changes via live reloading. (
gatsby develop) - The Gatsby plugin ecosystem is healthy and provides us with many ways to pull in content to our site.
- The builtin GraphQL explorer (GraphiQL) allow us to query the WordPress data that we pulled in.
- The Gatsby APIs are powerful, but we didn't get overwhelmed by them as we only needed to know about
createPages. - Netlify took a lot of the hard work in continuously deploy new versions of our site.
- Using webhooks we can wire up WordPress and our site on Netlify.
In case you're still puzzling over the blog post title: Keeping it cheap and staying in touch.
- We kept it cheap by using a free blog on WordPress.com and free hosting via Netlify.
- We stayed in touch by using the webhook on event feature that comes with WordPress.
There's still so much we haven't covered:
- Creating pages based on tags, categories, media, users, taxonomies or custom post types.
- Provide replacements for shortcodes, user comments and search.
- Image processing (which in turn requires the use of the ACF Entities (Advanced Custom Fields) WordPress Plugin).
- Authentication to have content for signed up members of your site.
Thank you for finishing this series! Please let me know if there are other topics you'd like me to cover around the Gatsby WordPress plugin.
To go to another part of the series, click on any of the grey dots below which is next to the current marker (the black dot).
Top comments (1)
Thanks for the series .