4 ms·
Not the OP, but Gatsby works well for sites that rarely change content. For e-commerce sites with >100 SKUs + variants, having to rebuild every single time you
by rozenmd 8y ago
Not the OP, but Gatsby works well for sites that rarely change content. For e-commerce sites with >100 SKUs + variants, having to rebuild every single time you make a description update is pretty tedious, and Next.js seems to be the solution in that case.
- mpeg 8y agoIt's only tedious if the build is not automated, static site generators work pretty well with continuous delivery practices though.
- deltron3030 8y agoCan't you use "dynamic widgets" inside Gatsby with some router tweaks, or did I misinterpret this blog post regarding Gatsby as "app shell"? https://www.gatsbyjs.org/blog/2018-11-07-gatsby-for-apps/ https://www.gatsbyjs.org/blog/2018-11-07-gatsby-for-apps/
- andrewingram 8y agoYou can do whatever dynamic things you want with Gatsby after the page is loaded, including client-only route. The issue is that if you need anything "dynamic" (eg user-specific stuff in the header, or layout variations for A/B tests) in the initial render; you have a more difficult problem. For A/B tests you could generate all the variations during build and have whatever sits in front of the site be responsible for serving the right files, but this just feels like an admission that, yes, static sites have their limits. For user-specific stuff the only real solutions are to go back to having pages be server-generated, or go all in on technologies like Edge Side Includes.