spec diffs can be hard to read

[joshmoore]

In #249 (comment), @d-v-b pointed out that the current strategy can lead to situations where there's no clear diff for a spec change (especially related to dev versions). For 0.5, @normanrz and I are going to proceed with the current 0.5/ directory to reduce churn, but for the release of 0.6 it might make sense to collapse the versions down. A priority will be maintaining the existing URLs, though a redirect would likely be acceptable.

[joshmoore]

Depending on the solution, also:

• evaluate dropping latest
• or symlinking (might require a more substantial web server)
• dropping bikeshed

[normanrz]

I just want to add that both the docs and the specs should have a favicon. Right now they have the default RTD and W3C icons.

[normanrz]

I think the best way of organizing versions would be through git branches/tags. That adds a bit more complexity to the rendering. I don't know what to do about bikeshed.

[joshmoore]

A fairly easy mechanism would be to retroactively attach them as builds which get downloaded from GitHub for rendering.