@filipjaskolski @dawgawel @GoHugoIO @Netlify Great!
Excited to see that.
@mazzerpants Ha ha. Scatter a collection of kittens around so that I can lounge about surrounded by fluff and whiskers, and we'll talk.
(adding that to the list of things I wish I'd never said out loud)
(adding that to the list of things I wish I'd never said out loud)
To all the talented designers I know in the San Francisco area, and to those who would like to be... @Netlify are looking for someone to join us and help build our brand. Is it you?
https://hire.withgoogle.com/public/jobs/netlifycom/view/P_AAAAAACAAADCZPvgvybW--
https://hire.withgoogle.com/public/jobs/netlifycom/view/P_AAAAAACAAADCZPvgvybW--
Oooh. These are lovely!
@GoHugoIO, @Netlify and git are are wonderful combo for maintaining and publishing documentation. This is a lovely example! https://twitter.com/LiveChat/status/953616436848680960
@GoHugoIO, @Netlify and git are are wonderful combo for maintaining and publishing documentation. This is a lovely example! https://twitter.com/LiveChat/status/953616436848680960
@trysmudford @Netlify Ah. Good point. I'm doubt you'll get names of those assets into your build as the post-processing happens after the build(!) To play well with SWs, you'll likely be better off generating hashed names for assets in your build and setting cache headers via _headers or netlify.toml
@LaurenceHebberd @comedyincrown @leewilsoncomedy @martiniswillis @kuanwen_huang @katiepritchards @CrownStA @HATW_uk Always a pleasure. Don't be a stranger!
@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!