[2.0] Inline CSS

Mark threads with "[2.0]" for discussions about features in the longer-term future, "[1.6]" is for short-term. This is not the place for general discussions or plugin or template requests. Only features that are approved to happen by the core team should be listed here for better structuring.
Locked
User avatar
garvinhicking
Core Developer
Posts: 30015
Joined: Tue Sep 16, 2003 9:45 pm
Location: Cologne, Germany
Contact:

[2.0] Inline CSS

Post by garvinhicking » Sun Jan 02, 2011 10:47 pm

.. discussion here ...
# Garvin Hicking (s9y Developer)
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/

User avatar
yellowled
Regular
Posts: 6959
Joined: Fri Jan 13, 2006 12:46 pm
Location: Eutin, Germany
Contact:

Re: [2.0] Inline CSS

Post by yellowled » Mon Jan 03, 2011 7:03 pm

Some rules of thumb:

* This should apply to backend and frontend, core and plugins -- unless it is absolutely necessary, please leave the styling of anything to the backend/frontend template's CSS.

* What is absolutely necessary? Well, it's much easier to state what isn't: Anything related to colors, fonts, backgrounds, etc., i.e. anything which relates to the "branding" or design of either backend or frontend should be left to the respective template.

[To be continued; I need to give this some though. Questions welcome.]

YL
amazon Wishlist - Serendipity-Podcast (German only, sorry)

Locked