-
-
Notifications
You must be signed in to change notification settings - Fork 124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
strategy and purpose #89
Comments
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. 🔮 |
@scottyzen Check this out!
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 :) |
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 The current roadmap is roughly
Any ideas on where to open a discussion form. I use Slack & Discord but haven't ever set a channel up. |
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. |
At first glance, i liked the project, but i see some points in projects that prevent it from becoming useful in a real-life project, even a small one. please correct me if i am wrong
1- it uses static build, but for all of the products at once, so its not possible to update one product via invalidating that build. assume that we have 1000 products and 5 variants for each and we want to update just one variant. basically, its not possible, solution would be capability of invalidating just one of statically generated pages. ( i know it's easily possible in nextjs)
2- in each e-commerce project, search is the most important feature, we don't have search here. trying to load everything in frontend and do a search in FE is not a good idea :) here we need a search layer and interface to be able to connect it to Wordpress itself or any other search engine, opensource or service like algolia.
3- inventory control on the product description page is essential, so we should be able to add some serverside functions and parts to manage things like that.
The text was updated successfully, but these errors were encountered: