GraphQL (Apollo) data as its own package

[thescientist13]

Type of Change

• New Feature Request
• Documentation / Website
• Improvement / Suggestion
• Bug
• Other (please clarify below)

Summary

Should @greenwood/cli/data, e,g. package/cli/data be it's own distinct package?

Details

There's also the case that it can be its own package (to maintain its own test cases, dependencies, etc) but have it be a direct dependency of @greenwood/cli. Essentially they would be functionally coupled, but benefit by having code logically organized.

Also, for now, we can just alias it as @greenwood/data and that way, if it becomes a package or not, it won't break user land code since the import path will stay the same.

[thescientist13]

I think coming out of #355 this will happen organically.

[thescientist13]

Re-purposing to help solve #418

1. Make data a plugin and something lighter than apollo?
2. update all usages to use @data/client instead of fetch in www/
3. See if data hydration still an issue
4. reduce duplicate graphql calls?