@richhiggins I recommend making contact from here: https://www.netlify.com/enterprise/
Tell 'em Phil sent you :)
And I can introduce you if needs be.
😎

@nmeth Thank you! It's my family home. Always nice to return.

Phil Hawksworth
@philhawksworth •
Taking a cheeky stroll for a morning coffee https://ift.tt/2Nx5AXI


@BrkSchoenfield @Netlify @troyhunt Did you watch the video? It had a good explanation. It's not about keeping the content secret. But about being confident as a user that the content you receive can be trusted and not interfered with on its way to you.


@joelycett I think you know why I'm writing to you, you bitch!
Actually perhaps not. Thank you for a wonderful gig. It was joyous. I also loved your message and that you were collecting for @crisis_uk
Bravo on all counts.
#rhubarbbikiniforever
Actually perhaps not. Thank you for a wonderful gig. It was joyous. I also loved your message and that you were collecting for @crisis_uk
Bravo on all counts.
#rhubarbbikiniforever

@papascott @gatsbyjs @Netlify Excellent!

@KBBS @michael_mardahl @Netlify @GoHugoIO My "static" site updates automagically whenever:
✨ I post a tweet
✨ I write a blog post
✨ I approve a comment
✨ I commit a code change
Fun times over on the #JAMstack!
😎
✨ I post a tweet
✨ I write a blog post
✨ I approve a comment
✨ I commit a code change
Fun times over on the #JAMstack!
😎

Phil Hawksworth
@philhawksworth •
I like having a standing desk. Just as well, because my desk chair usually looks like this. https://ift.tt/2NWfOlu

@nola_will @Netlify Ha ha. Not yet... this is happening on August 9th. I'm not sure if it will be recorded, but I'll share slides and materials afterwards.

@bepsays @zachleat @eleven_ty @Netlify @npmjs Oh, I thought you were frowning at something different. I misunderstood. So, are you saying, "just don't add dist to your .gitignore"?
Thus also storing the build output in case of far future build dependency calamity.
🙂
Thus also storing the build output in case of far future build dependency calamity.
🙂

@zachleat @bepsays @eleven_ty @Netlify @npmjs And FWIW, unless your dependencies change (or rather, unless your package.json changes) @Netlify will run the build with the same stashed dependencies, not reinstall them each time.
But yeah... bracing for a cryptic reminder in 2023: "hold breath and hit deploy"
But yeah... bracing for a cryptic reminder in 2023: "hold breath and hit deploy"

@bepsays @Netlify @eleven_ty I don't know about Jekyll, but in the setup @eleven_ty seems to have, a branch which has not been updated for a long time would just build and deploy when you push a change.

@bepsays @Netlify @eleven_ty They will be the builds of the latest commit to the specified branch. Unless they are locked. Deploys in @Netlify can be locked too, so commits stop triggering builds.

@phiberoptik @Netlify That's a very kind thing to say!
I am very lucky. I get to talk about the cool things you can do with @Netlify. I wish I could take the credit. But the truth is, there are talented folks here planning, designing, building and supporting it all.
I just give out the stickers! 😎
I am very lucky. I get to talk about the cool things you can do with @Netlify. I wish I could take the credit. But the truth is, there are talented folks here planning, designing, building and supporting it all.
I just give out the stickers! 😎