Why would you need JS, CSS or Flash to have issue tracking, documentation, metrics or graphs?
An issue tracker is essentially a forum where the threads have an open/closed state attached. People have built such web applications before JS even existed.
Documentation is even simpler, just a bunch of HTML documents, maybe with an HTML form to edit them.
The problem with your first link is not the lack of CSS, it's that the information listed is less relevant than what Github shows.
But instead of comparing with that, try disabling the CSS in the GH page. Ignoring the header section, I think the file list and README look just fine, and I wouldn't be bothered at all to use it as such.
An issue tracker is essentially a forum where the threads have an open/closed state attached. People have built such web applications before JS even existed.
Documentation is even simpler, just a bunch of HTML documents, maybe with an HTML form to edit them.
As for graphs, there are many here, and they work fine without JS or CSS: http://hydra.it.teithe.gr/munin/aetos/aetos/index.html
--
The problem with your first link is not the lack of CSS, it's that the information listed is less relevant than what Github shows.
But instead of comparing with that, try disabling the CSS in the GH page. Ignoring the header section, I think the file list and README look just fine, and I wouldn't be bothered at all to use it as such.