[theme-reviewers] Minified CSS

[Chip Bennett]

I'm not inherently opposed to having such coding standards for
repository-hosted Themes (and will very likely make an effort to ensure that
my own Theme conforms to those standards). I just don't think it's a battle
we should choose to fight anytime soon. Given the initial reaction to the
beefed-up Theme Review Guidelines as they exist now, can you imagine the
reaction if/when we throw the switch on requiring the WP CSS Code Standard?

If/when we go that route, we are going to need to provide a LONG lead-time
for implementation/enforcement.

And quite honestly: I think the reviewers' time is probably best-spent - at
least for the foreseeable future - on things other than ensuring that class
names have hyphens instead of underscores, and that CSS attributes are
alphabetized and properly indented.

Chip

On Fri, Feb 18, 2011 at 11:36 AM, Lance Willett <nanobar at gmail.com> wrote:

> > Bear in mind that the CSS Coding Standards found in the Codex apply to
> core
> > code, and at least at this time the core CSS
> > Coding Standards are not part of the Theme Review guidelines.
>
> The CSS code standards are intended to be universal for any WP
> development, not just for core. They came out of our work on
> WordPress.com themes, actually. But should apply to plugins, themes,
> core, and anything else.
>
> Right now they are in draft mode because Nacin made it that way after
> John O'Nolan commented that they weren't to his liking. :) I plan to
> talk with John about where/when to open a public discussion about the
> standards so we can remove the draft status.
>
> – Lance
> _______________________________________________
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20110218/e9d0d742/attachment.htm>