Discussion on using Sanity with Eleventy for scalable static site builds

Hello community,
I have a question regarding Sanity and scalability. I have a site I want to convert into a Sanity project. The website has approximately 10,000 static webpages which currently is manually maintained. Hypothetically if you were to migrate a website of this size, how well would Sanity cope? I'm wondering what would the build time would look like when deploying and any other potential issues/limitations.

Does anyone here have any experience with content of this size and if so could you possibly share any tips? The content I'm working with is mainly text and not a lot of media. I want to make sure Sanity is the right product for this project.

Many thanks in advance

It'd be fine. The build time is not really related to Sanity, it is related to the tech you have in that pipeline and the complexity of the pages or any APIs you need to call to generate them. Stuff like Hugo can build hundreds, maybe thousands of pages a second in theory, and of course you have the JS approaches like Next which are always advancing in terms of perf

Thanks User,
That sounds positive. My build is using eleventy and Nunjucks as it needs to be a static build hence I've not gone for a React solution. So far it seems to be working just fine, I'll do some testing soon by duplicating some pages and feedback in here for anyone who needs to know in future.

Loving Sanity atm, will be using for all my projects from now on
😃

Should be just fine with 11ty. They've just come up with a hybrid rendering model based on serverless, so you could possibly look into that as a scaling option (essentially don't build the long tail of low access pages you have until request)

Good to know, thanks for the info! I'm quite confident with 11ty being a Sanity gold sponsor. Can't believe how efficient modern FE web development has become in recent years. Over the moon!

Is it really though? 😄 200 frameworks, tools, npm hell, distributed monoliths, server side rendering...
All stuff rails was doing ten years ago
😉

I'm definitely seeing the seeds of a movement back towards more straightforward HTML, CSS and native JS where possible. So many sites just don't need these complex tools.

Well in terms of API CMS like Sanity, Contentful etc it's great. But yeah take your point there are too many frameworks. Hence I keep to static builds these days and like to keep it simple.

Yeah I second that User, simple html is better. React is great for UI in your admin panel but I can't think of reasons to use it for customers websites

Yeah CMS world has never been better, I agree. With a bit of craft, as I'm sure you find yourself, you can power global websites with very simple technology and low-bloat tooling. Most people aren't building Netflix style, event-sourced microservices architectures.

"Most people aren't building Netflix style, event-sourced microservices architectures." 😂 So true!