You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should have a more complete list of projects and ideas that have been discussed or worked on at Open Twin Cities meetings or events.
My idea is to use a Google Spreadsheet to act as a data store, then simply display this on a page on the opentwincities.org site. We can easily use Tabletop.js to get data from the Google Spreadsheet as well a template system like that including in Underscore.js to make it look good.
I am not sure what is the most appropriate way to handle input. I think having it editable by anyone could end up a bit bad, but we don't want to be gate keepers for it. We could also look at a mix of editing directly and Google Form submissions. Ideas?
The text was updated successfully, but these errors were encountered:
Is there anything to the idea of storing content in the spreadsheet as Markdown, and use something like https://github.com/evilstreak/markdown-js to convert it to HTML. I'm in the midst of turning much of opentwincities.org's content into Markdown, in part because it's so much more legible as plain text. As I work with the spreadsheet, I'm starting to see the same need there.
We should have a more complete list of projects and ideas that have been discussed or worked on at Open Twin Cities meetings or events.
My idea is to use a Google Spreadsheet to act as a data store, then simply display this on a page on the opentwincities.org site. We can easily use Tabletop.js to get data from the Google Spreadsheet as well a template system like that including in Underscore.js to make it look good.
I have started a basic spreadsheet here:
https://docs.google.com/a/opentwincities.org/spreadsheet/ccc?key=0AoH-VJHQACf4dEhkNTgtdG1PRlduYnRLd2g4clBaWWc
I am not sure what is the most appropriate way to handle input. I think having it editable by anyone could end up a bit bad, but we don't want to be gate keepers for it. We could also look at a mix of editing directly and Google Form submissions. Ideas?
The text was updated successfully, but these errors were encountered: