Incremental Builds in Gatsby Cloud
gatsbyjs.org
Incremental Builds in Gatsby Cloud
1–10 of 81 posts
Re: Incremental Builds in Gatsby Cloud
#2You still need to use an api for everything. Good apps need a backend; not a JAMStack fan for anything but the most basic of sites.
Re: Incremental Builds in Gatsby Cloud
#3This is great! Is there any technical limitation keeping this from being part of the open source version?
I get that Gatsby company put a lot of effort into this and wants a return on that investment, and good for them. I assume a third party could offer the same but why would they compete at the same value prop.
However an open source version to not be reliant on any company would be compelling to many.
Re: Incremental Builds in Gatsby Cloud
#4You still need to use an api for everything. Good apps need a backend; not a JAMStack fan for anything but the most basic of sites.
The 'backend' here is ... HTML. For read-only a blog, that's likely more than enough. Otherwise, for dynamic content like contact forms and such, I don't know if there's a meaningful benefit to building out a whole site in PHP/Python/Rails or something (and paying commensurately more in hosting) than to use Formspree or something similar.
Yes, it calls an API. And thankfully with Formspree, it's pretty easy to see the price breakeven points vs. hosting, but there are benefits to be had.
Re: Incremental Builds in Gatsby Cloud
#5You still need to use an api for everything. Good apps need a backend; not a JAMStack fan for anything but the most basic of sites.
The 'backend' here is ... HTML. For read-only a blog, that's likely more than enough. Otherwise, for dynamic content like contact forms and such, I don't know if there's a meaningful benefit to building out a whole site in PHP/Python/Rails or something (and paying commensurately more in hosting) than to use Formspree or something similar. Yes, it calls an API. And thankfully with Formspree, it's pretty easy to see th…
Content has to come from somewhere. Operational complexity is increased, not decreased, since you are running a build server in addition to your CMS. The benefit is easier optimizations in the frontend.
Re: Incremental Builds in Gatsby Cloud
#6so this is cool release, and no objection on that
but if your pipeline has automated testing, security scans and more then you are not actually deploying in 10s
more technical details would be good but I guess either I missed it or they look at it as IP
Re: Incremental Builds in Gatsby Cloud
#7Earlier quoted context omitted.
The 'backend' here is ... HTML. For read-only a blog, that's likely more than enough. Otherwise, for dynamic content like contact forms and such, I don't know if there's a meaningful benefit to building out a whole site in PHP/Python/Rails or something (and paying commensurately more in hosting) than to use Formspree or something similar. Yes, it calls an API. And thankfully with Formspree, it's pretty easy to see th…
Content has to come from somewhere. Operational complexity is increased, not decreased, since you are running a build server in addition to your CMS. The benefit is easier optimizations in the frontend.
But you can outsource those (build server, CMS) to e.g. Netlify and Contentful.
But if you don't want that, there's a billion alternatives; the CMS market is one of the most saturated ones out there.
Re: Incremental Builds in Gatsby Cloud
#8Earlier quoted context omitted.
The 'backend' here is ... HTML. For read-only a blog, that's likely more than enough. Otherwise, for dynamic content like contact forms and such, I don't know if there's a meaningful benefit to building out a whole site in PHP/Python/Rails or something (and paying commensurately more in hosting) than to use Formspree or something similar. Yes, it calls an API. And thankfully with Formspree, it's pretty easy to see th…
Content has to come from somewhere. Operational complexity is increased, not decreased, since you are running a build server in addition to your CMS. The benefit is easier optimizations in the frontend.
Content can come from text files. Operational complexity ought to be neutral (or even negative) if that content compilation step replaces your CI pipeline.
Re: Incremental Builds in Gatsby Cloud
#9Gatsby founder here.
Really appreciate the feedback and support for our launch today! The team worked super hard to get Incremental Builds live in public beta but are taking all the feedback (here and all over the web) as we go into full launch. Let us know what you think. Thanks!
Re: Incremental Builds in Gatsby Cloud
#10Earlier quoted context omitted.
Content has to come from somewhere. Operational complexity is increased, not decreased, since you are running a build server in addition to your CMS. The benefit is easier optimizations in the frontend.
But you can outsource those (build server, CMS) to e.g. Netlify and Contentful. But if you don't want that, there's a billion alternatives; the CMS market is one of the most saturated ones out there.
I actually feel like Gatsby will be developing a CMS to round out their paid feature-set. I have zero-inside knowledge, just a hunch that to get customers to pay up handsomely, the product needs a deeper "fit" in the publishing pipeline.