I've been a professional C, Perl, PHP and Python developer.
I'm an ex-sysadmin from the late 20th century.
These days I do more Javascript and CSS and whatnot, and promote UX and accessibility.
This is a good way to learn Tailwind, but not HTML - approaches like these throw away any semantic content in favour of div elements everywhere, and I think it's a much better idea for people starting out to learn how to construct a document first, rather than see it as some optional "nice to have" they might do later.
I realise it's not the point of the exercise, but if you style semantic elements then you don't need any of the Tailwind stuff anyway.
if you style semantic elements then you don't need any of the Tailwind stuff anyway
Using semantic elements is not related to using Tailwind - semantic elements should be used with Tailwind and can even make applying the Tailwind styles easier.
I've been a professional C, Perl, PHP and Python developer.
I'm an ex-sysadmin from the late 20th century.
These days I do more Javascript and CSS and whatnot, and promote UX and accessibility.
But they aren't, though, in the real world. People who use Tailwind almost exclusively use it with div soup since you're encouraged to make a lot of wrapper divs.
I'm not sure why you think that Tailwind encourages creating "a lot" of wrapper divs?
Since it's a utility framework anything it's doing is transferable to using style="" or a class on the same element where it's applied, so any "div soup" is still just an issue with the HTML directly, not Tailwind.
I've been a professional C, Perl, PHP and Python developer.
I'm an ex-sysadmin from the late 20th century.
These days I do more Javascript and CSS and whatnot, and promote UX and accessibility.
I've been a professional C, Perl, PHP and Python developer.
I'm an ex-sysadmin from the late 20th century.
These days I do more Javascript and CSS and whatnot, and promote UX and accessibility.
Anyone can write clean HTML. The people who are writing things like Tailwind (and a bunch of other things, like React components for example) are typically not doing that, though. Almost all the Tailwind tutorials you'll find use DIV soup, and people starting out with it just follow suit.
This is a good way to learn Tailwind, but not HTML - approaches like these throw away any semantic content in favour of
divelements everywhere, and I think it's a much better idea for people starting out to learn how to construct a document first, rather than see it as some optional "nice to have" they might do later.I realise it's not the point of the exercise, but if you style semantic elements then you don't need any of the Tailwind stuff anyway.
Using semantic elements is not related to using Tailwind - semantic elements should be used with Tailwind and can even make applying the Tailwind styles easier.
But they aren't, though, in the real world. People who use Tailwind almost exclusively use it with div soup since you're encouraged to make a lot of wrapper divs.
I'm not sure why you think that Tailwind encourages creating "a lot" of wrapper divs?
Since it's a utility framework anything it's doing is transferable to using
style=""or a class on the same element where it's applied, so any "div soup" is still just an issue with the HTML directly, not Tailwind.You're right in principle, but if you look at anything that's been styled with Tailwind you'll see what I mean.
You're still putting the blame on Tailwind when the issue is with HTML.
It's fine if you don't like Tailwind because of whatever reason. But that doesn't mean that anyone that uses it can't write clean HMTL.
Anyone can write clean HTML. The people who are writing things like Tailwind (and a bunch of other things, like React components for example) are typically not doing that, though. Almost all the Tailwind tutorials you'll find use DIV soup, and people starting out with it just follow suit.
Let's stop making assumptions about people that use specific tools - Thanks.
Thanks, Ben! I'll make sure to include more emphasis on semantic content in future tutorials. Appreciate your feedback!