Added Serialize override to the docs

[chiedo]

No description provided.

[gatsbybot]

Deploy preview ready!

Built with commit 30241ae

https://deploy-preview-1681--using-drupal.netlify.com

[gatsbybot]

Deploy preview ready!

Built with commit 30241ae

https://deploy-preview-1681--gatsbygram.netlify.com

[gatsbybot]

Deploy preview ready!

Built with commit 30241ae

https://deploy-preview-1681--gatsbyjs.netlify.com

[gatsbybot]

Deploy preview ready!

Built with commit 77fa0f0

https://deploy-preview-1681--using-drupal.netlify.com

[gatsbybot]

Deploy preview ready!

Built with commit 77fa0f0

https://deploy-preview-1681--gatsbyjs.netlify.com

[gatsbybot]

Deploy preview ready!

Built with commit 77fa0f0

https://deploy-preview-1681--gatsbygram.netlify.com

[secretfader]

👍 Thanks for this.

[KyleAMathews]

Looks great!

BTW, @nicholaswyoung it's not altogether clear to me how the top-level query and feeds queries relate to each other.

[secretfader]

@KyleAMathews For future documentation...

My thinking was options.query is effectively a global and is executed once per plugin iteration. feeds[].query is feed-local. Any data returned by feeds[].query is merged the data produced by options.query. Local data has priority.

This setup, while it may be a bit tricky at first, ultimately allows maximum reconfigurability and performance. I designed it when creating multiple (and rather complex) podcast feeds for my site. It's likely that I'll keep refining the API to improve it over time as well.