Original content FTW! ๐ Fed up with seeing people post that's just tweets or a link to something else ๐
Nice one Chris. I'm basing some of my course/content around this scenario of retrofitting Tailwind. Are you considering refactoring things into "Components"?
No problem at all. Yeah, I'm familiar, my site is built with Eleventy. Well, the term "components" doesn't have to be tied to a framework ๐
But, you could use a bundler and split any JavaScript code between modules. Then use partials to split your markup blocks into "Components". However, the part I was referring to was "Tailwind" components. If you use the plugins part of the config, you can create custom classes for commonly repeated things, etc. Didn't know if you were going to do anything like that.
Original content FTW! ๐ Fed up with seeing people post that's just tweets or a link to something else ๐
Nice one Chris. I'm basing some of my course/content around this scenario of retrofitting Tailwind. Are you considering refactoring things into "Components"?
Thanks, Jhey, means a lot coming from you.
Might try, but since this specific example is custom eleventy, not sure how I would fit it into "components"
Definitely keen to do some other articles on converting to Tailwind.
Would love to hear in which sense you are referring to Components?
Hey Chris.
No problem at all. Yeah, I'm familiar, my site is built with Eleventy. Well, the term "components" doesn't have to be tied to a framework ๐
But, you could use a bundler and split any JavaScript code between modules. Then use partials to split your markup blocks into "Components". However, the part I was referring to was "Tailwind" components. If you use the plugins part of the config, you can create custom classes for commonly repeated things, etc. Didn't know if you were going to do anything like that.
Oh right, might get into that, but not sure on the component topics yet.
We'll see what comes up in my work