strategy and purpose about woonuxt HOT 6 OPEN

Hi @Amenocy,

Instead of invalidating 5 variants WooNuxt would just need to invalidate the parent product. So one page basically. I haven't figured it out for Nuxt yet but hopefully I'll find a solution soon. Any site with 1000+ products I wouldn't try statically render it. Nuxt makes it ease to implement SSR so thats the approach I'd be taking.

I had a fuzzy search set up with the previous version with a small payload that made it fast and not heavy. I'm still on the fence on what way I'm going to go on this. I'm thinking of generating a separate json file or just pinging the server(but im reluctant to do this). But whatever way I go I will be avoiding any service like Algolia. That's not stoping anyone from customising the search component to use it though. Its just never going to ship by default.

inventory control is somewhat handles. It will only let you purchase a product that is in stock.

Like the saying goes "Horses for courses"! WooNuxt or any static eCommerce will find it's place in the World. Plenty of people are pushing this space so we will have to wait and see where it ends. 🔮

from woonuxt.

Instead of invalidating 5 variants WooNuxt would just need to invalidate the parent product. So one page basically. I haven't figured it out for Nuxt yet but hopefully I'll find a solution soon. Any site with 1000+ products I wouldn't try statically render it. Nuxt makes it ease to implement SSR so thats the approach I'd be taking.

@scottyzen Check this out!
https://dev.to/jacobandrewsky/incremental-static-regeneration-in-nuxt-3255

Like the saying goes "Horses for courses"! WooNuxt or any static eCommerce will find it's place in the World. Plenty of people are pushing this space so we will have to wait and see where it ends. 🔮

You'll be excited to see where soon.

from woonuxt.

Instead of invalidating 5 variants WooNuxt would just need to invalidate the parent product. So one page basically. I haven't figured it out for Nuxt yet but hopefully I'll find a solution soon. Any site with 1000+ products I wouldn't try statically render it. Nuxt makes it ease to implement SSR so thats the approach I'd be taking.

@scottyzen Check this out! https://dev.to/jacobandrewsky/incremental-static-regeneration-in-nuxt-3255

Like the saying goes "Horses for courses"! WooNuxt or any static eCommerce will find it's place in the World. Plenty of people are pushing this space so we will have to wait and see where it ends. 🔮

You'll be excited to see where soon.

Thanks @M-GRV. I had a look into this awhile ago. I'll definitely give it another look again now 🤞🏻

from woonuxt.

Instead of invalidating 5 variants WooNuxt would just need to invalidate the parent product. So one page basically. I haven't figured it out for Nuxt yet but hopefully I'll find a solution soon. Any site with 1000+ products I wouldn't try statically render it. Nuxt makes it ease to implement SSR so thats the approach I'd be taking.

@scottyzen Check this out! https://dev.to/jacobandrewsky/incremental-static-regeneration-in-nuxt-3255

Like the saying goes "Horses for courses"! WooNuxt or any static eCommerce will find it's place in the World. Plenty of people are pushing this space so we will have to wait and see where it ends. 🔮

You'll be excited to see where soon.

Thanks @M-GRV. I had a look into this awhile ago. I'll definitely give it another look again now 🤞🏻

I think with SEO and ISG this project is where it's at. For example, we have about 6,000+ products. Luckily, we do not require any sort of checkout (catalog only) but still a lot of items to rebuild.

For search I like the idea of keeping it un-opinionated. We are planning to use wpengine's version of algoia.

So not having to unwind some things would be nice.

You should open up discussions on this project so everyone can talk without it being opened as an issue :)

from woonuxt.

Hi @M-GRV,

Thanks, Yeah I'm 100% with you on the search or any feature really to be left un-opinionated. Like overwriting the ProductSearch.vue component in the parent directly lets you customise it any way you need to.

The current roadmap is roughly

• Getting SEO up to where it need's to be. And the plan would be to use Yoast with a fallback to basic SEO tags/meta-data if it's not installed.
• I'm playing around with isr but haven't got it to work yet! I can see how a 6,000 + product shop can need that 😰
• I'm also aware I need to make a setup video (It's just finding the time!)

Any ideas on where to open a discussion form. I use Slack & Discord but haven't ever set a channel up.

from woonuxt.

Hi @M-GRV,

Thanks, Yeah I'm 100% with you on the search or any feature really to be left un-opinionated. Like overwriting the ProductSearch.vue component in the parent directly lets you customise it any way you need to.

The current roadmap is roughly

• Getting SEO up to where it need's to be. And the plan would be to use Yoast with a fallback to basic SEO tags/meta-data if it's not installed.
• I'm playing around with isr but haven't got it to work yet! I can see how a 6,000 + product shop can need that 😰
• I'm also aware I need to make a setup video (It's just finding the time!)

Any ideas on where to open a discussion form. I use Slack & Discord but haven't ever set a channel up.
@scottyzen

M!-GRV is my work account. I can help you open a discord. Or Github has a discussions tab you can turn on for projects which may be the easiest option for now.

https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository

from woonuxt.