<meta> Component package

[thescientist13]

Type of Change

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

Summary

Coming out of #303 it makes sense to expose a standalone "<meta>" component with a general purpose API that could be used a la react-helmet.

Details

Something like this, ideally opting for a declarative API as a custom element (see #299 for reference)

<meta .title="${title}" .meta="${meta}"/>

• title would be a string for the page's <title>
• meta would be an Array of <meta> tags

Interesting tweet for consideration

In addition, we can now tap into the graph as part of ResourceInterface which means we can get per page data, really really great for SEO. 🤩

Questions

How should we package this, as a standalone package to publish to NPM? If so, will it then need to be a dependency of @greenwood/cli?

Or maybe there's a plugin we could use to pull this in for users through a transitive dependency? Does that mean it's not default?

Could also have this all done via SSR as Resource with an interceptor?