Another amazing line-up!
And not long to go now.
Getting really rather excited about @jamstackconf returning to San Francisco.
A single track event.
(With possibly my favourite corridor track of any event)
Tickets! Quick! 🎟 https://twitter.com/jamstackconf/status/1174053770117861376
RT @sanity_io: With our new source plugin for @gridsome, you can build fast by default websites in @vuejs, powered by structured content!…
RT @JAMstackTORONTO: Before I forget, anyone heading to @jamstackconf? The good ppl @ @loblawdigital were our hosts last night, but they're…
Are you:
- Working on web projects at an agency?
- Involved in project architectures?
- interested in #JAMstack?
I'd love to talk about how @Netlify might help.
Planning some agency discussions by invitation during @jamstackconf.
Find me in https://jamstack.org/slack for info.
- Working on web projects at an agency?
- Involved in project architectures?
- interested in #JAMstack?
I'd love to talk about how @Netlify might help.
Planning some agency discussions by invitation during @jamstackconf.
Find me in https://jamstack.org/slack for info.
I had a great time speaking at @frontendyork. Well organised and enthusiastically attended by a very welcoming group.
And York is utterly beautiful.
Heartily recommended. https://twitter.com/frontendyork/status/1171094663219933184
And York is utterly beautiful.
Heartily recommended. https://twitter.com/frontendyork/status/1171094663219933184
This is going to be 🔥🔥🔥 https://twitter.com/ireaderinokun/status/1173892795792338944
I struggle to open up our extendable dining table into its “we’ve got guests” position. Meanwhile, in Japan... https://twitter.com/MachinePix/status/1173716586202456064
@es_subodh @Netlify We don't currently support serving assets with Brotli compression. But there are a lot of requests for it and I'd imagine it will come in the future.
@stubbornella Is this the “My other car is a Porsche” bumper sticker for the class-less and financially perspective-free generation?
@swyx I think context is key here. E.g. Under some circumstances doing one big read up front can be desirable. Frequency of changes, ways the data is locally queried, ability to cache for subsequent builds with no need for fetch, reliability of access to remote data... all impact this.
Eagerly snooping around the pull request for this gorgeous and subtle addition to the @Netlify home page from @sarah_edo.
Every day is a school day 🤩 https://twitter.com/sarah_edo/status/1172548056333479936
Every day is a school day 🤩 https://twitter.com/sarah_edo/status/1172548056333479936
@swyx @ollie_monk And it's worth noting that in order to help multiply and amplify their wonderful work, the Support team contribute loads of good stuff in the discoverable & public forum of http://community.netlify.com
(ably assisted by loads of lovely community members)
A great first stop for help!
(ably assisted by loads of lovely community members)
A great first stop for help!
@Eastmad @remotesynth Even if the only markup coming down the wire is approx:
<div id="some-big-js-app"></div>
markup is still involved. But sure, developers might be using less markup or an abstraction with pre-processing. And authors may use abstractions. But still, the M in JAMstack is Markup.
<div id="some-big-js-app"></div>
markup is still involved. But sure, developers might be using less markup or an abstraction with pre-processing. And authors may use abstractions. But still, the M in JAMstack is Markup.