That’s why css names should be semantic. I’m sure it started actually purple until UX said “can we make this primary text more blue so it doesn’t look like a clicked link?” Replacing all references to “purple” wasn’t an option because of unrelated usage of that word elsewhere and they weren’t using an IDE capable of contextual rename of a css class. So they just changed the color code and called it a day.
I’m sorry but the solution to every argument is not just to throw of the word “semantic” in the sentence.
I’m sorry but who is saying that? Nobody is. If you are paying attention to the context, you will notice they are talking about CSS class names. That’s the context, and it’s a valid point within that context.
That’s why css names should be semantic. I’m sure it started actually purple until UX said “can we make this primary text more blue so it doesn’t look like a clicked link?” Replacing all references to “purple” wasn’t an option because of unrelated usage of that word elsewhere and they weren’t using an IDE capable of contextual rename of a css class. So they just changed the color code and called it a day.
sed -i 's/.purple/.not-purple/g' *.cssdone, boss
Removed by mod
It’s fine as long as you have proper source control. Run it and check the diff before committing.
But I set my
.gitdirectories to have.cssfilename extensions!!?! It shouldn’t be my job to educate you.Gotta do it on the HTML files and JS files too. Then you gotta re-test every page that uses those files.
Then the boss looks over your code and asks why you didn’t just change the actual color because that’s easier to QC.
Yeah, but if you just used css variables, this would’ve been a doddle. One and done.
I’m sorry but the solution to every argument is not just to throw of the word “semantic” in the sentence. Context is everything.
I’m sorry but who is saying that? Nobody is. If you are paying attention to the context, you will notice they are talking about CSS class names. That’s the context, and it’s a valid point within that context.