What are best practices for Gatsby Build/Release based on Content Updates in the CMS?
This question is posted on behalf of a user.
Moving content into the build+release process offers us a lot of new options + features, but I can see it also being an issue for clients if it's not performant.
Each save/publish in Agility causes a new content update, and that now has to be built every time, which can easily stack up and slow down.
Any suggestions/best practices for getting the best possible performance on builds and releases of content?
I've set up build+release pipelines with the gatsby and netlify CLIs in our DevOps that trigger on every save/publish. It takes around 30 seconds to get content built and updated; and that will get worse as more content/pages are created.
With a trigger every content update as well (imagining if someone saved/published 100 items at once), it can do a lot of useless builds too.
One answer is to beef up the VMs running the builds, though are there any other ways to speed things up that you've found ? How does your process look for content updates ?