@chris5marsh @csswizardry @Documentally Try to get a good night's sleep but also try to have at least one end-to-end run through while standing (not sitting in front of your laptop).
Don't be afraid to look out at the audience as you get comfortable, and most of all enjoy yourself.
It will be ace!
Don't be afraid to look out at the audience as you get comfortable, and most of all enjoy yourself.
It will be ace!
@slsoftworks @KTamas @FischaelaMeer @simona_cotin I'm sure that there will be no technical hiccups at all actually.
WAIT. I DID IT AGAIN.
WAIT. I DID IT AGAIN.
Easy. I'm just popping to the shed to make a dozen. https://twitter.com/awkwardgoogle/status/953329550003523586
Understanding the joke in this tweet is now table stakes. https://twitter.com/ianfeather/status/953923989570801665
@nsteinmetz @biilmann @Netlify @GoHugoIO @getgrav @scaleway That's curious. Irrespective of browser caching, was this the 1st time you'd hit the site after a deploy? The 1st request for a site after its deployment will have slightly slower response time as it will prime the CDN cache via a request to the origin. Then things get faster.
@whymclovin @Netlify Sure! Interested in hearing anything on the perf benefits of generating a view on demand rather than ahead of time. I guess targeted content rather than perf gain?
FWIW, when just a few pages need to by "dynamic", I invisibly proxy those to that service - https://medium.com/netlify/10-netlify-features-to-surprise-and-delight-225e846b7b21#7007
FWIW, when just a few pages need to by "dynamic", I invisibly proxy those to that service - https://medium.com/netlify/10-netlify-features-to-surprise-and-delight-225e846b7b21#7007
@whymclovin @Netlify If you mean rendering views on the server at request time, then no. We believe strongly in the power of the #JAMstack and removing that complexity.
Powerful automation and reduced friction for timely *pre-rendering at build time* (not req) time is where our power comes from.
Powerful automation and reduced friction for timely *pre-rendering at build time* (not req) time is where our power comes from.
@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!