
@remotesynth @stackbithq Yeah! Making it increasingly easy to consume these services seems like a huge opportunity as the category continues to grow.

@remotesynth @stackbithq I also find the argument that depending on third party services is bad, weak.
Better to become experts in building, and maintaining auth, db, payments, hosting in house too?!
No thanks. I’ll work with experts via their APIs which are their core business.
Better to become experts in building, and maintaining auth, db, payments, hosting in house too?!
No thanks. I’ll work with experts via their APIs which are their core business.

@SteveALee @opensourceway Thanks Steve!

Phil Hawksworth
@philhawksworth •
"4 Reasons Jamstack is changing web development"
— a new post with thanks to @opensourceway
https://opensource.com/article/20/9/jamstack
— a new post with thanks to @opensourceway
https://opensource.com/article/20/9/jamstack

Phil Hawksworth
@philhawksworth •
Super work from @fostr_io on this project! And a great example of using @Shopify as part of a Jamstack site. https://twitter.com/Netlify/status/1300514468628066304

@jlengstorf @AdrianoBaussen I do. And I think it could use expanding.

@jlengstorf @AdrianoBaussen Ooh there’s a thought.

@ravivyas84 How very kind! Thank you. And congrats on the update. It looks 🔥🔥🔥

@gradualist @cassidoo Priorities!

@evanfuture @debs_obrien @dawntraoz @Netlify “Today’s talk will be ever so slightly shorter than advertised...”

@kvlly This is the advice I most often give myself but then fail to follow.
I think I need adult supervision.
I think I need adult supervision.

@umaar @tailwindcss @simonswiss It’s one of my absolute favourites. And will address a lot of the questions you are likely you have.

@umaar @gopibabus @tailwindcss Yeah. And apply is handy for assembling your commonly used, but verbose sets of classnames into reusable classes.
Then I again, I often find myself making commonly reused html fragments into components anyway. So the repetition of css classes is often avoided.
Then I again, I often find myself making commonly reused html fragments into components anyway. So the repetition of css classes is often avoided.

@umaar @tailwindcss I've tried to emulate lots of points from this talk, but still think the very best explanation comes from @simonswiss. This talk is wonderful and is what convinced me to explore and overcome my reservations.
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

@umaar @tailwindcss I found this to be a slight mental/instinctual hurdle.
But you still are keeping your html and css separate. It’s just that your css gets far more specific and reusable.
But you still are keeping your html and css separate. It’s just that your css gets far more specific and reusable.

@bridgetstewart @chriscoyier It’s just occured to me that I’ve never seen @chriscoyier and @IncredibleCulk in the same place at the same time.

@JJAggas @CodeFoodPixels @Netlify Interesting! I should mention that to the @Netlify swag pixies.
That design does feature on the jammies - which were in this box. And are the comfiest!!!
https://swag.netlify.com/product/netlify-summer-jammies
That design does feature on the jammies - which were in this box. And are the comfiest!!!
https://swag.netlify.com/product/netlify-summer-jammies

@peduarte @benoitgrelard Pedro.

@peduarte @benoitgrelard Pedro.

@peduarte Wow. Bravo!

Phil Hawksworth
@philhawksworth •
Treat yo’self! https://twitter.com/jlengstorf/status/1299055681215946752

@drewm So coooooool!