WPNuxt Meeting Review - 14 May 2024

[yosefeliezrie]

This documents what was discussed at the meeting held between @vernaillen and @yosefeliezrie about the future of the WPNuxt plugin. Here are the initial things I can remember @vernaillen please add issues and other things we discussed that I forget about

Use GraphQL Introspection

• We should use GraphQL introspection to infer schema and data, asking a GraphQL schema for information about what queries it supports.
• this will allow us to infer much of the data, removing a lot of extra queries and fragments and still be type-safe.
• We can also use this to add an abstraction layer so WPNuxt Modules (ones that extend support) don't have to add a ton of extra GraphQL.
• More about this here https://graphql.org/learn/introspection/

Setup Github Org

• if not already setup setup a github org for WP Nuxt this will allow use to seperate all plugin, modules and other things as per issue

** Docker **

• Better document how the current docker is setup and how things will work for people who have are using a hosting company
• ⁠Document how to use the LocalWP app for local dev

WordPress

Gutenberg Blocks*

• Provide Support for Inner Blocks https://github.com/wpengine/wp-graphql-content-blocks?tab=readme-ov-file#what-about-innerblocks

[vernaillen]

Thanks for writing this out and for your feedback about the WPNuxt module, @yosefeliezrie

I think it's better though to create separate issues for each item. That way we can create a respective branche and pull request for each issue and thereby have a better way to follow up on them separately.

Regarding docker and localwp there's already issue #90 and #91
I'll create issues for the remaining items

[vernaillen]

I created these 2 new tickets: #99 and #100

[vernaillen]

I will close this issue now as the suggested features in this discussing have been created as separate issues to work on.

From now on any ideas, feature requests, questions and discussions can be added under the discussions tab