
@sarah_edo From my cold, dead hands.

@SlexAxton @nejsconf You got my hopes up!
Sadly having to miss @artifactconf in Austin this year, yeah which would have been a great opportunity. But...
A whole week in October - San Francisco. (For @jamstackconf)
Sadly having to miss @artifactconf in Austin this year, yeah which would have been a great opportunity. But...
A whole week in October - San Francisco. (For @jamstackconf)

@crgeary It was!
Except that I was literally saying “stop it stop it stop it” to myself during my final mouthfuls.
Outrageous.
Except that I was literally saying “stop it stop it stop it” to myself during my final mouthfuls.
Outrageous.

@brianleroux @swyx This!

@thespite That’s amazing.

Phil Hawksworth
@philhawksworth •
Popped out for a quick sandwich, but I tripped and my face landed on this.
It’s fine. Right?
It’s fine. Right?

Phil Hawksworth
@philhawksworth •
Mobile banking security question: What are you wearing? https://twitter.com/rem/status/1159540904165826561

@iamposti @frontity Hi Pablo. This looks most interesting. Let me do a little investigating.

Phil Hawksworth
@philhawksworth •
RT @smashingconf: 📹 Do we really need this JAMstack thing? And what even is it? Watch @philhawksworth give you a practical JAMstack tour at…


@jupiterorbit @nejsconf You read that right.

Phil Hawksworth
@philhawksworth •
Tomorrow is @nejsconf and I don’t mind saying that I’m really rather excited about it.
Only been in Omaha a few hours but I’ve already managed to enjoy:
🥩 Steak.
🍦 Cucumber sandwich ice cream.
What a time to be alive.
Only been in Omaha a few hours but I’ve already managed to enjoy:
🥩 Steak.
🍦 Cucumber sandwich ice cream.
What a time to be alive.

@DavidDarnes @maggerbo @Ghost @eleven_ty @Netlify ... or data files.
Most SSGs have some notion of collections of data as files in a data folder.
I used to regularly generate those from various APIs via gulp.
Most SSGs have some notion of collections of data as files in a data folder.
I used to regularly generate those from various APIs via gulp.

@dotNetCoreShow @Netlify @GoHugoIO For launches and releases, at @Netlify (!) we’ll often disable auto-publishing then build our release. This locks the site while readying the new version. Then you can release it in seconds.
@biilmann did this on stage in the video here:
https://www.netlify.com/blog/2019/07/10/netlify-analytics---accurate-insights-without-performance-impacts/
@biilmann did this on stage in the video here:
https://www.netlify.com/blog/2019/07/10/netlify-analytics---accurate-insights-without-performance-impacts/

@bepsays @dotNetCoreShow @Netlify @GoHugoIO A good place to start might be the @zapier integration. But yes, anything that can make an http post request can be your trigger.
https://www.netlify.com/blog/2018/11/07/automate-your-netlify-sites-with-zapier/
https://www.netlify.com/blog/2018/11/07/automate-your-netlify-sites-with-zapier/

@DavidDarnes @maggerbo @Ghost @eleven_ty @Netlify A pattern I’ve used for a lot with a variety of SSGs is to have something like Gulp run the build. It pulls data from APIs, stashes it in the data files the SSG prefers, then generates the site with the SSG.
This can keep your options open so you can choose the tool you prefer.
This can keep your options open so you can choose the tool you prefer.

@sarah_edo @dizzyd Blimey!

Phil Hawksworth
@philhawksworth •
RT @wptavern: O’Reilly Partners with Netlify to Publish Free E-Book: Modern Web Development on the JAMstack https://wptavern.com/oreilly-partners-with-netlify-to-publish-free-e-book-modern-web-development-on-the-jamstack https:/…

@9600 If the stonework is impeccable, it would be a shame to disturb it though. Craftsmanship is craftsmanship.