[development] websiteoptimization.com css size
tss24 at cornell.edu
Fri Jan 6 22:31:16 UTC 2006
No, I never said remove the out of box experience at all. I still like it
and want it, for sure.
What I'm proposing is to move everything in /misc into theme specific
folders. Out of the box it functions like it currently does.
However, if they decided to download uber-theme-XYZ, that theme may decide
to turn off certain JS features, turn on other ones it may need, and all the
time not have to worry about drupal.css since it already implements what it
needs to and includes drupal.css if it so desires.
There is a big distinction there.
Make drupal.css part of the default themes, not a required css file that
*all* themes *have* to use (without overriding).
On 1/6/06, Jeff Eaton <jeff at viapositiva.net> wrote:
> Simple: because Drupal is not JUST a development framework. It is, out
> of box, a functional web site CMS. A lot of stuff that we take for
> granted (having an 'edit' tab when we have perms to change a node, for
> example) are handled by that CSS file. Obviously, there's a case of
> creep somewhere along the line as unecessary CSS code snuck in that goes
> way beyond those basics. All the styles for drawing archive.module's
> calendar, for example, would best be moved into archive.css and included
> as needed IMO.
> Come to think of it, that's a nice idea for a patch.
> But, to return to the question, eliminating all CSS from core would be a
> definite mistake IMO. Stripping down drupal.css to a bare minimum,
> though? I'm all for that.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the development