I think you've identified that some websites are secretly multiple websites in a trenchcoat.
The New York Times has a website at NYTimes.com where people read news stories, and a separate content management system where their employees write and publish stories. NYTimes.com is in the "informational" quadrant; the content management system is somewhere in the "online" half. The needs of these two systems are pretty dramatically different.
Other websites blur the lines a bit more in their architecture. For example, WordPress blogs generally include an "admin" app that's almost completely separate from the main website, but hosted on the same domain. Other websites like Wikipedia and StackOverflow are nominally "the same website" but activate a lot of extra UI elements when you're logged in.
But IMO it still makes sense to think of these as separate systems and optimize them individually. For example, Wikipedia uses a different serving path with much more aggressive caching when you're logged out (and the site is "informational"), vs when you're logged in as an editor (and the site is "transactional").
The "islands" architecture discussed in the article lets us extend this to individual features on the same page, too. Think of a startup marketing site's "chat with support" popup; that's pretty clearly a real-time island on an otherwise static page.
The New York Times has a website at NYTimes.com where people read news stories, and a separate content management system where their employees write and publish stories. NYTimes.com is in the "informational" quadrant; the content management system is somewhere in the "online" half. The needs of these two systems are pretty dramatically different.
Other websites blur the lines a bit more in their architecture. For example, WordPress blogs generally include an "admin" app that's almost completely separate from the main website, but hosted on the same domain. Other websites like Wikipedia and StackOverflow are nominally "the same website" but activate a lot of extra UI elements when you're logged in.
But IMO it still makes sense to think of these as separate systems and optimize them individually. For example, Wikipedia uses a different serving path with much more aggressive caching when you're logged out (and the site is "informational"), vs when you're logged in as an editor (and the site is "transactional").
The "islands" architecture discussed in the article lets us extend this to individual features on the same page, too. Think of a startup marketing site's "chat with support" popup; that's pretty clearly a real-time island on an otherwise static page.