A few weeks ago the DX team at @Netlify cancelled our planned offsite where we would have hung out together and that made me sad.
We're about to have a zoom call called "Happy Hour" and I don't know what the next 50 minutes will bring, but it's 8pm for me so I have gin.

Phil Hawksworth
@philhawksworth •
Calls with @rafahari are not always 100% free from distractions. https://twitter.com/rafahari/status/1242843681889058817

@futuregerald Wait... were we all supposed to keep you so informed?
Noted.
Noted.

@jlengstorf @snookca @EliFitch I interpret this as: "time to change from work pyjamas into casual evening pyjamas"

@_shirish @Netlify @tracker_corona @cherhan I would very much expect so.
Information about this, and the form where you can apply and get directly into that process are here
š https://www.netlify.com/blog/2020/03/22/coronavirus/covid-19-support/?utm_source=twitter&utm_medium=covidsupport-sd&utm_campaign=devex
Information about this, and the form where you can apply and get directly into that process are here
š https://www.netlify.com/blog/2020/03/22/coronavirus/covid-19-support/?utm_source=twitter&utm_medium=covidsupport-sd&utm_campaign=devex

Phil Hawksworth
@philhawksworth •
Big up to all those people making resources to try to help inform and support during these difficult times. I hope that this can make those efforts even a tiny bit easier. https://twitter.com/sarah_edo/status/1242466260870258693

Phil Hawksworth
@philhawksworth •
Some great insights on busting the myth about static assets resulting in static experiences from @ondrabus in this @freeCodeCamp article.
https://www.freecodecamp.org/news/how-to-make-static-site-dynamic/
https://www.freecodecamp.org/news/how-to-make-static-site-dynamic/

@stefanjudis @contentful YES!

@stefanjudis @contentful Woah! That's excellent news!
@contentful are so lucky to have you back. š
@contentful are so lucky to have you back. š

Phil Hawksworth
@philhawksworth •
RT @Netlify: Have a WordPress site that you're ready to migrate to the JAMstack? We have the perfect post to walk you through just that! Frā¦

@Mandy_Kerr Thaaaatās the stuff.

@Mandy_Kerr This conversation is fine, but where is my next JelloWire update?!?!

@Amys_Kapers @Mandy_Kerr Same. This is the content hole I currently have in my life.

@Mandy_Kerr You mean, instead of āinformation super-highway cyber bulletinā?

@MiriSuzanne @eleven_ty @hankchizljaw @realglenndixon @nejsconf @zachleat @nhoizey There needs to be another showcase championing the best domain names (because these are great!)

@paul_melero @Netlify @cloudinary @NetlifyCMS Sure. You can redirect/rewrite/proxy any path to any place.

Phil Hawksworth
@philhawksworth •
This is an oft overlooked trick. Wishing I had it at my disposal when working with lots of big brand clients in the past. https://twitter.com/Netlify/status/1242049839644409858

@feather #NotAllHeroesWearCapes

@zachleat @MiriSuzanne I believe they should be the same. But following any deploy, the very first request for a new asset at each CDN node will go to the origin. After that it will be cached at the edge. So itās worth making some requests before benchmarking.

Phil Hawksworth
@philhawksworth •
RT @devdevcharlie: I miss going for a run so I made a thing to make running inside less weird...
Called it Qua*run*tine... Get it? š„
Usiā¦
Called it Qua*run*tine... Get it? š„
Usiā¦

@BrettStark @freeCodeCamp Hi Brett!
Note that the src path to the js is ā/js/vibe.jsā. Since thatās root relative, a browser will not find it if the index file is just opened from the file system. (It would if the path was ā./js/vibe.jsā)
But ānpm startā will serve it all up for you with a local server.
Note that the src path to the js is ā/js/vibe.jsā. Since thatās root relative, a browser will not find it if the index file is just opened from the file system. (It would if the path was ā./js/vibe.jsā)
But ānpm startā will serve it all up for you with a local server.

@jaffathecake Both kinds are the best kind.