April - PWAs, JAM and Headless CMS

Are you going?

25 spots left

Location image of event venue


PLEASE NOTE: RSVPs will be opened on the 17th!

This month we have Jamie Bradley and Sam Beckham with us for an acronym packed event! We'll also be giving away 2 codes for a year subscription for a Jetbrains toolbox product of your choice and a ticket for the Amsterdam JSNation conference!

6:30 - 6:45: People start arriving
6:45 - 6:50: Introductions
6:50 - 6:55: Job Pitches - Give a shout out for any jobs you have
6:55 - 7:25: Jamie Bradley (@jamiebradley234) - Finding My Sanity
7:25 - 7:35: Break with food and chat
7:35 - 8:20: Sam Beckham (@samdbeckham) - Making GitLab a PWA
8:20 - 8:30: Prize draw and closing remarks

Jamie Bradley (@jamiebradley234) - Finding My Sanity
Following my previous talk "What the JAMstack" my talk will revise the basics of JAMstack i.e. what it is, why it’s becoming so popular and also some of the potential drawbacks with using JAMstack. I will then follow up with a demonstration of a project using Gatsby along with a Headless CMS solution called Sanity. I will showcase how this fits into the JAMstack and why it is proving to be a success.

Sam Beckham (@samdbeckham) - Making GitLab a PWA
This is not your typical PWA talk. We're not going to make a dummy application that's perfectly tailored for use with a PWA, then show you just how easy it is to turn it into one. We're not going to talk about how much faster, or how much more useful our website is now that it's a PWA. We're not even going to make anything particularly useful.

I'm going to show you how to use the concept of "the boring solution" to make small changes to a big application. Small changes that, over time, turn in to large ones. Specifically, my process of turning GitLab into a "PWA" in less than 100 lines of code.

This is a real story of GitLab's journey to a fully fledged PWA. One small step at a time.

Please note the group is intended for people looking to expand their knowledge. While recruiters are welcome to come and learn, we operate a strict no active recruitment policy, outside of the job pitches at the start of the event.
Code of conduct - https://leedsjs.github.io/code-of-conduct/