Markdown?
Markup?
More?
@remotesynth clarifies the M in #JAMstack nicely.
https://dev.to/remotesynth/markdown-is-markup-and-other-confusions-around-jamstack-41pg
Markup?
More?
@remotesynth clarifies the M in #JAMstack nicely.
https://dev.to/remotesynth/markdown-is-markup-and-other-confusions-around-jamstack-41pg
@zachleat Wait. What? @sarah_edo has been charging me a fee to attend meetings. And making lots of meetings manadotry.
Is that not normal?
Is that not normal?
@DavidDarnes shhh.
Our coffee morning calls are our little secret.
(and of course you are, you glorious beast)
Our coffee morning calls are our little secret.
(and of course you are, you glorious beast)
@jeromecoupe @eleven_ty @Netlify (I confess that I forgot about doing that before. Sorry for the repetition)
..but hooray!
..but hooray!
Would pay cold hard cash to be in this meeting with these rather brilliant Netlifriends.
(I'd sit quietly and keep out of trouble) https://twitter.com/rafahari/status/1172178927483281408
(I'd sit quietly and keep out of trouble) https://twitter.com/rafahari/status/1172178927483281408
@scottjehl @sarah_edo @Netlify @filamentgroup Branch builds, preview builds, and instant rollbacks are a heady combination. Time-travel powers++
Another great article from @jeromecoupe! This time describing a very logical approach to multi-language sites with #JAMstack.
This method of generating the site with @eleven_ty is a perfect fit for @netlify's lang/geo detection and redirects.
https://www.netlify.com/docs/redirects/#geoip-and-language-based-redirects https://twitter.com/jeromecoupe/status/1172131960438886400
This method of generating the site with @eleven_ty is a perfect fit for @netlify's lang/geo detection and redirects.
https://www.netlify.com/docs/redirects/#geoip-and-language-based-redirects https://twitter.com/jeromecoupe/status/1172131960438886400
Goodness me yes!
Having gotten used to having this capability over the last few years, I simply can't imagine being without it.
👇👇👇👇👇 https://twitter.com/sarah_edo/status/1172149941516390401
Having gotten used to having this capability over the last few years, I simply can't imagine being without it.
👇👇👇👇👇 https://twitter.com/sarah_edo/status/1172149941516390401
RT @sarah_edo: I love that @Netlify makes deploying easy, but here are some things that take it to the next level for me:
* lock a particu…
* lock a particu…
@Netlify That pro-tip post and video:
https://dev.to/philhawksworth/netlify-pro-tip-using-split-testing-to-power-private-beta-releases-a7l
https://dev.to/philhawksworth/netlify-pro-tip-using-split-testing-to-power-private-beta-releases-a7l
@svillegastweets @tachyons_css @tailwindcss @simonswiss @DotAllConf @adamwathan I know just what you mean!
I found the argument about semantics in html vs css quite compelling. And the thoughts on sustaining maintainable CSS over time (even on my personal projects) struck a chord.
Trying to be willing to explore and learn. Despite my entrenched opinions.
I found the argument about semantics in html vs css quite compelling. And the thoughts on sustaining maintainable CSS over time (even on my personal projects) struck a chord.
Trying to be willing to explore and learn. Despite my entrenched opinions.
@simonswiss @tachyons_css @tailwindcss @DotAllConf It was SO well put together. Lots of inspiration for me about both the content and the delivery.
@simonswiss 🙂 I’m going to have to experiment. I’ve considered exploring these before but was a little cautious. Your arguments landed well for me.
Looking at utility-first CSS tooling such as @tachyons_css and @tailwindcss with fresh eyes and piqued interest after watching this brilliantly constructed talk by @simonswiss from last year's @DotAllConf.
https://dotall.com/sessions/a-real-life-journey-into-the-opinionated-world-of-utility-first-css
https://dotall.com/sessions/a-real-life-journey-into-the-opinionated-world-of-utility-first-css