One of the things that's creating headwinds for Modern Web Development (Headless/Jamstack) is the profusion of rendering strategies and confusion around terminology.

Cache invalidation and naming. Again and again and again. There's collective industry trauma bound up in all of this. People have *powerful* psychological attachments to static rendering, because it's dependable. Buuuut....

Here's where we are with Headless/Jamstack. Some technologies ride the hype cycle across the chasm: garnering early majority adoption based on buzz.

That's the easier path. Won't work here.

Here's an interesting thing. "Composable Stack" is new language that's emerging in our market to identify a possible successor to the existing DXP category. I highlighted this article on Monday that I thought was pretty good:

cmswire.com/digital-experi…

Ok, so as promised, here's my hot-take on this great piece from @realstorygroup's @apoorv in @cmswire, which maps to what I've seen in the market.

TL;DR - suites are out, stacks are in, and the cool kids in marketing are years ahead of most vendors.

cmswire.com/digital-experi… I'm clearly biased, but this has been my jam for a while.

pantheon.io/blog/dxp-vs-we…

Every technology professional who pays attention to politics is apoplectic about what happened in Iowa last night. My take(s), in thread form... 1. This was an unnecessary use of technology. While I have a self-interested motive to see more tech in more places (future job security), you don't need an app for everything. Especially when you have an effective and resilient process in place.

In addition to #serverless (see link), my other new favorite piece of hashtag-compliant vocabulary for Pantheon is #WebOps

Let me explain.

https://twitter.com/outlandishjosh/status/1154442154984394754

The default short-hand for what we do is, of course, "hosting." The dreaded H-word. It's part of our story for sure, but it misses out on the value Pantheon provides.

It's an incomplete "what" that thoroughly misses out on the "why."