What are the key friction points in a Jamstack development mode, specifically in terms of collaboration between engineering and content teams?

I think the whole idea of headless CMSs and build hooks allowing non-developers to collaborate was one of the biggest problems. I guess there may still be friction there in terms of immediacy. When building a site in Jamstack, you ship some content, but it still takes time to build and get distributed via CDN, the content delivery network that's an essential part of the Jamstack approach. As opposed to just making a change, saving it in a database, and next time you make a request it comes out of the database. I think there's perhaps a faster iteration speed there, and I'm not sure that Jamstack has 100% solved that. So that part of the collaboration may still be a challenge.

And then there’s just people learning to do things a different way. That’s always a friction point. At the end of the day, for somebody that's trying to create content, as long as the words are on the page, it looks good, and it's achieving SEO goals, it probably doesn't matter that much which approach is taken. So learning a different way of doing things, or even just learning a different CMS, can be a barrier.