berlinjs / new-berlinjs.org Goto Github PK

We got a few questions at Twitter and via email why the new website is a static website instead of some node.js backed thing, as we are a JS community after all. Here's why:

• we want to focus on organizing great events, not on hosting a website or maintaining software
• GitHub pages has proven to be pretty stable and worked well for us and others in the past
• we want to make submitting a talk as easy as submitting a pull request
• we can merge the Pull Request from everywhere.
• no permission bureaucracy. Want to fix a typo? Submit a talk? Help out? Submit a pull request.
• easy backup
• easy to fork, which enables other meetup groups to use the resources and start their own (yay community!)
• clean history in case of something goes wrong, or a password got lost (and passwords do get lost a lot)
• zero dependencies for just adding something to the website
• no build process required

A note on the last point: We'll use Jekyll eventually, so to preview the site locally you'll have some dependencies then. Still, submitting a talk will be just markdown. Jekyll is fully supported by GitHub pages so you don't need to install it locally.

Hope that helps to understand the reasoning behind the website and why we do things like we do.

Thanks everyone for helping and giving feedback so far.

A thing that worked really well with the old BerlinJS website is that you can see which talks are planned on the frontpage and you even see placeholders if there are talk spots left. I think we should have that for the new website too.

This issue is basically a placeholder for discussion about the use of Jekyll and the details thereof. There's a “jekyll” branch where work is happening.