Replies: 1 comment
-
|
Fresh 2.0 brought the <Head/> component back. No longer relevant. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hey, I recently entirely rewrote my blog from scratch using Fresh 2, and I looked at both the migration guide and the code example in the #2363 issue, and I really couldn't figure it out.
My problem is the fact that with the blog, I really only need to edit the title on the pages of the actual articles, and I also need to put a bunch of SEO stuff on both the main page and the pages of the articles.
If I take what is in the migration guide as the source of truth, from what I understand, it means that I need to store all of the head related stuff in a state and define it on every page, even in the cases where I don't need to have the extra headers, which is a bit much.
If I take what is in the issue as the source of truth, it would actually be pretty convenient for me, but I tried to do it in the seemingly same way as with the example code, but it didn't seem to actually touch the
<head>I know that the head api is actually not concrete at all and it may possibly change, but I was just wondering what the real/current/intended approach is for this, because this was my biggest pain point with the switch to Fresh 2.
(Besides this, I find Fresh 2 to be really pleasant and intuitive and I love the benefits it brings me. Y'all have done an amazing job on it and I'm really excited for the release.)
Beta Was this translation helpful? Give feedback.
All reactions