Good job! We see many orgs adopting this approach for the same reasons you mentioned (disclaimer: we build a CMS for these sites https://forestry.io https://for

Good job! We see many orgs adopting this approach for the same reasons you mentioned (disclaimer: we build a CMS for these sites https://forestry.io https://forestry.io). The healthcare.gov site might be a good comparison for your team. It was a large legacy-CMS site when it launched. It had a lot of performance problems so they migrated to Jekyll which solved everything. Here’s a quick video from one of the guys describing the migration: https://www.msnbc.com/all-in/watch/the-nerds-who-saved-obamacare-175808579562 https://www.msnbc.com/all-in/watch/the-nerds-who-saved-obama... Also, Kyle Rush worked on the original Obama site (Jekyll) and shares insights here in this video. He attributes their success to the fact that their front-end devs were able to A/B test the site multiple times per day to increase the donations. It’s loaded with good arguments to move to a static platform. https://www.youtube.com/watch?v=ia8vsuiXiL0 https://www.youtube.com/watch?v=ia8vsuiXiL0 If you're curious to see some build-time benchmarks for Jekyll/Hugo, check out this (from our team) https://forestry.io/blog/hugo-vs-jekyll-benchmark/ https://forestry.io/blog/hugo-vs-jekyll-benchmark/