Your mission, should you choose to accept it...
(with lots more missions to come) https://twitter.com/Netlify/status/1329114182369890307
(with lots more missions to come) https://twitter.com/Netlify/status/1329114182369890307
@SaraSoueidan For me, this hinges on the language which might feel most intuitive to the user when making the decision.
"Do you want this or that?" lends itself to a radio button.
"Do you want this or not?" lends itself to a checkbox.
"Do you want this or that?" lends itself to a radio button.
"Do you want this or not?" lends itself to a checkbox.
@SaraSoueidan All’s well that ends well!
I’m was just happy to breath a big sigh of relief and then be reminded check my own situation!
I’m was just happy to breath a big sigh of relief and then be reminded check my own situation!
@DaraghOShea @cloudinary Yes indeed. Using placeholders rather than a wildcard delivers that.
I'm now passing through a height in the path:
https://petsof.netlify.com/cloudinaried/500/polly.jpg
(from = "/cloudinaried/:height/:image")
Docs:
https://url.netlify.com/rk2y1QZ9w
Code: https://github.com/netlify/petsofnetlify/blob/master/netlify.toml#L8-L14
I'm now passing through a height in the path:
https://petsof.netlify.com/cloudinaried/500/polly.jpg
(from = "/cloudinaried/:height/:image")
Docs:
https://url.netlify.com/rk2y1QZ9w
Code: https://github.com/netlify/petsofnetlify/blob/master/netlify.toml#L8-L14
@mesetatron @kvncnls @Netlify That was an admission of my naiveté about the attention Jamstack had been starting to pick up.
Oopsie!
Oopsie!
@kvncnls @Netlify ha!
Not the creator. But I somewhat put the cat amongst the pigeons with this discussion:
https://github.com/jamstack/jamstack.org/issues/279
Not the creator. But I somewhat put the cat amongst the pigeons with this discussion:
https://github.com/jamstack/jamstack.org/issues/279
@Accudio @cloudinary @Netlify You're right that it's not a zero impact change to serving the same assets from your own site. But once Cloudinary ingests & caches these assets on the first request, no user would ever spot a perf impact.
They also do smart things for you, like serving the best format per client
They also do smart things for you, like serving the best format per client
@Accudio @cloudinary @Netlify Redirects happen at the edge of the Netlify CDN in some highly optimized C so that bit is crazy fast. Your browser doesn't need to look up another domain, so no additional overhead there. And @cloudinary is its own image CDN optimized for caching and serving these assets.
@davatron5000 @DavidDarnes @chriscoyier @cloudinary @Netlify @eleven_ty Aha! Well in that case, yeah that looks like an option!
@davatron5000 @DavidDarnes @chriscoyier @cloudinary @Netlify @eleven_ty I’ll dig out an example if generating _redirects file with @eleven_ty.
@davatron5000 @DavidDarnes @chriscoyier @cloudinary @Netlify @eleven_ty The images always reside in the images folder, even when served from Cloudinary. (Because Cloudinary accesses them to ingest them as the source image). There is never a “cloudinaried” folder for images. That’s just a path which resolves to the url on cloudinary.