render project links in index.html

[christianp]

At the moment, the project data is held in JSON and the list is created
in javascript after the page loads. This breaks the site for users
without JS.

This moves the rendering of the project list to index.html, so it's
included in the static page, and then the renderProjects() function
shows/hides and reorders the projects as necessary.

If the JS doesn't run, you just see the complete list of projects in the
default order, without the filter interface.

This somewhat conflicts with #525, which assumes that the page is unusable if JS isn't supported.

[shiftkey]

@christianp this looks pretty great. The only regression I can notice here is that we no longer get the benefit of randomizing the project list on the client - this code - and we're now doing thing alphabetically.

[christianp]

@shiftkey is it really a regression? When the JS runs, the list is shuffled. I can't see how you'd shuffle the list per-client without JS, and on gh-pages.

[dahlbyk]

It's a regression in that the top projects now get disproportionate exposure. If JS is available, we could suppress the HTML project list until we're able to shuffle it.

[shiftkey]

Dropping this back to need-work because there are outstanding conflicts, and this changes the behaviour of the site to no longer randomize the list of projects.

[shiftkey]

I'm going to close this out because #1412 is ready for discussion about a simpler first step to improve the experience for clients with JavaScript disabled.