Moving away from Tailwind, and learning to structure my CSS (jvns.ca)

Article summary

The author reflects on their experience of moving away from using Tailwind, a utility-first CSS framework, and learning to structure their CSS. They discuss how Tailwind taught them a lot about CSS, but ultimately limited their ability to do certain things. The author shares their approach to organizing CSS, including using semantic HTML, components, and utility classes. They also mention their curiosity about new CSS features and their desire to improve their CSS skills.

Main themes

• CSS structuring
• Tailwind limitations
• Semantic HTML
• Accessibility
• LLMs and coding
• Web development frameworks

What commenters say

• Using LLMs to generate code can be beneficial, but may lead to unmaintainable codebases if not done carefully.
• Tailwind can be a useful tool, but its limitations can make it difficult to achieve certain design goals.
• Accessibility is an important consideration in web development, and should be prioritized from the start, not treated as an afterthought.
• The use of utility-first CSS frameworks like Tailwind can lead to a lack of semantic meaning in HTML, making it harder for screen readers and other accessibility tools to interpret.
• Some developers believe that using LLMs to generate code can replace the need for manual coding and frameworks like React, while others argue that these tools are still necessary for complex projects.
• There is a trade-off between the benefits of using frameworks like Tailwind and the potential drawbacks, such as limited control and accessibility issues.
• Accessibility is not just about accommodating blind users, but also about making websites usable for people with a wide range of disabilities and needs.
• Prioritizing accessibility can have a high return on investment, but some developers may prioritize other goals, such as rapid development or ease of use, over accessibility concerns.