@brucel @smashingconf Bruce doesn't know better but I'm disappointed in the rest of you. Making a note of all of the people who *like* this tweet. Consider your cards marked.
OMG! Thanks is now by favourite tweet of all time.
I will now ONLY do workshops where @rafahari is available to perform this move! https://twitter.com/rafahari/status/961640252036276226
I will now ONLY do workshops where @rafahari is available to perform this move! https://twitter.com/rafahari/status/961640252036276226
@JoCoOne @smashingconf No cigar for you, I'm afraid.
Emojis are not the official theme... they're just awesome.
😎🚇😎
Emojis are not the official theme... they're just awesome.
😎🚇😎
@simonmcmanus @Netlify @greenkeeperio You can fire webhooks based on different events such as a successful/failed build. And you can trigger builds on different branches via an incoming web hooks.
So it is more like you have the Lego pieces to make this, rather than having the specific feature you mentioned.
So it is more like you have the Lego pieces to make this, rather than having the specific feature you mentioned.
SO many valuable points in @aemcknig's #SmashingConf talk. We often overlook the importance of creating the a culture that values performance in favour of focus on the details of how to do so technically. One can't succeed without the other. https://twitter.com/albertonarda/status/961631662621777920
@simonmcmanus @Netlify Looks to me like these tests could run in a build in a project on @netlify, which you trigger with a webhook whenever the target site finishes a successful build (of master/branch/pr whatever.
(Just my first thought after a peep while in a talk at smashing though!)
(Just my first thought after a peep while in a talk at smashing though!)
@EugeneMolari @Netlify Yep. The gulp task called get:tweets fetches tweets from twitter's API and saves then to a file in the project.
Then the build runs @GoHugoIO to generate the site, which uses the tweets it finds in data/tweets.yml to populate some of the templates.
Then the build runs @GoHugoIO to generate the site, which uses the tweets it finds in data/tweets.yml to populate some of the templates.
@EugeneMolari @Netlify Thanks Eugene!
And go nuts. All the code for my site is on Github. Help yourself. But don't judge me on some of my wobbly JavaScript!
😬
https://github.com/philhawksworth/hawksworx.com
And go nuts. All the code for my site is on Github. Help yourself. But don't judge me on some of my wobbly JavaScript!
😬
https://github.com/philhawksworth/hawksworx.com
Happy to have finished my first ever #SmashingConf lunchtime workshop session with *nobody* throwing food.
Fun. But at bit fast.
THANK YOU if you squeezed in to join me for that. Please don't hesitate to shout questions about @Netlify or #JAMstack my way. https://twitter.com/VeryThorough/status/961606627551047680
Fun. But at bit fast.
THANK YOU if you squeezed in to join me for that. Please don't hesitate to shout questions about @Netlify or #JAMstack my way. https://twitter.com/VeryThorough/status/961606627551047680
@_leilaura @Netlify @smashingconf TFW someone closes the projector screen before you've even finished describing the workshop agenda.
Pretty emphatic feedback! LOL.
But I *would not be deterred* !
Pretty emphatic feedback! LOL.
But I *would not be deterred* !
For those at #smashingconf today with questions about @Netlify, I'll be holding a show and tell session at lunch time where you can ask me anything.
http://bit.ly/netlify
http://bit.ly/netlify
@AndyDavies @Una @patrickhamann Totally! Perfect blend of knowledge, enthusiasm and warmth. Can't help feeling like we are in very safe hands.
At #smashingconf and interested in seeing some more examples of how to get started with @Netlify?
Join me for a lunchtime show and tell on day 2.
https://ti.to/smashingmagazine/ldn-lunch/with/nkam7kefmic
We'll also look at *real* A/B testing, #jamstack form handling, header control and other bits and bobs.
Join me for a lunchtime show and tell on day 2.
https://ti.to/smashingmagazine/ldn-lunch/with/nkam7kefmic
We'll also look at *real* A/B testing, #jamstack form handling, header control and other bits and bobs.