speaker write make a pull request moderator publish merge the pull request system provide GitHub and GitHub Pages Berlin.JS | 2014-02-20 | Anton Wilhelm | @timaschew
the file to edit on github.com/berlinjs/berlinjs.org 3. click on edit 4. change the content in the HTML code 5. commit & confirm automated created Pull Request Berlin.JS | 2014-02-20 | Anton Wilhelm | @timaschew BERLIN.JS STATUS QUO SPEAKER MODERATOR SYSTEM
the file to edit on github.com/berlinjs/berlinjs.org 3. click on edit 4. change the content in the HTML code 5. commit & confirm automated created Pull Request Berlin.JS | 2014-02-20 | Anton Wilhelm | @timaschew BERLIN.JS STATUS QUO SPEAKER MODERATOR SYSTEM - GitHub account - no preview - HTML format - 2.8 MB traffic CONS
on plus (create new file) 3. write the talk description in Markdown and save 4. confirm and send auto generated pull request Berlin.JS | 2014-02-20 | Anton Wilhelm | @timaschew SPEAKER MODERATOR SYSTEM SOLUTION 1 - Markdown PROS - GitHub account - preview without context - 1.8 MB traffic CONS without context preview
the repo & fork it 3. clone repository on your local machine 4. create file and write the content 5. download ruby 6. install gems for Jekyll 7. run Jekyll 8. preview in the browser 9. commit and push the changes to your fork 10. send a pull request with context preview Berlin.JS | 2014-02-20 | Anton Wilhelm | @timaschew SOLUTION 1.1 SPEAKER MODERATOR SYSTEM - Markdown - preview PROS - GitHub account - complex steps with env. setup CONS
use email as fallback • write talk proposal in the browser • preview without environment setup • don't break current architecture • GitHub Pages & pull request Berlin.JS | 2014-02-20 | Anton Wilhelm | @timaschew SOLUTION 2 SPEAKER MODERATOR SYSTEM goals
Anton Wilhelm | @timaschew SPEAKER MODERATOR SYSTEM SOLUTION 2 http://berlinjs.github.io/berlinjs.org http://berlinjs.org git:berlinjs-bot/berlinjs.org authenticate master .jade .md fork fetch upstream create .md commit & pull request SPEAKER MODERATOR deploy merge pull request DocPad .jade .md src out .html POST /submit submit & receive mail GET /confirm/:token click on activation link Node.js pull
click on submit A. receive mail & click on activation link B. use GitHub auth instead of email Berlin.JS | 2014-02-20 | Anton Wilhelm | @timaschew SPEAKER MODERATOR SYSTEM SOLUTION 2 PROS - no GitHub account - Markdown - preview - mobile devices - less than 200 KB traffic
server 3. wait for regeneration to review 4. deploy Berlin.JS | 2014-02-20 | Anton Wilhelm | @timaschew SPEAKER MODERATOR SYSTEM SOLUTION 2 - staging / explicit deploying PROS - two more steps CONS
deploying with DocPad • Node.js: • save talk proposal • send email activation link • use GitHub API for pull request SPEAKER MODERATOR SYSTEM Berlin.JS | 2014-02-20 | Anton Wilhelm | @timaschew SOLUTION 2 - automatically dates, talk slots PROS - setup DocPad - Node.js CONS
submitting a talk • edit a file / update an existing pull request • auth via GitHub • decapsulate and make an npm module ToDo Berlin.JS | 2014-02-20 | Anton Wilhelm | @timaschew SPEAKER MODERATOR SYSTEM