A hearty recommendation for this!!!
There is so much to learn when you Learn With Jason! https://twitter.com/jlengstorf/status/1188937636594872321
@mrwiblog @TrentWalton Heh. I think I've seem more even that that. But yes, the same result.
"The website you make us MUST be fast"
(Hooray!!!)
"And before we launch you must add all these tracking codes and blocking 3rd party scripts"
(Oh!)
"The website you make us MUST be fast"
(Hooray!!!)
"And before we launch you must add all these tracking codes and blocking 3rd party scripts"
(Oh!)
This is a reason I got so excited when @Netlify launched split testing that uses fully featured branch builds so everything is “as production” and no client side scripts are required.
https://twitter.com/netlify/status/1171833284638257153?s=21
https://twitter.com/netlify/status/1171833284638257153?s=21
“You just have to pick one!”
— says @TrentWalton on clients adding *multiple* third party scripts for analytics and a/b testing.
This is the voice I’ve always wanted in the room when brand clients dismissed this as a concern from an agency “tech person”.
Data helps.
#aeadev
— says @TrentWalton on clients adding *multiple* third party scripts for analytics and a/b testing.
This is the voice I’ve always wanted in the room when brand clients dismissed this as a concern from an agency “tech person”.
Data helps.
#aeadev
@hardfire @TrentWalton Absolutely! I've seen this open the floodgates to all sorts of scary code being added to sites by those unfamiliar with the implications. Often by clients who also hold you responsible for delivering good perf while simultaneously scuppering you.
Being equally inspired & terrified by @TrentWalton's outstanding talk at #aeaden where he describes the impact and prevalence of 3rd party scripts in our sites.
There is such a huge impact on performance and effectiveness when we don't understand and control the JS on our sites.
There is such a huge impact on performance and effectiveness when we don't understand and control the JS on our sites.
@toddlibby @sarah_edo Great to meet you! Always delighted to see @netlofy stickers find their way to the laptops of enthusiastic Netlify users.
@nystudio107 @devmodefm @swyx @Netlify @zachleat @eleven_ty @ChrisFerdinandi @GoHugoIO That's funny. I often use that very example for the opposite point. I would still talk about my site being LAMP stack even when it didn't need a DB, and just used PHP and Apache on a Linux machine.
@nystudio107 @devmodefm @swyx @Netlify @zachleat @eleven_ty @ChrisFerdinandi @GoHugoIO That's interesting. And perhaps related to a common misunderstanding:
Yes #JAMstack stands for JavaScript APIs and Markup, but you absolutely *don't need to use all three*.
If your site is regenerated and can be served directly from a CDN, it's a JAMstack site.
Yes #JAMstack stands for JavaScript APIs and Markup, but you absolutely *don't need to use all three*.
If your site is regenerated and can be served directly from a CDN, it's a JAMstack site.
Nodding enthusiastically as @zeldman espouses the benefits of authoring your own personal site. Whether it is popular or not, the lessons we can learn in writing, designing, communicating are super valuable. #aeaden
Echoes of @lauragift21's recent post.
https://www.giftegwuenu.com/the-benefits-of-owning-a-personal-blog/
Echoes of @lauragift21's recent post.
https://www.giftegwuenu.com/the-benefits-of-owning-a-personal-blog/
RT @lauragift21: 🎉New post on my blog - The Benefits of Owning a Personal Blog http://zpr.io/tq9uW
Oooft! This is naaaasty! 🔥 https://twitter.com/TheHoopCentral/status/1188582251656646656
@kbariotis @Netlify It’s available for all, from the starter plan on up. (Although it is _headers rather than __headers)
As long as it is present in the root of your deploy directory, you should be good to go. You can also declare your custom headers in your netlify.toml if you prefer.
As long as it is present in the root of your deploy directory, you should be good to go. You can also declare your custom headers in your netlify.toml if you prefer.