6,000+ pages sounds like it would be a pain to rebuild with each change. I've considered something like Gatsby for a large site I manage with mostly static content, but we've got 9,000+ posts and I'm concerned about the build times whenever someone realizes they made a small typo.
Is Gatsby smart enough to only build what changed, or does it build everything every time? And how long does that take?
VP of DevRel RapidAPI ❯ Award-winning Web Developer NodeCLI.com ❯ Google Dev Expert Web tech ❯ 2x GitHub Stars Award ❯ WordPress Core Dev ❯ TEDx Speaker ❯ "awesome example for devs" — Satya Nadella
Location
San Francisco Bay Area
Education
EE-CS Engineer turned Software Developer
Work
VP of DevRel (DX Eng., Content & Community) RapidAPI ❯ Google Dev Expert ❯ GitHub Star ❯ NodeCLI.com
6,000+ pages sounds like it would be a pain to rebuild with each change. I've considered something like Gatsby for a large site I manage with mostly static content, but we've got 9,000+ posts and I'm concerned about the build times whenever someone realizes they made a small typo.
Is Gatsby smart enough to only build what changed, or does it build everything every time? And how long does that take?
I have no idea, but it really should be smart enough to build what’s changed. Seems like fairly straightforward diffing.
You can both cache the build inside of Gatsby and on Netlify. :)
This is more of a question than a statement. I thought that was what a React app was good at. Only building what had changed.
Smashing Magazine switched from WordPress to a JAMstack: netlify.com/case-studies/smashing/
Try Hugo. Your 9000 page site will take a second to build. Most likely less.
Gatsby is pretty smart. Building has been slow in the past, but it's steadily getting faster.