leopd / codetrend Goto Github PK

Nice to have. For primary page display, I expect the charts to continue to be generated client-side -- interactivity is super useful. But when sharing a link to codetrend.org many services (facebook in particular) look for an image to represent the page. Being able to share links is important to get more visitors and help generate UGC. So for the <og:image tag alone, I think it's worth rendering the charts on the server.

The "correct" way of running node to interpret d3 is probably not in fact ideal, since the client-side charts will be animated and interactive, and just have a different design goal. So I expect the server-side charts to be simplified in a parallel code path.

It would be great to have descriptions of the technologies directly in CodeTrend w/o having to link to SO. This requires importing SO's tag-wiki.

The tag-wiki data are currently in the data export, sort of. The contents of each page is, but the name of the page is not in the entry, meaning all the associations must be done manually.

This post on meta-SO raises the question: http://meta.stackoverflow.com/questions/176407/data-dump-is-missing-link-between-tag-names-and-tag-wikis-tag-wiki-exceprts

Add a top-level "contribute" menu which invites people to use any popular openid provider. Probably just gonna use omniauth directly without devise or anything else layered on top.

Volunteers?

Bueller?

Allow visitors to voice their opinions about which technology is better for what kind of problem. Logged in users should be able to create new tradeoffs, while not logged in voters should be allowed to vote on previously defined tradeoffs. Tradeoffs should be scoped to the metatag.

When adding a new metatag, it gives me two messages.