Except, I think this is actually somewhat an example of what the author is saying, because when I click around links: * Support * Guides * Login * Blog are

Except, I think this is actually somewhat an example of what the author is saying, because when I click around links: * Support * Guides * Login * Blog are all outside the SPA, and some appear to be MPA apps. And perhaps once I logged in that would be its own new app as well? So in that sense, your website in not an SPA, you have an app for getting new signups which is an SPA, and then you have a bunch of other SPA or MPA apps hooked up to that. As the author said, "Websites can still have Rich User Interfaces without cramming the entire site into one document." I think the point is to find a balance and realize building your entire infrastructure into an SPA will indeed break the web and your user's experience, most likely. Having a mix of SPA/MPA apps that cover the various functionality you need, and using each where appropriate, is a much better use of resources and results in a better UX.