class vs. id in code

Tata · Post by **Tata** » Wed Jul 23, 2014 4:55 am

I have found IMHO VERY INTERESTING articel at http://csswizardry.com/2014/07/hacks-fo ... ecificity/.

I STRONGLY RECCOMMEND all designer and coders read this and think about following this simple explained philosophy.

cmb · Post by **cmb** » Wed Jul 23, 2014 10:11 am

Tata wrote:I have found IMHO VERY INTERESTING articel at http://csswizardry.com/2014/07/hacks-fo ... ecificity/.

I STRONGLY RECCOMMEND all designer and coders read this and think about following this simple explained philosophy.

That is a very interesting article indeed, and I will try to avoid styling IDs in the future, as that actually makes sense. It might be noteworthy that inline-styling (<p style="...">) is even worse than styling IDs, so it should usually be avoided, too. As the article is lacking a link to the specification: http://www.w3.org/TR/CSS2/cascade.html#specificity.

Something else I like to suggest especially for plugin developers: don't overstyle your plugins! It might look great when viewed with one template, but it might look bad when viewed with another (sometimes the plugin might be even partially unusable, unless the user makes some customizations).

Tata · Post by **Tata** » Wed Jul 23, 2014 10:21 am

The simplest is the styling of a plugin backend, the better. There is no crucial need to save space or force any gorgeus design. The functionality is the m ost important.

svasti · Post by **svasti** » Wed Jul 23, 2014 5:04 pm

Tata wrote:I have found IMHO VERY INTERESTING articel at http://csswizardry.com/2014/07/hacks-fo ... ecificity/.

+1 indeed
I propose to use this article for template guidelines. ... of course for plugin authors too.

svasti

CMSimple_XH–Forum

class vs. id in code

class vs. id in code

Re: class vs. id in code

Re: class vs. id in code

Re: class vs. id in code