Easier flow with data-driven builds

[guahanweb]

This is more a recommendation than an issue, but I'd be interested in taking it on if nobody has issue with the idea. This site is currently just a managed list, and there are a lot of manual updates to the markup to add, update, or change content. I believe the site might be easier to keep current if we moved it to a simple build relying on a config file with all the conferences listed.

If this were done today, the data could be something as simple as this in JSON:

{
  "official": [{
    "id": "jsconfus",
    "name": "JSConf US",
    "logo": "//2015.jsconf.us/img/js-sized.png",
    "site": "//2018.jsconf.us",
    "status": "onsale"
  }, ...],
  "family": [ ... ]
}

Wrapping some simple PUG templates with an NPM script to build out the entire site from this structure would be a straightforward task. What might be considered, though, would be having a separate repository (something like jsconf.com-source) in which contributions are accepted and merged. Once merges take place, we could set up Travis CI to automatically build the main site and either push or PR against this repo with those changes.

I'd be interested in hearing thoughts on something like that before I put any effort into it.