WIP: support multiple projects

[phillipj]

Working on getting both io.js and node supported, mainly related to downloads and versions. So far its been brute force just to get it up-n-running.

As we dont have a unified versions.json yet, as @mikeal mentioned in nodejs/build#163, I've just created a simple unified_versions.json for mocking purposes in the meantime.

Just duplicating everything doesnt make sense and obviously doesnt look that great either. The frontpage didnt get too bad though, but the downloads page with its matrix and previous released versions is a whoooole different story.

Any thoughts about how this?

[fhemberger]

There's no need to support multiple projects. From version 4 on, there will be only Node.js.
Older versions of node/io.js will only be shown in the overall release list, which will by then become a separate page (with a looooong list).

[phillipj]

Ahh, so when you said

Both. There still needs to be some work done to integrate the builds automatically into the site.

in issue #20 you only meant the previous release list?

[fhemberger]

Yes. The list should not only the converged release (starting with 4.0.0), but all io.js and node.js releases in a single spot. Sorry, if this caused a misunderstanding.

[phillipj]

Np, created a WIP to find out what needed to be done - great success in other words 🎉

Sounds alot simpler than what I had in mind. Closing this PR as it sounds trivial enough to fix quickly after build has a unified versions in versions.json ready.

[mikeal]

This came up in the TSC meeting a bit as well, we want to have a merged/complete Changelog as well and I want to try and create automated release posts from the Changelog+versions.js