CSS

CSS Specificity is one of those things that you might assume you already have a firm grasp of since you are able to write solid CSS. Yet, CSS specificity is pretty confusing. It takes a little bit of time to get used to, but is well worth the effort. Have you ever created a CSS rule and wondered why it didn't apply to an element even though you thought it would?

I'm the first to admit, I'm guilty of taking short cuts and writing sloppy CSS. Usually coding sloppy CSS is because of strict deadlines, budget limitations, or putting a band aid on something (Meaning quick fixes without rebuilding entire pages or sections). And of course you could say what about planning and time management?

It's important to have a print CSS file. I know that with web work it may seem that most people will be viewing your site with a web browser, but for accessibility and best practice reasons you should always have a print CSS file in case someone wants to print out information from your website. Below are some tips to remember when creating a print CSS file.

In Cascading Style Sheets (CSS), the default behavior is that the most specific and last-defined rule takes the priority. That is the main reason to use CSS; you can specify one rule and it will apply (or cascade) to all instances of that element.