Yea, essentially what I'm saying in my a vs b scenario.
> Or you can only list the product and make the buy button and items available come from an api, doable, but then you start to loose the simplicity of gatsby.
And you still haven't solved the issue of delays between content changes and deployment... What if someone has made a bad mistake in content editing and you need to revert it? You're exposed to the whims of your build processes and infrastructure... There's no way I can sell to anyone who's played with Wordpress or Shopify "well, your changes might take anywhere from 3 to 15 minutes to be live..."
That's why I'm asking, how can product and engineering teams justify this kind of thing? I'm not being facetious, I'd love to hear their perspective.
> Or you can only list the product and make the buy button and items available come from an api, doable, but then you start to loose the simplicity of gatsby.
And you still haven't solved the issue of delays between content changes and deployment... What if someone has made a bad mistake in content editing and you need to revert it? You're exposed to the whims of your build processes and infrastructure... There's no way I can sell to anyone who's played with Wordpress or Shopify "well, your changes might take anywhere from 3 to 15 minutes to be live..."
That's why I'm asking, how can product and engineering teams justify this kind of thing? I'm not being facetious, I'd love to hear their perspective.