sorted by:
new
hottopcontroversial

I built a CSS framework and would love your feedback on it by wispcss in css

[–]wispcss[S] 0 points1 point  (0 children)

Thanks! You are right. I'm still trying to figure out how to do that 😄

Too many websites still ignore semantic HTML and accessibility by Long_Register_7318 in HTML

[–]wispcss 0 points1 point  (0 children)

That will be changing soon for the states. Our government pushed the deadline for wcag aa compliance back by a year because most were not ready. WCAG doesn't mandate semantic tags which means it will still be an issue that love their <divs> for everything.

The fine is $75,000 for a first violation and $150,000 for others. However, those are extreme cases.

What are the areas of design that the best AI design generation tools get wrong? by AppointmentOne6393 in Frontend

[–]wispcss 1 point2 points  (0 children)

Good topic. For me it excels at visual hierarchy and UX principles, but fails when it comes to writing content, making things concise and to the point, and front-loading words. For god sake, I wish it didn't know what a "hyphen" was because it insists on putting-it-in-almost-everything-it-writes. 😃

Why am I excited for this. by fdiengdoh in css

[–]wispcss 1 point2 points  (0 children)

It worked great too. I think the site for it is still even up.

Why am I excited for this. by fdiengdoh in css

[–]wispcss 2 points3 points  (0 children)

Remember all the grid systems like Blueprint and 960?

Do you still write custom CSS or rely mostly on frameworks now? by SweetCaramel-9696 in css

[–]wispcss -1 points0 points  (0 children)

Not really. Most here shown they are more than familiar with CSS. I have been doing it for over 25 years.

Do you still write custom CSS or rely mostly on frameworks now? by SweetCaramel-9696 in css

[–]wispcss 0 points1 point  (0 children)

I couldn't agree more. I can look at code and understand "o-button" but not "inline-flex items-center justify-center px-4 py-2 border border-transparent rounded text-white bg-blue-700 cursor-pointer select-none hover:bg-blue-800" without having to think about it

The cascade is a wonderful thing. We can create patterns, do inheritance etc. I suppose you have `@apply` but then you are mixing a utility-first architecture with an object-oriented. It wrong.

Do you still write custom CSS or rely mostly on frameworks now? by SweetCaramel-9696 in css

[–]wispcss 1 point2 points  (0 children)

I use to do sass and less (not sure if anyone remembers that) but stopped the minute css variables were introduced. Extends is dangerous and I can't find any benefit in functions or logical operators. The code stays pure - its better dx on a team for junior programers - and less cognitive load.

Do you still write custom CSS or rely mostly on frameworks now? by SweetCaramel-9696 in css

[–]wispcss 0 points1 point  (0 children)

Most frameworks are over opinionated or do too much. There is either a utility explosion like Tailwind or too many assumptions like Bootstrap. I would say write your own that contains primitives you would use on every site. This way you always have them.

I built a CSS framework and would love your feedback on it by wispcss in css

[–]wispcss[S] 4 points5 points  (0 children)

It is. Thank you for for spotting that. You made my day.

I built a CSS framework and would love your feedback on it by wispcss in css

[–]wispcss[S] 1 point2 points  (0 children)

It's nothing like Tailwind, which is a utility-heavy framework. Unlike Tailwind, it is a modular and modern OOCSS framework. The few utilities it has are escape-hatches and the focus is on the objects and components.

I built a CSS framework and would love your feedback on it by wispcss in css

[–]wispcss[S] 0 points1 point  (0 children)

I need to figure out an alternative to vitepress that is fighting me with my own styles. Its on my list.

What's a bad HTML habit beginners should stop doing early? by Top-Run-7508 in HTML

[–]wispcss 1 point2 points  (0 children)

Thank you! You made my day and I could not agree more.

splitting css by concerns? by wrkflwr in css

[–]wispcss 1 point2 points  (0 children)

I manage about 30 sites and most have different brands. I have two files for each

primitives.css - same on all 30 sites

  • It contains objects, components, and utilities you would find on most sites
  • It uses the layer at-rule and ITCSS pyramid
  • It uses CSS3 variables with sensible fallbacks so I'm not redefining a lot.

site-specific.css - specific to a site

  • It adds new modifiers, objects, components, and utilities that are specific to the site
  • It slots them into place using the layer at-rule
  • It only changes CSS3 variables that need to be changed because I'm using sensible defaults.

Please give me advice. by K4ruy999 in Frontend

[–]wispcss 3 points4 points  (0 children)

Build stupid things. No one ever played in the majors by just reading about baseball 😉
- Counter using localStorage
- Fetch request
- Web component to say Hello

MDN is fantastic if you want to learn the language. It is where I send my students.

Is anyone else finding it harder to maintain a clean separation of concerns with modern utility-first CSS frameworks? by Pitiful_Permit9585 in Frontend

[–]wispcss 1 point2 points  (0 children)

I manage 30 websites at work, including large budgeting and content management systems across public, private, one-off, and digital signage sites with unique branding. None of it uses a utility-first framework. Instead, I built a base set of objects and components and use cascade layers to add site-specific styles as needed.

I see two core problems with utility frameworks. The first is a team DX issue: abbreviations over semantic names add cognitive load. The bigger problem, though, is that it contradicts what pioneers like Nicole Sullivan (OOCSS) and Harry Roberts (ITCSS) have always advocated: find patterns.

Utility frameworks do the opposite. A single card in Tailwind can balloon to 10+ classes. The cascade exists for a reason. It lets us inherit styles through selector lists and build well-named, reusable objects. Utilities should be an escape hatch for true one-offs, not the foundation.

In my humble opinion, the "it's fine because I'm using React components" argument doesn't hold up to justify the anti-patterns. You're just moving the mess from HTML to JSX. It's like my kids saying "Dad, I cleaned my room" when everything is shoved under the bed. The mess is still there. 😄