|
|
|
|
|
|
by imbnwa
1082 days ago
|
|
|
>That power is only for the contrived example of doing a complete redesign that doesn’t change any of the html content. Didn't Github just re-style their whole UI? Presuming that's an extreme possibility seems like premature optimization unless you run Product. |
|
|
The other comment made a good point about WP templates, I can only speak to my own experience. I have mostly worked on projects where I could edit the HTML, and in those cases using a Tailwind-like methodology was dramatically easier. Even when doing a full-site redesign.
So if you are designing for a project where you are unable to edit HTML, sure, use the right tools for the right. Or if the bulk of your coding time is spent doing full site redesigns instead of updates to an existing design, then it wouldn’t be the right approach. I wouldn’t use it on a project intended to be white-labelled, otherwise that’s the methodology I’d use.