WordPress source plugins

[kennethormandy]

For the sake of getting feedback this, and keeping gatsbyjs/gatsby#5796 active, I’ve updated this RFC for adding subplugins to gatsby-source-wordpress.

WordPress is an excellent headless CMS for Gatsby, but many WordPress plugins require an additional wrapper before their data can be used within Gatsby. Currently, support for a select number of WordPress plugins are built directly into gatsby-source-wordpress:

• Custom Post Types, including those made with Custom Post Type UI WordPress plugin
• Advanced Custom Fields + ACF to REST API
• WP API MENUS
• WPML REST API
• WP REST Polylang

What if gatsby-source-wordpress had a generic way to pull in data from any plugin’s WordPress REST API endpoint?

Read the the full draft here…

Thanks!

[pieh]

I think we can actually move this out of main package, but still ship them by default (at least initially). This would also allow us to validate that our extension points actually do make sense if we would implement ACF (and other things we support) in separate packages that use public wordpress plugin extension points

[pieh]

I think this is very good write up of the issue and we should start thinking about "Detailed design". I will now look into plugin implementation to see what extension points would be needed to be able to move ACF, Menus etc support from core wordpress plugin package and also think about requirments for things like WPML (gatsbyjs/gatsby#10942) or Gravity Forms

[kennethormandy]

Thanks! Just to save the reference, here’s the changes I made to add Gravity Forms support to Gatsby v1.x WordPress plugin that you already reviewed gatsbyjs/gatsby#5599 Not sure if that’s still a relevant example now, but I can port it as a test later on.