@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
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.
@DavidDarnes Precisely. I should have mentioned that. Your analytics code would just need to distinguish between branches (since that's not in the URL) via a suitable tagging structure. Simple enough via branch builds and a static site generator.
@ChrisFerdinandi Yep! Since its job is to manage assets directly to your git repo, it doesn't depend on @Netlify. It needs the Github API. You could use it with some other CI which watches your repo for changes and triggers builds.
If you use Netlify Identity it needs to be on Netlify though.
If you use Netlify Identity it needs to be on Netlify though.
@AdrienRahier @Netlify A quick look at how that works @AdrienRahier
https://twitter.com/philhawksworth/status/968109066806616066
https://twitter.com/philhawksworth/status/968109066806616066
A few people have asked me about how split-testing works in @Neltify. Happily, it is very quick to create and deploy different variants of your sites for A/B or Multi Variant testing.
Here's a quick look.
https://www.youtube.com/watch?v=5VgpJJUOng4
Here's a quick look.
https://www.youtube.com/watch?v=5VgpJJUOng4
@bibliocloud @Netlify aha. Ok. Just as long as you are aware. @algolia search seems to work beautifully other than that. I wonder if a wildcard redirect in your _redirects file might help hide this until resolved. Perhaps
https://adoring-einstein-b558e7.netlify.com/* https://www.bibliocloud.com/:splat 301
https://adoring-einstein-b558e7.netlify.com/* https://www.bibliocloud.com/:splat 301