@djm_ Ha ha.
The other thing later turned out to be Pinterest at least 5 years before Pinterest was Pinterest.
#WhereIsMyYacht?
I've always found the split testing UI in @Netlify gratifying. But I'd never noticed the little bouncing padlock on locked branches letting me know that I can't adjust some weightings because maths.
Boing!
❤️ Love it.
Related: https://dev.to/philhawksworth/power-up-gatsby-sites-with-a-b-testing-on-netlify-fp4
Boing!
❤️ Love it.
Related: https://dev.to/philhawksworth/power-up-gatsby-sites-with-a-b-testing-on-netlify-fp4
@Benghamine Also the thinking that it's ok to dismiss the passion project being enthusiastically described and demonstrated by a junior (or any, really) developer as being without merit because "there are things like this"... is missing the point by some margin.
One of my lingering regrets from early in my career was letting the feedback of “so, you’re just building another X?!” completely torpedo a side project of mine.
I was learning, energised, and convinced I was making something useful. This feedback from a mentor knocked me back. https://twitter.com/TaelurAlexis/status/1163676341557846016
I was learning, energised, and convinced I was making something useful. This feedback from a mentor knocked me back. https://twitter.com/TaelurAlexis/status/1163676341557846016
@smakosh @ThePracticalDev @gatsbyjs @Netlify If you’re curious and willing to explore further, I’d love to move this over to http://community.netlify.com where other people could help to figure it out, and we might be able to share the learnings with others who might have tripped up on something similar.
@smakosh @ThePracticalDev @gatsbyjs @Netlify I think I see. So some pages existed on one branch but not others? I’m also curious how users were being redirected differently. Netlify redirect rules would be specific to the branches too, unless there was something involved?
(I might not quite get the logic that was in place)
(I might not quite get the logic that was in place)
@smakosh @ThePracticalDev @gatsbyjs @Netlify Oh really? Did you ever get to the bottom of that? Netlify creates branch affinity so that each user should always be served by the same branch they were allocated. Did accessing the build on each branch url directly all work ok?
@Frankspin @sarah_edo @gatsbyjs @Netlify Great question, Frank!
I think this is where so much of the art comes in to this kind of thing.
A lot depends, I think, on the type of site and publishing cadence you have. But it really helps if all content and code updates are based on a git publishing model.
Good blog idea.
I think this is where so much of the art comes in to this kind of thing.
A lot depends, I think, on the type of site and publishing cadence you have. But it really helps if all content and code updates are based on a git publishing model.
Good blog idea.
@zachleat @TatianaTMac @nejsconf @andybelldesign @DavidDarnes @Robb0wen It mostly happens when I'm in trouble. 😞
@TatianaTMac @zachleat @nejsconf @andybelldesign @DavidDarnes @Robb0wen Curses for being called Philip with its 2 disqualifying extra letters.
@notrab @Netlify Aha. Gotcha. Not just creating the UI to populate, but pre-populating it too.
Seems handy to me, but I'm not sure I've seen it happening.
Can I suggest asking this question over in http://community.netlify.com? Smart people from support and the community are likely to chime in there
Seems handy to me, but I'm not sure I've seen it happening.
Can I suggest asking this question over in http://community.netlify.com? Smart people from support and the community are likely to chime in there
@notrab @Netlify I think you'll be able to do what you want by adding some info to the netlify.toml file of the repo you are cloning. That can let you prompt of contextual variables in the UI
https://www.netlify.com/docs/deploy-button/#template-configuration
https://www.netlify.com/docs/deploy-button/#template-configuration
🧪 Don't run A/B tests in a way that harms your site's performance!
Create and measure real A/B tests for your @gatsbyjs sites with @Netlify.
No fuss.
No mess.
No performance degradation.
Here's a video and an explanation.
https://dev.to/philhawksworth/power-up-gatsby-sites-with-a-b-testing-on-netlify-fp4
Create and measure real A/B tests for your @gatsbyjs sites with @Netlify.
No fuss.
No mess.
No performance degradation.
Here's a video and an explanation.
https://dev.to/philhawksworth/power-up-gatsby-sites-with-a-b-testing-on-netlify-fp4
@swyx @sxywu @mysterhee What!!??! Fantasticl! So many congratulations.
(And this photo is off the charts wonderful!)
(And this photo is off the charts wonderful!)