Hi there! I am following your tutorial but in here 22:20 instead of getting the error message you get I get this message in the terminal: Component project doesn't exist. I have created a similar block as "tour" set to "Content Type" and called project.
@AustinShelby22 күн бұрын
Since this video, the @storyblok/react package has been updated. I have now updated the project GitHub repository to be on the latest version github.com/AustinShelby/storyblok-nextjs There are a few changes, you need to call storyblokInit only once and use StoryblokServerComponent instead of StoryblokComponent. Hope you can get your project working by following the repository.
@adli22 күн бұрын
@AustinShelby thanks a lot! Much appreciated! I managed to make it work. Hope won't have to make too many changes further on!
@AustinShelby22 күн бұрын
@@adli Awesome to hear that! Let me know if there are any other issues.
@microronyАй бұрын
Thank you so much , the tutorial is amazing. Even better than the all the the official ones.
@joaolima378025 күн бұрын
Man, that was amazing! Congratulations on your work! 👏
@NadaII6 ай бұрын
After being told I'll be suing StoryBlok as of next week, this was perfection. Thank you.
@italonolasco51422 ай бұрын
Amazing, amazing content! I'm working to delivery a new website to a client and the team decide to use the storyblok as CMS. Cost is important when choosing the CMS, and your techniques to decrease the traffic/month are awesome!! It helps me a lot. Thanks.
@LukeRoberts19797 ай бұрын
Amazing tutorial, so clear on instructions not only with storyblok but with nextjs and going into each step with detail. Have subscribed, would love to see more storyblok and nextjs content.
@AustinShelby7 ай бұрын
Thank you for the supportive comment Luke. Is there anything in particular that you want to see in the future?
@leo13gg2 ай бұрын
33:42 I bet John C. loved their local ice cream XD. Btw, nice content! At start I was afraid of using Storyblok for my projects, but its so nice to learn this. Thanks
@AustinShelby7 ай бұрын
GitHub Repository for this project: github.com/AustinShelby/storyblok-nextjs Sign up to Storyblok for free: get.storyblok.com/austin-shelby
@dorjikhandu38983 ай бұрын
Man...this is good
@AustinShelby3 ай бұрын
I'm glad I could be of help!
@sanamnawaz83246 ай бұрын
Thanks very very much, I learned both next and storyblok, it is very helpful, Thanks for your efforts , keep uploading such content
@AustinShelby6 ай бұрын
Awesome to hear that 🤩
@ac540212 күн бұрын
Got the same issue at 20:00, I got 401 Unauthorized instead of 404. I am using NextJS 15.1.4
@ac540212 күн бұрын
I figured it out myself. I chose region Australia so I got to add region to storyblokInit like so: storyblokInit({ accessToken: process.env.STORYBLOK_ACCESS_TOKEN, use: [apiPlugin], apiOptions: { region: 'ap', } }) It is also insteresting that Australia's abbreviation is ap, instead of au.
@andreaaxelsson570419 күн бұрын
Hi! Great tutorial :D I was wondering since the @storyblok/react package has been updated, how do you manage the caching problem now? I couldnt find it in your github repo.
@HowardKitto-g9mАй бұрын
I'm not sure why but for some reason I couldn't get the provider to work because the the init function in layout.tsx doesn't have the components registered the page rendering always fails with "component foo doesn't exist"
@team6ixygo122Ай бұрын
What version of next are you using?
@SuperGeekWorldАй бұрын
this whole code is not working for me. I tried of accessing the content from storyblok in my next.js 15.1.2 , but not even able to get connected. i was hoping this tutorial would help but its not🥺
@AustinShelbyАй бұрын
@SuperGeekWorld Hey what error are you getting? Maybe I can help you fix it
@blankcheckguy694 ай бұрын
if i use storyblok is my site going to be slow af?
@AustinShelby4 ай бұрын
It depends on how you are fetching the data. If you are using static site generation, it doesn't really matter where the data is being fetched from, as the pages will be generated ahead of time. Based on my experience, Storyblok seems to be fast enough, even when fetching the data on a per-request basis.