re inventing
play

Re-inventing js.com Hi, Im Katie @katie_fenn Hi, Im Katie - PowerPoint PPT Presentation

Re-inventing js.com Hi, Im Katie @katie_fenn Hi, Im Katie @katie_fenn Hi, Im Katie @katie_fenn cw: animation work at make the npmjs.com website also support the registry from sheffield @katie_fenn disclaimer:


  1. Re-inventing js.com

  2. Hi, I’m Katie @katie_fenn

  3. Hi, I’m Katie @katie_fenn

  4. Hi, I’m Katie @katie_fenn cw: animation

  5. • work at • make the npmjs.com website • also support the registry • from sheffield @katie_fenn

  6. disclaimer: this talk is not about performance @katie_fenn

  7. L et’s go back to the beginning @katie_fenn

  8. june 2010 landing page @katie_fenn

  9. december 2010 becoming a portal @katie_fenn

  10. august 2012 community hub @katie_fenn

  11. february 2015 company homepage @katie_fenn

  12. september 2015 marketing pages @katie_fenn

  13. march 2018 what’s next? ??? @katie_fenn

  14. • orgs • private repos services • 2fa • access tokens • ??? @katie_fenn

  15. identity crisis harder to develop @katie_fenn

  16. identity crisis isolated developers @katie_fenn

  17. technology crossroads @katie_fenn

  18. technology crossroads @katie_fenn

  19. humans technology @katie_fenn

  20. Humans @katie_fenn

  21. follow the lead of the community @katie_fenn

  22. webpack • postcss react next.js redux jest enzyme • vue @katie_fenn

  23. embrace the frontend @katie_fenn

  24. node package manager @katie_fenn

  25. 80% of users use npm for frontend development @katie_fenn

  26. @katie_fenn

  27. @katie_fenn

  28. we get it you’re feeling pain @katie_fenn

  29. we hired more frontend developers @katie_fenn

  30. website developers are reporting bugs in npm client and registry @katie_fenn

  31. lines blurring between registry and website developers @katie_fenn

  32. generalists are important to us @katie_fenn

  33. is 32 people @katie_fenn

  34. • shared knowledge ownership sharing • reuse code across projects @katie_fenn

  35. Technology @katie_fenn

  36. so, what about express? @katie_fenn cw: animation

  37. nope. @katie_fenn

  38. nope. @katie_fenn

  39. there was a better option: spife @katie_fenn

  40. “doesn’t that make it hard to hire spife developers?” - anonymous npm employee @katie_fenn cw: animation

  41. “doesn’t that make it hard to hire spife developers?” - anonymous npm employee @katie_fenn cw: animation

  42. “it’s good for finding people within npm ” - anonymous npm employee @katie_fenn cw: animation

  43. “it’s good for finding people within npm ” - anonymous npm employee @katie_fenn cw: animation

  44. 1. spife a batteries-included http framework @katie_fenn icon: cutlery by Chanut is Industries from the Noun Project

  45. 1. spife routing • db • orm a middleware monitoring batteries-included logging http framework metrics • auth @katie_fenn

  46. 1. spife • familiar opinionated • asynchronous djavascript • structured • comfortable @katie_fenn icon: cutlery by Chanut is Industries from the Noun Project

  47. 1. spife middleware and decorators @katie_fenn

  48. 1. spife middleware API data and decorators @katie_fenn

  49. 1. spife middleware API data rate limit and decorators @katie_fenn

  50. 1. spife middleware API data rate limit check csrf and decorators @katie_fenn

  51. 1. spife middleware API data rate limit check csrf and auth decorators @katie_fenn

  52. 1. spife middleware API data rate limit check csrf and auth validate decorators @katie_fenn

  53. 1. spife middleware API data rate limit check csrf and auth validate schema decorators @katie_fenn

  54. spife is open source @katie_fenn

  55. 2. design system react components with css modules @katie_fenn

  56. 2. design system components encapsulate standards @katie_fenn

  57. 2. design system components encapsulate standards @katie_fenn

  58. 3. spiferack a react • built-in server-side-rendering • built-in code splitting framework • progressive enhancement @katie_fenn

  59. 3. spiferack server-side • searchable content rendering • fast initial page renders @katie_fenn

  60. 3. spiferack code • automatically split per-route splitting • spreads bundle loading evenly @katie_fenn

  61. 3. spiferack <Form action=“/login” method=“POST> <InputText progressive name=“username” label=“Username" /> enhancement <InputPassword name=“password” label=“Username" /> </Form> @katie_fenn

  62. 3. spiferack • enhances to XHR requests progressive when JS is enabled enhancement • returns JSON response when XHR request is received @katie_fenn

  63. 3. spiferack make doing the right thing easy @katie_fenn

  64. preview.npmjs.com @katie_fenn

  65. preview.npmjs.com @katie_fenn

  66. it’s much better and we hope you’ll love it @katie_fenn

  67. 1. registry 2. cli 3. website @katie_fenn

  68. Where are we going? @katie_fenn

  69. make doing the right thing easy @katie_fenn

  70. tooling that embraces short-range sharing @katie_fenn

  71. a focus on making tech work for people rather than computers @katie_fenn cw: animation

  72. aesthetics @katie_fenn cw: animation

  73. aesthetics accessibility @katie_fenn cw: animation

  74. new and shiny @katie_fenn cw: animation

  75. new and shiny tried and trusted @katie_fenn cw: animation

  76. performance @katie_fenn cw: animation

  77. performance resilience @katie_fenn

  78. computers do things better @katie_fenn

  79. computers do things better faster Jenn Schiffer @katie_fenn cw: animation

  80. Thank you @katie_fenn @npmjs preview.npmjs.com @katie_fenn

  81. Thank you @katie_fenn @npmjs preview.npmjs.com @katie_fenn

Recommend


More recommend