This tutorial is awesome! I was looking for resources about integrating headless CMS with Next.js and found your video packed with valuable details. Thank you @TuomoKankaanpaa for creating such great content. You earned yourself a new subscriber.
@@TuomoKankaanpaa : Do you have any advice on if your app has more than one route/page? Currently I am unable to use the Navbar for example on the layout.js file so I have to repeat a lot of the code such as adding in nav code and api request to every page 🤔
how would I edit the middleware so that when the user travels between pages they keep the same language ? at the moment if you go to another page the default is english, requiring the user to change between languages on each page load
im thinking of implementing lang support into a project im building... I think my approach regarding this issue will be to change the locale and pass it to a global state (maybe w zustand) and fetch the data according to the state. idk if there are better solutionsm if so please let me know
Good questions! I haven't tested localizing slugs, but I think you can do it with this www.storyblok.com/apps/translatable-slugs. About the locale in the url, I have used them that way in my projects, but on the top of my head I guess you can modify the middleware to store the selected locale somewhere else e.g. cache / local storage, and load it from there.
I have it deployed on Vercel myself, works well! Only thing you need to configure in Vercel is the environment variables SB_TOKEN and SB_DATA_VERSION and you should be good to go!
You are probably the only one who is making detailed technical videos on Nextjs features
Thanks for the comment! Do you like the more technical videos?
@@TuomoKankaanpaa love the in depth tech content
@@TuomoKankaanpaa just out of curiosity, what vscode theme you're using? I like that
@guilhermemm-dev aura dark
Thank you, I was just in need of that specific tutorial, you nailed it!
Great to hear thanks!
Thank you for your tutorial because easy to follow.
Great to hear!
This tutorial is awesome! I was looking for resources about integrating headless CMS with Next.js and found your video packed with valuable details. Thank you @TuomoKankaanpaa for creating such great content. You earned yourself a new subscriber.
Thank you I’m glad to hear that! Great to have you!
awesome exactly what i was looking for! thanks a lot!
You are welcome!
This was a brilliant tutorial!
Great to hear, thanks!
@@TuomoKankaanpaa : Do you have any advice on if your app has more than one route/page? Currently I am unable to use the Navbar for example on the layout.js file so I have to repeat a lot of the code such as adding in nav code and api request to every page 🤔
great Job Man. you are real teacher. I hope you will make a full website of 3, 4 pages in next js14 using Tailwind CSS + i18n
Thanks man!
I will hope boss you will make soon for video of 3, 4 pages in next js14 using Tailwind CSS + i18n@@TuomoKankaanpaa
@mzeeshanfayyaz93 i already have videos using those with nextjs 13, you should check them out, things regarding those havent changed much if at all!
Thank you so much!
Quality content
Thanks! 🙌
Replace "px-52" with "px-10 lg:px-52" on both Testimonials and Faq. Your mobile view will be much better.
Cheers!
@@TuomoKankaanpaaOh. You even see the replies. You have no idea how much this helped me. Thank you so much. Wish you all the best!
Hi Tuomo, thanks for the video! Have you tried using the Storyblok react SDK? And would you know if it's also compatible with Next JS 14?
Is it better option than using contentlayer or sanity?
how would I edit the middleware so that when the user travels between pages they keep the same language ? at the moment if you go to another page the default is english, requiring the user to change between languages on each page load
im thinking of implementing lang support into a project im building... I think my approach regarding this issue will be to change the locale and pass it to a global state (maybe w zustand) and fetch the data according to the state. idk if there are better solutionsm if so please let me know
What about localized slugs? And what if I dont want the /en or /fi slug to be shown?
Good questions! I haven't tested localizing slugs, but I think you can do it with this www.storyblok.com/apps/translatable-slugs. About the locale in the url, I have used them that way in my projects, but on the top of my head I guess you can modify the middleware to store the selected locale somewhere else e.g. cache / local storage, and load it from there.
And what about deploying of this project?
I have it deployed on Vercel myself, works well! Only thing you need to configure in Vercel is the environment variables SB_TOKEN and SB_DATA_VERSION and you should be good to go!
niece
Cheers!