The Future of CSS in Drupal

Submitted by Benjamin Melançon on August 19, 2010 - 9:12pm

Link Title and URL:

# Do a round of cleanup in system.css, and ensure code is in the appropriate CSS file.
# Remove code, and possibly entire files, that clearly do not belong, e.g. border, color, font-family, margins, paddings, etc.
# Keep CSS that provides helpful visual cues, and accessibility compliance, such as system messages, progress bars, etc.
# Completely separate admin styles into separate files, i.e. use block.admin.css instead of block.css, when the purpose of the file is purely administrative.

Comments

Post new comment

Your name: *

E-mail: *

The content of this field is kept private and will not be shown publicly.

Homepage:

Subject:

Comment: *

You may post code using <code>...</code> (generic) or <?php ... ?> (highlighted PHP) tags.
You can use Markdown syntax to format and style the text. Also see Markdown Extra for tables, footnotes, and more.
Web page addresses and e-mail addresses turn into links automatically.
Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <img> <blockquote> <small> <h2> <h3> <h4> <h5> <h6> <sub> <sup> <p> <br> <strike> <table> <tr> <td> <thead> <th> <tbody> <tt> <output>
Lines and paragraphs break automatically.

User login

The Future of CSS in Drupal

Comments

Post new comment

Search

Agaric?

Agaric Design Collective

Copyright