@andybudd @csswizardry @hey_stac In about a week's time I'll have participated in, or hosted virtual conferences with 4 different combinations of tools. I've been refining my own setup along the way.
I feel a blog post swelling!
@_phzn has an excellent post on the A/V at Women of React
https://dev.to/_phzn/running-av-at-the-women-of-react-conference-1jnh
@misterhtmlcss @Netlify @sarah_edo @shortdiv @cassidoo @Tzmanics @jlengstorf Yeah it's hard to include lots of detail on each of these in a single blog post. But you're right, we should add links to more info on the next steps.
For example. you might be interested to see this big list of examples and tutorials. 👉 https://functions.netlify.com/?utm_source=twitter&utm_medium=support-pnh&utm_campaign=devex
For example. you might be interested to see this big list of examples and tutorials. 👉 https://functions.netlify.com/?utm_source=twitter&utm_medium=support-pnh&utm_campaign=devex
RT @smashingmag: 🎉🥳 Showtime! Join our free online meet-up with @YiyingLu @philhawksworth @markboulton @rachelandrew @Mandy_Kerr and the en…
@brendandawes I wish Past Phil was smart enough to put a chocolate eclair in the fridge. That would have been the classy thing to do.
But he didn’t.
All he did was finish all the milk.
Past Phil is a dick.
But he didn’t.
All he did was finish all the milk.
Past Phil is a dick.
RT @eleven_ty: @TheGreenGreek @philhawksworth @aaronpeters @SpeakToChris @davidrhoden Incredible—thank you for writing this!
I'm with @nhoizey.
Jamstack offers an opportunity for web developers to build great experiences for users. But as with all tools, we can mess that up if we're not thoughtful.
Doing as much as possible on the server ahead of time is my mantra. https://twitter.com/nhoizey/status/1257731500465848320
Jamstack offers an opportunity for web developers to build great experiences for users. But as with all tools, we can mess that up if we're not thoughtful.
Doing as much as possible on the server ahead of time is my mantra. https://twitter.com/nhoizey/status/1257731500465848320
@ysfaran15 @NetlifyCmnty Hey Yusuf!
I think in this scenario, you'd still host the npm package itself on GitHub and the package downloads would happen from there. But you can host the documentation page for the package elsewhere (like on Netlify). Usually the free tier is fine for that.
I think in this scenario, you'd still host the npm package itself on GitHub and the package downloads would happen from there. But you can host the documentation page for the package elsewhere (like on Netlify). Usually the free tier is fine for that.
@TheGreenGreek @eleven_ty Looking forward to reading this!
(So if doing so as a proof-reader helps at all, I’d be delighted)
(So if doing so as a proof-reader helps at all, I’d be delighted)
@mrwiblog Possibly also of interest - how the community chose to start using Jamstack instead of JAMstack partly to dial down the focus on those specific technologies in that order.
https://github.com/jamstack/jamstack.org/issues/279
https://github.com/jamstack/jamstack.org/issues/279
@mrwiblog Yeah lots of names have been used over the years. Jamstack is the one that stuck.
As you say, neither Javascriot nor APIs are essential for something to be Jamstack. I’d think of the name as meaningful for the model it represents rather than an acronym.
https://css-tricks.com/jamstack-vs-jamstack/
As you say, neither Javascriot nor APIs are essential for something to be Jamstack. I’d think of the name as meaningful for the model it represents rather than an acronym.
https://css-tricks.com/jamstack-vs-jamstack/
@jackdomleo7 @joshnesbitt @csswizardry @KlaraMiffili @charlotte_dann @elibelly @overflowhidden Great write up, @jackdomleo7! And thanks for the namecheck! I wish I could take more credit, but this event really is a labour of love from Josh and Harry.
I'm just the glamour.
I'm just the glamour.
@slightlylate @joshcarpenter @eleven_ty @Netlify @letsencrypt Not sure if this is helpful, but I had some fun with using Netlify Large Media for the sake of responsive images with @eleven_ty.
I probably shouldn't have used the picture element, but the principle is here.
https://example-nlm-picture.netlify.app/
I probably shouldn't have used the picture element, but the principle is here.
https://example-nlm-picture.netlify.app/
I love everything about these technical choices and this thoughtful write-up by @trysmudford about @clearleft's upcoming SofaConf.
https://www.trysmudford.com/blog/sofaconf-2020/
https://www.trysmudford.com/blog/sofaconf-2020/
@csswizardry page.tags should already be an array, no?
You shouldn’t need to manually split it or treat it as a string.
So you should be able to:
{% for tag in page.tags %}
{{tag}}
{% endfor %}
You shouldn’t need to manually split it or treat it as a string.
So you should be able to:
{% for tag in page.tags %}
{{tag}}
{% endfor %}