Hey, This is awsome. I've been needing to make a setup video for awhile now but keep putting it on the long finger 😅 You've done a much better job on it than I ever could!
Hi do you have much experience with nuxt? In terms of SEO the basics are covered with meta tags, sitemap and robots.txt however Scott is working on full Yoast SEO compatability from what i can see in the docs.
Hi are you familiar with any Javascript frameworks (i.e. Next JS)? Nuxt is Vue based so very easy to pick up if you are comfortable with code. I would recommend getting started with learning the base workflow with Vue then begin reading the documentation around Nuxt. Vue school offers some excellent content.
Awesome, thank you for taking the time into creating this video. I am looking for a solution for a efficent headless e-commerce. I am coming from Webflow/Wordpress-Bricks background more as a no-code person, although I am getting more familiar with coding thanks to AI.
Great and thanks for the comment. I fell in love with Nuxt after working with it and WooNuxt is a fantastic boilerplate to spin something up fast and see how it all clicks together. But be mindful the this has been built with standard products and variable products in mind and so if you intend to use customer product types then there will be modifications needed. Best of luck on your journey and let me know if you need some help.
Hi nope this is how you build a website using nuxt and woocommerce. This isn’t a page builder but a JavaScript framework so you definitely need to be proficient in code. Very cool but if you are not at that level yet then bricks is a fantastic base.
We are experiencing an issue where users are unable to log in using the Safari browser. Have you encountered this problem before? Thank you in advance for your response.
Hi I haven’t unfortunately but it’s probably todo with CORS policy or cookies.. Safari is stricter with these so could be there is an issue with your configuration. I’m away on holidays at the moment so can’t run any tests. Fingers crossed that helps.. let me know
Hi there. The benefits of headless really depends on the brand/company. For most websites the more traditional approach is suffice and going headless introduces complexity and costs that are not necessary for small to medium sized companies and specifically companies that require a heavy scoop of DIY maintenance. However for sites that are growing and increasing in complexity then decoupling the frontend from the backend is a excellent way to get control over security, solidify version control via git, allow for development to be distributed/tracked amongst teams easily and (for me personally) being able to use a frontend framework with an AWESOME developer experience (i.e. Nuxt). In addition moving headless will reduce the number of plugins needed on a Wordpress/Woocommerce website which has a maintenance, cost and security implication. But again its very dependent on the client/brand and the costs you save on a plugin won't necessarily hit your back pocket as you are moving those funds into additional hosting (i.e. Netlify or Vercel) and you have increased complexity of the development. However that said Nuxt comes with some amazing modules which are super simple to setup (for a developer) and really streamline the dev process so for example if a client is using gridbuilder to do a carousel then in Nuxt you can one click install swiper.js. Now one major benefit is performance out of the box, when you use a frontend framework like Nuxt you get automatic code splitting, static or hybrid rendering and your website is being served by cdn's without having to render each page on the server for every navigation which means in-website navigation and performance is greatly increased. In response to this specific video. The benefits here is you get to have "your cake and eat it" so to speak. So for example if a client/brand has and existing WooCommerce website and there is a desire to stay within the platform (resistance to change for example) then we are able to retain the CMS, reduce/nullify team training, and utilise a front end framework like Nuxt with a signifiant reduction in dev hours as allot of the heavy lifting has been done for us thanks to WooNuxt. I hope that helps answer your question, but like anything really it's not a one size fits all approach and is a tool to be used when/if required. I personally love headless but we also use no-code solutions, page builders, and custom + customised themes based on whats right for our clients (i.e don't use a bazooka to squash a fly).
Originally, the reason I started this project was when I was working on a client project ( an influencer with a large following) the original site no matter how much we optimized it would still crash when there was a launch of a new product. Thousands of people queuing up to buy what was on offer before it sold out. WooNuxt takes a massive load off the server. So Performance is a big one. Also having a modern front end can have a very rich user experience for the customer. The ability to have a PWA is a big one. This also opens up the option to put something like capacitorjs on top of it and have a mobile app. It basically opens a lot of doors.
![Deploy a Django web app to Vercel [FREE]](http://i.ytimg.com/vi/ZjVzHcXCeMU/mqdefault.jpg)
There's literally only this video on the whole internet about WooNuxt.
Yeah and WooNuxt is so good.
Hey, This is awsome. I've been needing to make a setup video for awhile now but keep putting it on the long finger 😅 You've done a much better job on it than I ever could!
Well you did the hardest part.. excellent job. FYI your vercel deployment links go to a old repository I think, so deployment breaks
@@AlternatePro Thanks for the heads up. I'll take a look 🤙🏻
Would love to see how you customize WooNuxt and get a feel for the DX.
Thanks Jason I’ll add it to the todo list. If you know Nuxt then you will love it.
Thanks for this tutorial! Seems quite easy to setup. I'd be interested to know how to customize the pages and how to optimize for SEO
Hi do you have much experience with nuxt?
In terms of SEO the basics are covered with meta tags, sitemap and robots.txt however Scott is working on full Yoast SEO compatability from what i can see in the docs.
Hi i have no experience in Nuxt. What do you recommend to get started with Nuxt?
Hi are you familiar with any Javascript frameworks (i.e. Next JS)? Nuxt is Vue based so very easy to pick up if you are comfortable with code. I would recommend getting started with learning the base workflow with Vue then begin reading the documentation around Nuxt. Vue school offers some excellent content.
Awesome, thank you for taking the time into creating this video. I am looking for a solution for a efficent headless e-commerce. I am coming from Webflow/Wordpress-Bricks background more as a no-code person, although I am getting more familiar with coding thanks to AI.
Great and thanks for the comment. I fell in love with Nuxt after working with it and WooNuxt is a fantastic boilerplate to spin something up fast and see how it all clicks together. But be mindful the this has been built with standard products and variable products in mind and so if you intend to use customer product types then there will be modifications needed. Best of luck on your journey and let me know if you need some help.
Does it work well with bricks builder ?
Hi nope this is how you build a website using nuxt and woocommerce. This isn’t a page builder but a JavaScript framework so you definitely need to be proficient in code. Very cool but if you are not at that level yet then bricks is a fantastic base.
We are experiencing an issue where users are unable to log in using the Safari browser. Have you encountered this problem before?
Thank you in advance for your response.
Hi I haven’t unfortunately but it’s probably todo with CORS policy or cookies.. Safari is stricter with these so could be there is an issue with your configuration. I’m away on holidays at the moment so can’t run any tests. Fingers crossed that helps.. let me know
WooCommerce + GraphQL = instant DoS endpoint
Yes but good server security and using custom authentication token with env to validate requests to graphql can help mitigate this.
Where is the full tutorial ?
Hey. It’s on the todo list.
what's the major benefits?
Hi there. The benefits of headless really depends on the brand/company. For most websites the more traditional approach is suffice and going headless introduces complexity and costs that are not necessary for small to medium sized companies and specifically companies that require a heavy scoop of DIY maintenance.
However for sites that are growing and increasing in complexity then decoupling the frontend from the backend is a excellent way to get control over security, solidify version control via git, allow for development to be distributed/tracked amongst teams easily and (for me personally) being able to use a frontend framework with an AWESOME developer experience (i.e. Nuxt).
In addition moving headless will reduce the number of plugins needed on a Wordpress/Woocommerce website which has a maintenance, cost and security implication. But again its very dependent on the client/brand and the costs you save on a plugin won't necessarily hit your back pocket as you are moving those funds into additional hosting (i.e. Netlify or Vercel) and you have increased complexity of the development.
However that said Nuxt comes with some amazing modules which are super simple to setup (for a developer) and really streamline the dev process so for example if a client is using gridbuilder to do a carousel then in Nuxt you can one click install swiper.js.
Now one major benefit is performance out of the box, when you use a frontend framework like Nuxt you get automatic code splitting, static or hybrid rendering and your website is being served by cdn's without having to render each page on the server for every navigation which means in-website navigation and performance is greatly increased.
In response to this specific video. The benefits here is you get to have "your cake and eat it" so to speak. So for example if a client/brand has and existing WooCommerce website and there is a desire to stay within the platform (resistance to change for example) then we are able to retain the CMS, reduce/nullify team training, and utilise a front end framework like Nuxt with a signifiant reduction in dev hours as allot of the heavy lifting has been done for us thanks to WooNuxt.
I hope that helps answer your question, but like anything really it's not a one size fits all approach and is a tool to be used when/if required.
I personally love headless but we also use no-code solutions, page builders, and custom + customised themes based on whats right for our clients (i.e don't use a bazooka to squash a fly).
Originally, the reason I started this project was when I was working on a client project ( an influencer with a large following) the original site no matter how much we optimized it would still crash when there was a launch of a new product. Thousands of people queuing up to buy what was on offer before it sold out. WooNuxt takes a massive load off the server. So Performance is a big one. Also having a modern front end can have a very rich user experience for the customer. The ability to have a PWA is a big one. This also opens up the option to put something like capacitorjs on top of it and have a mobile app. It basically opens a lot of doors.
@@scottyzen88 nicely put..