Ghost & Ember

13bc3aed226e3d7b0d262e5664468f50?s=47 Hannah Wolfe
October 29, 2015

Ghost & Ember

Looking back at our experiences of choosing, implementing and using Ember in Ghost and the impact the switch has had on the project.

13bc3aed226e3d7b0d262e5664468f50?s=128

Hannah Wolfe

October 29, 2015
Tweet

Transcript

  1. & EMBER Hannah Wolfe | @ErisDS

  2. None
  3. Just a blogging platform

  4. None
  5. None
  6. None
  7. None
  8. Not for profit Money © 2014 Aaron Patterson, Flickr MADE

    FOR LOVE
  9. Sustainable

  10. None
  11. None
  12. Server Blog Client Admin HTTP require JSON API

  13. BEFORE EMBER

  14. None
  15. None
  16. None
  17. AMBITIOUS components

  18. move FASTER BREAK less things

  19. None
  20. None
  21. None
  22. Single page app?

  23. Ugly routing

  24. No data binding

  25. View related memory issues

  26. Poor mobile support

  27. Lacking direction on how to solve problems

  28. Issue #2144

  29. Lacking direction on how to solve problems

  30. We needed a RULEBOOK

  31. CHOOSING EMBER

  32. None
  33. THE MIGRATION

  34. JSON API

  35. Server Blog Client Admin HTTP require JSON API

  36. Server Blog Client Admin HTTP require JSON API ???

  37. Client Admin JSON API

  38. None
  39. None
  40. ONE YEAR LATER

  41. Did we make the right choice?

  42. YES!

  43. Did Ember allow us to reach our goals?

  44. Not yet…

  45. COMPLEXITY

  46. Complexity in a client-side JS app Time Complexity

  47. Time Complexity Complexity in a client-side JS app

  48. Complexity in an Ember app Time Complexity

  49. Complexity in an Ember app Time Complexity

  50. None
  51. SURMOUNTING the learning curve

  52. None
  53. TESTING

  54. None
  55. Ember moves REALLY FAST

  56. None
  57. Triumph of COMMUNITY

  58. No getting STUCK

  59. The power of OPEN SOURCE

  60. THANK YOU Hannah Wolfe | @ErisDS

  61. GHOST.ORG/SLACK Join our community