There is such unexpected power in this seemingly simple feature.
⬥ redirect
⬥ rewrite
⬥ proxy
⬥ authorise
⬥ localise
All from a config file which lives as part of your versioned code.
See how simple this can be with a look at the docs 👉 https://docs.netlify.com/routing/redirects/?utm_source=twitter&utm_medium=redirects-pnh&utm_campaign=devex https://twitter.com/Netlify/status/1227867510915174400
Ha ha ha. We all need these neighbours! https://twitter.com/JoshFeldberg/status/1220713524554620934
Here's a digest of the fourth week of articles @shortdiv wrote about JAMstack during each and every day of January.
Good stuff in here!
🤔 Speed?
🤔 Security?
🤔 Servers tho?
🤔 Authoring experience?
...and more.
https://dev.to/netlify/the-final-full-week-of-jamuary-for-2020-1bc9
Good stuff in here!
🤔 Speed?
🤔 Security?
🤔 Servers tho?
🤔 Authoring experience?
...and more.
https://dev.to/netlify/the-final-full-week-of-jamuary-for-2020-1bc9
Any opportunity to listen to @Tzmanics say words out loud should be grabbed with both hands. https://twitter.com/ngconf/status/1227643833124442112
@bradcypert @jlengstorf @Netlify @gatsbyjs Recommended!
I really enjoyed listening to this conversation.
I really enjoyed listening to this conversation.
It's more than 2 years since I posted this list of @Netlify features which excited me.
Now I take many of them for granted (and more have since been added). But I find it hard to imagine building for the web without things which I now feel fundamental.
https://medium.com/netlify/10-netlify-features-to-surprise-and-delight-225e846b7b21
Now I take many of them for granted (and more have since been added). But I find it hard to imagine building for the web without things which I now feel fundamental.
https://medium.com/netlify/10-netlify-features-to-surprise-and-delight-225e846b7b21
RT @jlengstorf: hi everyone! I need you to do me two favors, please:
1. send your favorite “get well soon” GIFs to @AishaBlake 💜
2. come…
1. send your favorite “get well soon” GIFs to @AishaBlake 💜
2. come…
RT @Netlify: In just a few hours we're hosting a webinar with Victoria Beckham Beauty! We'll be chatting with @contentful and hearing about…
@stubbornella @modernserf @LorienMCS @Netlify @loblawdigital @citrix @mattersupply This is also a good reference for JAMstack sites at enterprises and at large scale.
Rebooting MS Docs. Millions of pages and monthly views
The whole talk by @danielfe is great and well worth a watch. The JAMstack specific mentions start ~ 18mins in.
https://twitter.com/danielfe/status/1225261643254288384?s=20
Rebooting MS Docs. Millions of pages and monthly views
The whole talk by @danielfe is great and well worth a watch. The JAMstack specific mentions start ~ 18mins in.
https://twitter.com/danielfe/status/1225261643254288384?s=20
@rposbo @stubbornella @LorienMCS Logically they do seem similar. But in practice and when deploying code and content changes they have quite different implications. If pre-rendering, deployment can be sending everything to the CDN. That’s not the case with SSR if code/data/content might all change independently.
@stubbornella @LorienMCS My experience has been: this is can be tough to get right.
Server side rendering at request time tends to involve querying dynamic sources (or else why do it on demand per request?)
So you need to define the logic of what is dynamic and what is cacheable throughout the stack.
Server side rendering at request time tends to involve querying dynamic sources (or else why do it on demand per request?)
So you need to define the logic of what is dynamic and what is cacheable throughout the stack.
@stubbornella @torgo @phae Yeah.
My perspective here is that I spent years enthusing about static sites, claiming they had many advantages in certain situations.
Even though the tools & services had evolved, few clients were convinced until I began avoiding the loaded term "static". The word mattered.
My perspective here is that I spent years enthusing about static sites, claiming they had many advantages in certain situations.
Even though the tools & services had evolved, few clients were convinced until I began avoiding the loaded term "static". The word mattered.
@stubbornella @torgo @phae Ha ha. Nice.
I guess it might be seen as a dirty word if placed in exclusive opposition to "substance".
(As with the 99.9% vs 0.1% assertion)
There is more substance to the things described by the word, than to the word itself. But isn't that how such words work?
I dunno!
I guess it might be seen as a dirty word if placed in exclusive opposition to "substance".
(As with the 99.9% vs 0.1% assertion)
There is more substance to the things described by the word, than to the word itself. But isn't that how such words work?
I dunno!
@torgo @stubbornella @phae I'm very much with you to be honest.
I think of both PWA and JAMstack in similar ways - a collection of tools, services, and technologies which are hard to articulate without a convenient catch-all term.
I'd argue they have substance but needed some vocab.
I think of both PWA and JAMstack in similar ways - a collection of tools, services, and technologies which are hard to articulate without a convenient catch-all term.
I'd argue they have substance but needed some vocab.
@torgo @stubbornella It was hard to "sell" the pattern to stakeholders
"It’s marketing, just like HTML5 had very little to do with actual HTML. PWAs are just a bunch of technologies with a zingy-new brandname that keeps the open web going a bit longer"
— @phae on coining PWA
https://fberriman.com/2017/06/26/naming-progressive-web-apps/
"It’s marketing, just like HTML5 had very little to do with actual HTML. PWAs are just a bunch of technologies with a zingy-new brandname that keeps the open web going a bit longer"
— @phae on coining PWA
https://fberriman.com/2017/06/26/naming-progressive-web-apps/
@stubbornella Oh I agree that the phrase PWA is marketing.
But would you say that PWAs are 99.9% marketing and 0.1% substance? Or would you say that there are great technologies there which we struggled to communicate with stakeholders until it they got a convenient name?
But would you say that PWAs are 99.9% marketing and 0.1% substance? Or would you say that there are great technologies there which we struggled to communicate with stakeholders until it they got a convenient name?
@stubbornella @modernserf @LorienMCS My case studies are @Netlify-centric, but still about JAMstack.
Like this from @loblawdigital:
https://www.netlify.com/customers/loblaw/?utm_source=twitter&utm_medium=casetstudy-pnh&utm_campaign=devex
this from @citrix:
https://www.netlify.com/blog/2019/06/12/jamstack_conf-nyc-session-recap-citrix-delivers-better-ux-with-less-overhead-using-jamstack-and-netlify?utm_source=twitter&utm_medium=casetstudy-pnh&utm_campaign=devex
and this from @mattersupply for Nike
https://www.netlify.com/customers/matter-supply-nike-site/?utm_source=twitter&utm_medium=casetstudy-pnh&utm_campaign=devex
Like this from @loblawdigital:
https://www.netlify.com/customers/loblaw/?utm_source=twitter&utm_medium=casetstudy-pnh&utm_campaign=devex
this from @citrix:
https://www.netlify.com/blog/2019/06/12/jamstack_conf-nyc-session-recap-citrix-delivers-better-ux-with-less-overhead-using-jamstack-and-netlify?utm_source=twitter&utm_medium=casetstudy-pnh&utm_campaign=devex
and this from @mattersupply for Nike
https://www.netlify.com/customers/matter-supply-nike-site/?utm_source=twitter&utm_medium=casetstudy-pnh&utm_campaign=devex
@modernserf @stubbornella @LorienMCS Yes. Cost and confidence differences for sure. We've seen huge savings (in terms of infrastructure, licensing, time to market, and developer and author productivity) at large companies with substantial projects too.
@stubbornella @LorienMCS Although a staggering percentage of the sites on the web *are* content sites. I find it hard to justify a roundtrip to a DB to get the content for a blog post, for example.
And caching is so hard to do with dynamic infra that it is the source of CS jokes
https://martinfowler.com/bliki/TwoHardThings.html
And caching is so hard to do with dynamic infra that it is the source of CS jokes
https://martinfowler.com/bliki/TwoHardThings.html
@stubbornella I'd offer that it is useful vocabulary rather than all marketing. Since "static" doesn't go nearly far enough to describe all the technologies and services which have arrived and make this model so attractive and viable. (which is the "substance")
Kind of like with term "PWA"
Kind of like with term "PWA"