Hey Zypho, thanks for your feedback :) I mentioned that I really built Column to solve my own problems first (my fiance might say I need medication, not more s

Hey Zypho, thanks for your feedback :) I mentioned that I really built Column to solve my own problems first (my fiance might say I need medication, not more software), I happen to be a real-time/node/web-app developer, and participate in hackathons, so you've hit the nail on the head with your last statement :) I'm hoping that just bringing some attention to this issue, and how we're trying to solve it will help teams recognize that preparation is critical, and an easy way to make participating in a hackathon both more fun, and more informative. One important point that I think you're making here, is that we need to defend each choice, for example: What makes Swig a good hackathon templating solution? Debate is important, debate will help us reach some consensus over which tools make appropriate defaults and why. So when the argument begins (hopefully prior to the hackathon), why this tool? You can point them to a landing page which provides the key benefits of each tool, with links to the documentation, and whatever else might help a team get started.