@igloo_si @Netlify We got you.
https://twitter.com/Chr_Bach/status/999049294857420802
Adding some extra meaning to your browser tabs.
(or, "Now you can see your deploy status while busily watching kitten videos in another tab") https://twitter.com/Netlify/status/999040677269917696
(or, "Now you can see your deploy status while busily watching kitten videos in another tab") https://twitter.com/Netlify/status/999040677269917696
@jameswillweb @zachleat Why isn't the possum wearing sunglasses/spectacles/monocle?
@jaffathecake Did you ghostwrite this tweet?
https://twitter.com/RebeccaRHelm/status/998981323716005888
https://twitter.com/RebeccaRHelm/status/998981323716005888
@darpots @Netlify @stolinski Ha ha! Yeah, I enthused so much about @netlify that a lot of people would tell me to "get a room".
So I joined the company. Now we work in the same room. I think that was what they meant.
So I joined the company. Now we work in the same room. I think that was what they meant.
Every time I make something with @eleven_ty it makes me smile. I think that might be to do with its focus on simplicity. @zachleat seems to strive for that often.
https://www.zachleat.com/web/that-could-possibly-work/
https://www.zachleat.com/web/that-could-possibly-work/
@jrTera3yte @Netlify Standard unhelpful answer: It depends! (On what your site/app does)
More useful guidance: The more you can deliver pre-rendered in your HTML, the more performant and robust your site will be. You can then enhance with calls to the same API client-side too. Best of both! :)
More useful guidance: The more you can deliver pre-rendered in your HTML, the more performant and robust your site will be. You can then enhance with calls to the same API client-side too. Best of both! :)
@alex_thomas @Netlify I'm afraid I don't use this. I recommend contacting support@netlify.com if you're having issues. That is the best way to track issues and reach the correct person.
@bhenbe @davatron5000 @Netlify @____lighthouse The defaults you get automatically from @Netlify's CDN are really rather good, but if you want full control over http caching headers, you can have that via the custom headers configuration.
https://www.netlify.com/docs/headers-and-basic-auth/
https://www.netlify.com/docs/headers-and-basic-auth/
@danrocc @username_ZAYDEK @vuejs @Netlify Excuse the drop-in, but I'm curious... this is a front end which calls an API hosted elsewhere on Flask?
If so, a UI built with @vuejs and @nuxt_js which talks to an API anywhere would work nicely on @Netlify.
CDN-level proxy to any API:
https://www.netlify.com/docs/redirects/#proxying
If so, a UI built with @vuejs and @nuxt_js which talks to an API anywhere would work nicely on @Netlify.
CDN-level proxy to any API:
https://www.netlify.com/docs/redirects/#proxying
Ooh, my @render_conf presentation is featured on the home page of @benotist! Yay!
I'm getting excited at how @benotist is shaping up, and would certainly recommend signing up for the beta. It nicely bridges Lanyrd & Speakerdeck.
https://noti.st/
I'm getting excited at how @benotist is shaping up, and would certainly recommend signing up for the beta. It nicely bridges Lanyrd & Speakerdeck.
https://noti.st/
Just a couple of days until @raymondcamden and I talk about Modern Web Development with the JAMStack in a free online webinar. Registration still open.
https://certifiedfreshevents.com/events/jamstack/
Expect some chatter about:
#auth0
#netlify
#static
#ssg
#headless
#serverless
#jamstack
https://certifiedfreshevents.com/events/jamstack/
Expect some chatter about:
#auth0
#netlify
#static
#ssg
#headless
#serverless
#jamstack