For document-based websites, I go JS-free. My blog works without JS (except for comments, because they're from disqus and I'm lazy). And for public facing docum

For document-based websites, I go JS-free. My blog works without JS (except for comments, because they're from disqus and I'm lazy). And for public facing document websites it's usually possible to cache everything so it'll be REALLY fast. But if I'm making an actual application, it's a lot simpler to disregard users without JS. For example, I use angularjs, and if you take full advantage of it, you always just send the user the same index.html page and the server has a bunch of JSON API endpoints. Then you let the client-side router take over. If you really want to support JS-free users on your application, you're probably better of making a separate limited version of your application instead of having multiple fallbacks in the same page.