You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
No, but Prismic come with an auto-generated SEO metadata tabs for page types. So, why don't create a SEO compostable that get data from useAsyncData and safely inject in useSeoMeta()?
Hi @luca-smartpricing, I'm thankful for your suggestion and I'm sorry I couldn't get back to you properly back then.
Slice Machine generates some basic SEO fields for you when creating a page type, but since those can be updated, and many times, augmented by users (to add more meta fields for open graphs, Twitter, or schemas), it's a bit tricky to design a "one composable fits them all" solution that would work for all users. With that in mind I think it's better for everyone to write their own composable as you suggested above.
Re: useHead vs. useSeoMeta
useSeoMeta wasn't as powerful when we first wrote these snippets on Slice Machine's end, I'll proceed to update them to this more modern variant ☺
Is your feature request related to a problem? Please describe.
No, but Prismic come with an auto-generated SEO metadata tabs for page types. So, why don't create a SEO compostable that get data from useAsyncData and safely inject in
useSeoMeta()
?In the slicemachine page snippet your code is:
but you don't use meta_image and the correct compostable:
useSeoMeta
.Having a pre made compostable wrapper would be very handy.
Something like this:
The text was updated successfully, but these errors were encountered: