@jensfranke @stefanjudis @Netlify @SpeedCurve Filed under "examples I want to see and case studies I want to read"
(pretty bloody close to the top)
@reimertz @NorbertDragan @Netlify Yikes! That has been a long road! Glad that you found @netlify and a CMS solution that fits you, in the end. 😬
This is a great tutorial and uses one or two patterns that I find really useful on my own sites. https://twitter.com/tomsansome/status/995973585683537920
@dav_is_dev @ChrisFerdinandi @vincpa @ianfeather Only if you design and build them with robustness in mind. PWAs use a collection of technologies. It's up to you to use them responsibly. Many of them, like SW, were designed as progressive enhancements specifically to allow you to use them with this in mind.
@dav_is_dev @ChrisFerdinandi @vincpa @ianfeather I recommend watching the entire talk when the video is released.
So excited that @gossip_rabbit is officially part of @Netlify. Talented data scientist ahoy! https://twitter.com/gossip_rabbit/status/995789350800674816
@DavidDarnes @chrishawes @Netlify 100%
In a similar way, I might add email notifications to submitters when thir comment is published in this reference example:
https://css-tricks.com/jamstack-comments/
In a similar way, I might add email notifications to submitters when thir comment is published in this reference example:
https://css-tricks.com/jamstack-comments/
@DavidDarnes Totally! You have all the event hooks, build tiggers, and access to the form data via the submissions API you'd need on @Netlify.
And event-based lamda functions would be perfect to send the email (just name the lambda file "deploy-succeeded.js")
https://www.netlify.com/docs/functions/#event-triggered-functions
And event-based lamda functions would be perfect to send the email (just name the lambda file "deploy-succeeded.js")
https://www.netlify.com/docs/functions/#event-triggered-functions
@davatron5000 @OThatSean Alas, we have no affiliate scheme like that... but for every heartwarming message like that one from Sean, you'll earn an official Hawksworth nod of approvalâ„¢, a hearty handshake/hug depending on your personal space preferences, and all the @Netlify stickers you can eat!
@davatron5000 @github And yep again. The @github API doesn't allow for finer grained permissions. Some people are put off by that, but the authentication happens client-side and @Netlify don't store any creds ourselves after the required hooks are establish for the repo in question.
@davatron5000 @github Yep. Good shout. Sites with lots of assets/pages in particular benefit from plenty of traffic as it thoroughly primes the global CDN caches. If benchmarking it's worth doing some refreshes after each deploy to be sure that you're not going back to the origin for any requests.
@davatron5000 Great! I might even have hoped for a more dramatic improvement. Then again, I know nothing about the previous hosting or the profile of the site. A 33% perf bump with no re-engineering is not to be sniffed at. 🤓
Was the process of getting up and running as you had hoped?
Was the process of getting up and running as you had hoped?
@swyx @Chr_Bach The term #jamstack tries to describe something more than is often implied by they term "static site". Mostly due to the rich ecosystem of tools and services now available to make them so much richer and dynamic, and less "static".
Some thoughts: https://www.hawksworx.com/blog/webserverless
Some thoughts: https://www.hawksworx.com/blog/webserverless
@swyx @Chr_Bach I think maybe the practice is more popular than the term. The variety and popularity of different static site generators suggests that there is some enthusiasm out there.
https://www.staticgen.com/
https://www.staticgen.com/
STILL flabbergasted by the elegance of this beautiful creation from @mwichary. https://twitter.com/mwichary/status/994849248784023552