In reply to Russell Aaron.

Russel – you are correct, that is kind of what Jamstack is attempting to achieve. However, what many that snicker or cringe at WordPress fail to understand or keep up with is the recent WP enhancements and the current efforts and milestones already set to address these problems. Just because WordPress historically had issues that more modern approaches solve doesn’t mean you need a whole new CMS architecture. It just means the currently leading CMS needs some enhancements to adopt that new way of rendering content – which WP is currently already doing with Gutenberg and also full-site block editing coming soon.

So…yes, I am team WP all the way. However, it’s still imperfect. If I can state one BIG thing that would really help push WP and CMS into the future, it is what major WordPress hosting providers include on their server architecture. Right now, most WordPress hosts don’t include technologies necessary for server-side rendering of JS heavy UIs. If WordPress is to include components that are more futuristic, this needs to change in order for WordPress to remain SEO friendly and continue to deliver content that is rendered on the server in certain situations. Without Node installed on all WP servers, this because impossible to consider. The day WordPress can rely on Next.JS or other like technologies more is the day we will see a bigger and better WordPress emerge. This will destroy most Jamstack benefits.