The DataTank is open source data platform, which you can use to transform any dataset into an HTTP API.
I've just installed the android and the desktop app. Seems like it's just the web version in a container, but still, it's nice :)
We have an intern at Open Knowledge Belgium who I could ask to revamp the website of thedatatank.com (now still the 1-pager to announce the fact that there are people providing SLAs) into a more community friendly website. Then the roadmap can be a part of it.
Zalig ^^
on the road to a public roadmap: do you consider gathering "public input" - real life via user-group-meetings or online via votable topics like with https://www.google.com/moderator/ - you could use that to gather and rank suggestions, then translate them into concrete issues for the next release - or was your question more about how to style the page :) - other thing that could help in structuring the roadmap(s): the clear and sustained yearly-release-cycle?
Furthermore, also indicating the biannual release cycle would be a nice addition to the website indeed!
Question: Would it be possible to use TDT as a LOD "redirect" service, e.g. if we define LOD ID's somewhere (.../id/news/123) can we forward the request to TDT and have TDT do content negotiation? Trouble is that HTML representations and LOD representations may have quite different URLs so we should keep quite a big referral table, and preferably also a smart (à la mod_rewrite) redirection for some types
This is something not yet implemented over here: tdt/core#120
Another answer, a better one I believe, is to hook up e.g., a virtuoso to tdt/triples
then, tdt/triples will dereference any URI that uses the place where tdt/core+tdt/triples is installed as a baseURI
(e.g., for the current situation, if you would have a triple with a subject http://data.gent.be/trees/1 in your virtuoso, and you configure it that way, it will dereference that URI and show that triple)
you can read more about that in the paper "painless URI dereferencing with The DataTank: http://2014.eswc-conferences.org/sites/default/files/eswc2014pd_submission_37.pdf
Bonus: you will have a triple pattern fragments interface without further problems ;)
tdt/triples source: https://github.com/tdt/triples (any tdt/core installation can directly be extended with tdt/triples) and a demo: http://triples.demo.thedatatank.com/triples/all
We could extend tdt/triples with that quite easily... but the question is whether you want that: only machines will see these links and when machines arrive at non-linked resources by using a HTTP link which is expected to show more useful information in a machine interpretable format their logic might break
what you could do however is just add a link http://id.stad.gent/trees/1 rdfs:seeAlso http://stad.gent/htmlpagesoftrees/1 .
that way, machines will understand that a rdfs:seeAlso means that what's further is just more information in possibly human only readable formats
in HTTP you're almost obliging a redirect, with a rdfs:seeAlso you're indicating that in the end-userinterface it might be interesting to show this link with the identifier
you can perform content negotiation on that URI :)