Switch to client-side templating

[jtojnar]

This would make the JavaScript client equal to other clients and allow us to drop the JS-specific API endpoints entirely.

Since selfoss requires JavaScript to work and we don’t care about SEO, the only difference should be in performance. And the difference should be negligible because the majority of markup comes from the item bodies anyway.

I implemented a proof of concept in client-side-templates branch.

[armandabric]

Have you thought about making the web UI a SPA. This could make the actual selfoss API perfectly shared between all the clients (web, android, iOS). It will also make possible to make this SPA a progressive web app: this will make the mobile experience way better (if done correctly)

[jtojnar]

@Spy-Seth Yes, this is the goal. niol is already working on offline support.