Graceful degradation.

I am frequently browsing documentation in `links` or `lynx`, because our target system does not have anything better.

Please, make sure that the website gracefully degrades when the client does not support all the features of the most recent Chrome.

Example:

### Old website






Useful and usable, 5 pages of pure content, and I can ever get a full sitemap for free, because the menu automatically expands.

### New website





1. The _good_ thing about the new website is that in `links` it has a navigation menu at the top, which is just very user-friendly, and an excellent feature. However, I don't users hardly need two copies of that menu.

The rest I wouldn't consider very helpful.

1. The front page is not really speaking about what boost is, not nearly as much helping the user to grasp most of the boost (as an organization, and as a set of libraries) logic from just a single page. (And browsing and clicks are very expensive for human brain.)
2. It is also not giving a direct download link to the most recent release.
3. I also don't see links to RSS, which is still a useful news source, even though newer standards exist. (I would ask to consider equipping the website with hEntry Semantic Web tags, but those are not yet widely supported.)
4. The wonderful site map is entirely missing.

And with all that, the pages are more or less equal in size:

```
-rw-r--r-- 1 lockywolf users 26K May 12 09:40 new-boost.txt
-rw-r--r-- 1 lockywolf users 27K May 12 09:40 old-boost.txt
```

Start by opening the website in links and lynx and compare the old and new examples described in the issue. Review the page structure and navigation entry points, then determine how the requested content, release link, RSS links, and sitemap should remain usable without modern Chrome features. Done means the site remains useful and navigable in limited clients.

Written by the indexing model from the issue text.