The vast majority of the internet is files of text and images that don’t need to be updated that often. Further, rendering of text and images is handled by cli

The vast majority of the internet is files of text and images that don’t need to be updated that often. Further, rendering of text and images is handled by client configured applications that change - with the content fitting into client specified configurations Given that, if you want your content to be fast to access and simple to maintain over the longest period then: 1. Provide the smallest possible amount of bytes to the client that completes the communication task 2. Format the data in a way that will remain supported by the most clients over the longest term It’s fun to play with different setups for a variety of use cases and server side rendering, but history shows that the most reliable design pattern prioritizes clients being able to consume and render data as quickly and clearly as possible. I’ve never found a simpler way to do that than a file server hosting static .html files with text, svgs and pngs.