Rethinking general structure

[aaronlidman]

I'm not sold on this template idea, copying the template and putting the settings inline for each new import. We would end up with many template urls like: http://osmly.com/laparks, http://osmly.com/tigerwater, http://osmly.com/blahpois good descriptive urls but too many dumb files sitting around in gh-pages. I want something quickly interchangeable, a query string.

Idea: settings live in a github gist, they get pulled down on start. If no settings query: index.

This removes the distinction between index and template but also the need for many templates. Index would have to be built in js, osmly.index. Import urls would look like this: http://osmly.com/6515737 for the associated gist. Could also probably do with a single branch because of it. Need to try it out, see what the downsides there are.

[aaronlidman]

What if we just use another table? I've been thinking of using a general purpose k/v table on the database for comments (allowing users to also comment on any problems, notes to reviewers, etc...) mostly doing everything via json. Just keep settings in a special place in this table. Administrative users can edit the settings through some special modal with basic forms for the settings (checkboxes, radio buttons) and inline documentation about what each setting does. This would allow for imports just defined by their database, allowing for a single template using a simple query string. http://osmly.com/laparks -> laparks.sqlite -> fetch settings.