@trysmudford @Netlify You can get fine-grained control over that (smarter people than I can help describe details) but you can also get it automatically via the post-processing optimisations. Along with various assets optimisations, that will fingerprint everything and manage far future cache for you.
@rem @Netlify That's one of the killer features for me. I included it in my top 10. Also worth knowing that these all happen on the CDN edge nodes so are lightening fast, and you can also use them for shadowing and proxying. (I invisibly proxy some paths to Lambdas)
https://medium.com/netlify/10-netlify-features-to-surprise-and-delight-225e846b7b21#7007
https://medium.com/netlify/10-netlify-features-to-surprise-and-delight-225e846b7b21#7007
@DavidWells @sbarski @StegerPatrick @Netlify I'd be interested in this blog post too.
As an aside, Netlify's hosting infrastructure is cloud provider agnostic and has in-built redundancy across the large providers. So we should be able to weather disruptions to any of the underlying systems.
As an aside, Netlify's hosting infrastructure is cloud provider agnostic and has in-built redundancy across the large providers. So we should be able to weather disruptions to any of the underlying systems.
@stefanjudis oooooh. That's quite a head-scratcher!
Thanks for chasing that one down letting us know Stefan!
/cc @Netlify
Thanks for chasing that one down letting us know Stefan!
/cc @Netlify
@neutyp @stefanjudis @Netlify That's why I'm baffled. All my images go through ImageOptim before they go into my build, and I also have Netlify's post-processing attempt to squeeze them further.
I'll look at Squash to see if it can perform better.
I'll look at Squash to see if it can perform better.
When @gatsbyjs and @Netlify and @NetlifyCMS come together... exciting possibilities!
#jamstack #headlessCMS https://twitter.com/erquhart/status/953298572107309056
#jamstack #headlessCMS https://twitter.com/erquhart/status/953298572107309056
@stefanjudis @Netlify You prompted me to double check my own site... and now I have a nagging image performance itch that I'll need to scratch!
@stefanjudis @Netlify You bet!
Meanwhile I'm totally baffled about how I can't compress 2 of my images any further and yet WebPageTest is confident I could.
https://www.webpagetest.org/performance_optimization.php?test=180116_N2_5d85a3fed8f593c06d08b088483b6886&run=2#compress_images
#ChasingGreen
Meanwhile I'm totally baffled about how I can't compress 2 of my images any further and yet WebPageTest is confident I could.
https://www.webpagetest.org/performance_optimization.php?test=180116_N2_5d85a3fed8f593c06d08b088483b6886&run=2#compress_images
#ChasingGreen
@stefanjudis @Netlify Hmmmm. That's odd. I get gzip all happening for me without any manual config. I do have the post-processing option enable, but I believe things should be gzipped either way.
Could you ping support through https://app.netlify.com so that we can investigate and track it properly?
Could you ping support through https://app.netlify.com so that we can investigate and track it properly?
RT @amacarthur: Just finished up a @Firebase function that processes @stripe payments made through http://typeitjs.com. It's now an a-m…
@amacarthur @gatsbyjs @NetlifyCMS @MikeRiethmuller Great, Well if it helps, there is a bustling and helpful @NetlifyCMS community over here: https://gitter.im/netlify/NetlifyCMS
My buddy @peduarte has inspired me with his delicious side-project, and is now looking for opinions on some new branding. Which option is best? GO! https://twitter.com/peduarte/status/952944264224411648
@amacarthur @gatsbyjs @NetlifyCMS You might @MikeRiethmuller's thought on this interesting:
https://twitter.com/MikeRiethmuller/status/952759502201176064
https://twitter.com/MikeRiethmuller/status/952759502201176064
@Jack_Franklin @peduarte @Netlify Thanks for flagging that, @Jack_Franklin. Not sure what triggered it, and agree that it could be pitched a bit better. Will make sure we look at it.
Feedback like this is always helpful. Ta!
Feedback like this is always helpful. Ta!
@Jack_Franklin Whatever you decide, I'd recommend against serving your site from the apex domain. I reinstated my www subdomain after learning a little more about DNS.
@biilmann wrote a good explanation about that here:
https://www.netlify.com/blog/2017/02/28/to-www-or-not-www/
@biilmann wrote a good explanation about that here:
https://www.netlify.com/blog/2017/02/28/to-www-or-not-www/
@LeaVerou @Netlify Yay! Pleased you're getting on well with it.
Yep. Both of those are available to use in your. FWIW I do some image generation and manipulation as part of my build to automatically generate open-graph assets for each of my pages.
https://github.com/philhawksworth/hawksworx.com/blob/63a18cc6d4c3b4d0d13b4539529de7d46dfcf8dc/gulpfile.js#L110
Yep. Both of those are available to use in your. FWIW I do some image generation and manipulation as part of my build to automatically generate open-graph assets for each of my pages.
https://github.com/philhawksworth/hawksworx.com/blob/63a18cc6d4c3b4d0d13b4539529de7d46dfcf8dc/gulpfile.js#L110