[stadium]

I'm learning to build front end with Vue.js and it supports SPA with client side rendering with multiple routes. I intentionally choose this to take advantage of cheap (free) static site hosting, and the learning curve is easier without having to think about server management.

I didn't realize until this project that a dynamic, reactive site can use static hosting.

Vue has been a pleasure to work with. It supports server side rendering too but do far I haven't needed it.

[depressedpanda]

Once you get more comfortable with Vue, I suggest you start looking into making the project a PWA so that it may work offline and can be "installed" by the user (if it suits your use case).

I've written a fully statically served, backendless PWA, that uses the browsers local storage for persistent data, meaning that the data is fully private and owned by the user. If a user needs to sync their data between clients, they can connect the app to their Dropbox or Google Drive. There's even a chat implemented with WebRTC which allows users to communicate directly with each other, without a backend.

If you disregard the JS haters on HN, you'll realize you can do some amazing things in the pure browser runtime nowadays.

[stadium]

Interesting, that must be what I installed to get the Vue docs as an app. I hadn't heard the term PWA, thanks for sharing.