Delicious Simplicity: Gatsby Is A Gamechanger
- 1. Brian Webster, Delicious Simplicity Gatsby as a legit gamechanger for our team
- 2. ( but we are 100% apolitical ) - NPOs - Radio/Video broadcasting companies - News media sites - Political commentary sites ABOUT DELICIOUS SIMPLICITY Who we serve
- 3. Agency Life B.G. ( Before Gatsby ) THE PAST Part 1 of 3
- 4. Dark Ages - Flash sites - Custom .Net & PHP - Basic HTML Age of Discovery - Static site generators - Decoupled CMS architectures - Single-page apps 2009 AND BEFORE Open-Source Renaissance - Full-stack Drupal & Wordpress sites 2009-2016 2016-2018
- 5. AND THEN, THERE WAS Gatsby Part 2 of 3
- 6. AND THEN, THERE WAS Gatsby Part 2 of 3
- 7. QUOTH THE DEVELOPER: “The best from static site generators, headless CMS, and single page apps—all of those things combine in Gatsby.”
- 8. SLOW & STEADY How we converted 90% of our projects to Gatsby in under a year - Assessed the functionalities of every project - Slated projects according to complexity - Conquered 1-2 new, unsolved functionalities per project - After initial learning curve, we gained some serious momentum
- 9. EXTENDED METAPHORS AHEAD Gatsby and clients
- 10. GATSBY + CLIENTS Pitching the tech stack Nothing helps communicate technological complexity quite like a solid metaphor. Here’s ours...
- 11. You could choose a boombox monolithic CMS/Framework...
- 12. Or... You can assemble the perfect modular audiophile content setup with Gatsby at its center.
- 13. ...and audio content sources for the very best experience.
- 14. QUOTH THE DEVELOPER: “Because of Gatsby, we finally have the ability to choose exactly the right tools to best suit the content.”
- 15. GATSBY + CLIENTS “Gotchas” we’ve encountered - Waiting on builds for large sites… Time to live - Need for preview environment… ( but now there’s Gatsby Preview ) - Redefining the notion of a “static” site
- 16. GATSBY + CLIENTS “Ah ha” moments we’ve witnessed - Security - Hosting costs - Supported & familiar products - Trust building & use of budget - As a result, we’re winning bids
- 17. NERDING OUT How Gatsby changed our dev team
- 18. GATSBY + DEV TEAM Back to the future - A return to the basics of HTML and CSS - Local environments and workflow - Reusability from project to project - Much easier to step away and return to a project without skipping a beat
- 19. GATSBY + DEV TEAM Lights-out performance - Sleeping better at night knowing the site’s uptime is almost guaranteed - Unbelievable Lighthouse scores out of the box - Ease of upgrading between versions - Feels like “writing in one language”
- 20. GATSBY + DEV TEAM Empowering the front-end devs - Ease of learning curve - Outstanding plugins and documentation - Component thinking bringing together our design/front-end/dev team - Tasks that were formerly ‘red lines’ for front-end devs are now accomplishable
- 21. QUOTH THE DEVELOPER: “I wouldn’t be making functional components if the tech didn’t meet me halfway. I never imagined being able to do this level of work as a front-end dev/themer.”
- 22. QUOTH THE DEVELOPER: “It’s like we gained additional dev staff without hiring anybody.”
- 23. GATSBY + DEV TEAM Serious stack envy - Formed new partnerships with dev teams seeking us out, wanting to work in this tech - Helped solve persistent hiring, scale and capabilities ceilings
- 24. “THE FUTURE, MR. GITTES!” What we’re solving next Part 3 of 3
- 25. THE FUTURE Technically speaking - Staying focused on streamlining our workflow and writing reusable components - Continuing to tackle new challenges with each project - Performance, build times, and time to live ( incremental builds are coming )
- 26. THE FUTURE Big picture - Expanding the team and more collaborations - Giving back and being active in the community - Staying curious with new tech - Saying “yes” to more projects
- 27. Gatsby as a legit gamechanger for our team
- 28. Gatsby as a legit gamechanger for our your team