@rafahari Woah!
@jupiterorbit @Netlify Coming up, we have the traffic news. Followed by the majesty which is, the Electric Light Orchestra.
@captainsafia @github @Netlify I love that too! It's the fact that you can do it with confidence that makes it feel magical.
I've deployed an update to my site during an event while sitting in the audience and my site was on screen. #NervesOfSteel
I've deployed an update to my site during an event while sitting in the audience and my site was on screen. #NervesOfSteel
@petervangrieken @Netlify Wonderful! Delighted to hear that.
@petervangrieken @Netlify ha ha. "A camera? Oh, I had no idea."
@petervangrieken @Netlify Pro-level Peter is at pro level.
Phil Hawksworth
@philhawksworth •
Another good 'un from @jaffathecake https://twitter.com/jaffathecake/status/968500192210227202
Phil Hawksworth
@philhawksworth •
Tickets for @hey_stac conference in Leeds won't be around forever. @joshnesbitt & @csswizardry have managed to snag these fine folks:
@rachelandrew
@una
@ianfeather
@stopsatgreen
@iamashley
@jaffathecake
I'd heartily recommend giving this a look!
https://twitter.com/hey_stac/status/966227750884388864
@rachelandrew
@una
@ianfeather
@stopsatgreen
@iamashley
@jaffathecake
I'd heartily recommend giving this a look!
https://twitter.com/hey_stac/status/966227750884388864
@dawgawel I wonder if this could be achieved through a careful branching model. You can configure tests to include any branches (and don't need to include master). Might there be a git workflow which could facilitate this?
@RyanTownsend @AndyDavies @indysigner @smashingconf All good points. Yeah this demo is very much focussed on how MVT can be run on @netlify.
I'll give some thought to a demo which includes the tagging.
I'll give some thought to a demo which includes the tagging.
@AndyDavies @indysigner @smashingconf ah. Sorry - Static Site Generator.
Think @jekyllrb or @GoHugoIO or some such.
Think @jekyllrb or @GoHugoIO or some such.
@kelseyhightower You may be interested in @Netlify Functions. Dependencies are compiled into your functions and deployed to AWS for you automatically.
The intent is to radically simplify the provision and workflow of FaaS.
Let me know if you'd like access to the beta.
https://functions-beta--www.netlify.com/docs/lambda-functions/
The intent is to radically simplify the provision and workflow of FaaS.
Let me know if you'd like access to the beta.
https://functions-beta--www.netlify.com/docs/lambda-functions/
@RyanTownsend @AndyDavies @indysigner @smashingconf I agree totally... except about the need to avoid a deployment. When friction is sufficiently low, a deployment should be mundane.
Would it be of interest if I were to muddle up a demo of something that tries to make the analytics tagging simple as part of the process?
Would it be of interest if I were to muddle up a demo of something that tries to make the analytics tagging simple as part of the process?
@AndyDavies @indysigner @smashingconf The cookie does nothing more than keep a user going back to the same branch for a given split test.
For measurements, you'd need to include suitably descriptive tagging in your analytics. A SSG could probably make light work of setting that up.
For measurements, you'd need to include suitably descriptive tagging in your analytics. A SSG could probably make light work of setting that up.
@tvanantwerp @NetlifyCMS You might be able to get some insight by chatting to the rather helpful community over at https://gitter.im/netlify/NetlifyCMS
@benpbarnett I maintain that I'm the only one who would ever get yours right.
Phil Hawksworth
@philhawksworth •
That feeling when you can't spell where you work. (@Netlify) https://twitter.com/philhawksworth/status/968109066806616066
@indysigner Yes! Traffic splitting right at the CDN.
I'd love to hear what @AndyDavies makes of this after his excellent session at @smashingconf where he talked about some of the performance hits of A/B testing which depend on client-side UI manipulation with JavaScript.
I'd love to hear what @AndyDavies makes of this after his excellent session at @smashingconf where he talked about some of the performance hits of A/B testing which depend on client-side UI manipulation with JavaScript.