Title: CSS coding standards and CSS frameworks
Last modified: August 19, 2016

---

# CSS coding standards and CSS frameworks

 *  Resolved [Simon Fairbairn](https://wordpress.org/support/users/simonfairbairn/)
 * (@simonfairbairn)
 * [15 years, 5 months ago](https://wordpress.org/support/topic/css-coding-standards-and-css-frameworks/)
 * Hi,
 * I’m currently developing a WordPress theme and I’m trying to keep to the CSS 
   coding standards. However, I’d like to use the Blueprint CSS framework, which
   often has up to 24 class declarations for 1 property.
 * According to the standards, each comma-separated selector in a single block should
   be separated by a line break.
 * How flexible are these standards? It seems to me to be a little bit crazy to 
   transform this
 *     ```
       .grid-1, .grid-2, ... , .grid-24 {
          margin-right: 10px;
       }
       ```
   
 * into this
 *     ```
       .grid-1,
       .grid-2,
       ...,
       .grid-24 {
           margin-right: 10px;
       }
       ```
   
 * resulting in a much, much longer (and, in my opinion, more unmanageable) file.
 * Any thoughts on this would be welcome.
 * Thanks,
 * Simon

Viewing 4 replies - 1 through 4 (of 4 total)

 *  [Steffen Jørgensen](https://wordpress.org/support/users/jint/)
 * (@jint)
 * [15 years, 5 months ago](https://wordpress.org/support/topic/css-coding-standards-and-css-frameworks/#post-1788749)
 * No reason to seperate selectors by linebreaks.
    However, if you **want** to do
   so, it would be a quick search/replace in notepad
 *  Thread Starter [Simon Fairbairn](https://wordpress.org/support/users/simonfairbairn/)
 * (@simonfairbairn)
 * [15 years, 5 months ago](https://wordpress.org/support/topic/css-coding-standards-and-css-frameworks/#post-1788755)
 * I’d rather not, to be honest: it’ll turn 200 lines into over 700.
 * It’s just that the [CSS coding standards](http://codex.wordpress.org/CSS_Coding_Standards)
   page was adamant that each selector should have its own line.
 * I’ll leave it as it is. Thanks for your input.
 *  Anonymous User
 * (@anonymized-3085)
 * [15 years, 5 months ago](https://wordpress.org/support/topic/css-coding-standards-and-css-frameworks/#post-1788766)
 * It’s purely for ease of reading – it doesn’t affect the validity of your CSS 
   at all.
 * personally I’d say it’s ok to leave as is.
 *  Thread Starter [Simon Fairbairn](https://wordpress.org/support/users/simonfairbairn/)
 * (@simonfairbairn)
 * [15 years, 5 months ago](https://wordpress.org/support/topic/css-coding-standards-and-css-frameworks/#post-1788776)
 * Awesome, thanks for your help!

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘CSS coding standards and CSS frameworks’ is closed to new replies.

## Tags

 * [coding standards](https://wordpress.org/support/topic-tag/coding-standards/)
 * [css](https://wordpress.org/support/topic-tag/css/)

 * 4 replies
 * 3 participants
 * Last reply from: [Simon Fairbairn](https://wordpress.org/support/users/simonfairbairn/)
 * Last activity: [15 years, 5 months ago](https://wordpress.org/support/topic/css-coding-standards-and-css-frameworks/#post-1788776)
 * Status: resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics