Upgrade to Pro — share decks privately, control downloads, hide ads and more …

New Stack Lunch Presentation

New Stack Lunch Presentation

Lunch Presentation at Zendesk

A731bc19c3b04919610fcee6d0589914?s=128

Mathias Biilmann

March 07, 2016
Tweet

Transcript

  1. The New Stack Chris Bach & Matt Biilmann, Netlify 2016

    1
  2. The Web Dev Toolchain Disrupted • Modern Build Tools •

    Modern Browsers • Modern APIs • CDN Hosting 2
  3. Push your web-app or site to netlify. - the modern

    day platform that developers use to manage and publish their content online. 3
  4. Butterfly Butterfly Effect In chaos theory, the butterfly effect is

    the sensitive dependence on initial conditions in which a small change in one state of a deterministic nonlinear system can result in large differences in a later state. 4
  5. "I'm writing some scripts to try to track things a

    whole lot faster." Thu Apr 07 2005, Linux-Kernel Mailing List 5
  6. Made by MarketMe GitHub launched February 2008, grew to 10

    million repositories within the first 5 years, now has more than 10M active users. 6
  7. 10 Years Ago 7

  8. Or today? For many Wordpress developers 8

  9. Git Centric Workflow • Anything that’s text based goes in

    a git repo • Clone, fork, push and pull all the time • Git has become as essential as our text editors 9
  10. Another Detour • GitHub rode the Rails wagon • Rails

    came with Rake • Task runners went mainstream 10
  11. Front-end Build Tools • All modern front-enders use build tools

    and task runners • Grunt, Gulp, Webpack, Ember-CLI • Jekyll, Middleman, Roots, Hugo, Metalsmith 11
  12. Git Centric Workflow Any front-end project at netlify should work

    somewhat like this 12
  13. Git Centric Workflow After the initial clone, the flow becomes

    something like this 13
  14. Pull • Watch • Push 14

  15. Pure Front-Ends • Not mixed with backend code or dependency

    • All you need is in Git • No database, message queue, search engines, etc… 15
  16. 16

  17. Pull • Watch • Push Gulp + Jekyll, BrowserSync, No

    Backend 17
  18. APIs Dynamic needs handled by 3rd party widgets Made by

    MarketMe 18
  19. Most Dev Friendly Setup • All content live Markdown or

    YAML files • Everything in version control • Use all of our text based dev tools 19
  20. 20

  21. Single Page App • Run full front-end app locally with

    no dependencies • Run locally against production API • Pure front-end, completely decoupled from backend 21
  22. Made by MarketMe 22 The Production Story

  23. Pull • Build • Push 23

  24. JavaScript, APIs & Markup • Can run anywhere • Distribute

    on Global CDN nodes • Faster, Safer, Simpler & Cheaper 24
  25. Intelligent CDN • Atomic Deploys • Instant Cache Invalidation •

    Routing intelligence: Proxying, GeoIP, Authentication 25
  26. 26

  27. Example: WeWork • Gradual transition from Rails to Roots •

    No huge rewrite • Proxy all non-static requests to legacy origin 27
  28. One Rule netlify intelligently proxies only URLs with no corresponding

    file 28
  29. 29

  30. Closing the Circle 30

  31. 31

  32. 32

  33. Example: Sequoia • Large site: ~15,000 HTML Pages • Fetches

    data from Contentful + Job API • Trigger rebuild whenever content change 33
  34. 34

  35. Content Editors? • How to get your marketing team on

    board? • Ideal dev cycle, but what about non-techies • Normal people are not int “Git Centric Worflows”! 35
  36. 36

  37. Thanks! Matt Biilmann www.netlify.com @biilmann 37