[theme-reviewers] Best practice CSS options

Emil Uzelac emil at themeid.com
Sun May 8 06:05:43 UTC 2011


and there come the UN hehehe, yes I think so too and I agree :)

Cheers,
Emil

*----*
*Emil Uzelac* | ThemeID | T: 224-444-0006 | Twitter: @EmilUzelac | E:
emil at themeid.com | http://themeid.com
Make everything as simple as possible, but not simpler. - Albert Einstein



On Sun, May 8, 2011 at 12:44 AM, Philip Walton <philip at philipwalton.com>wrote:

> Ryan and Emil, I think you two are talking about different things (unless
> I'm misreading).
>
> The original question was not about inline verse linked styles, it was
> about creating a theme option that a theme user could write custom CSS
> styles into that would override existing styles and alter the look of their
> public facing pages. The OP was asking for a recommendation about how best
> to accomplish that.
>
> In such a case, I think it's safe to say that the amount of CSS someone
> would write into a textarea would be very little. If someone knew enough
> about CSS to write tons of it, you'd think they'd know enough to actually
> edit the CSS file.
>
> So, assuming it's very few styles, there's probably no difference one way
> or another in terms of page load (inline vs linked). One the one have you
> have browser caching, but on the other hand you have fewer HTTP requests.
>
> Furthermore, the type of user who would actually write custom CSS into a
> theme option instead of hard coding it into the styles.css (or creating a
> child theme) probably isn't loosing sleep over how fast his/her theme is
> loading.
>
> Philip
>
>
>
> On Sat, May 7, 2011 at 10:03 PM, Emil Uzelac <emil at themeid.com> wrote:
>
>> CSS from the Theme itself should not be used/passed into Theme Options if
>> there is no need for that, if someone wants to work on performance either a)
>> for Theme b) for Theme Options they are more than welcome to do that. Simple
>> shorthand properties will speed up the any page.
>>
>> *----*
>> *Emil Uzelac* | ThemeID | T: 224-444-0006 | Twitter: @EmilUzelac | E:
>> emil at themeid.com | http://themeid.com
>> Make everything as simple as possible, but not simpler. - Albert Einstein
>>
>>
>>
>> On Sat, May 7, 2011 at 11:03 PM, Ryan Hellyer <ryan at pixopoint.com> wrote:
>>
>>> > From: Emil Uzelac <emil at themeid.com>
>>>
>>> > Subject: Re: [theme-reviewers] Best practice CSS options
>>> >
>>> > Performance-wise for Theme Options? come on now. How much of styles can
>>> one
>>> > have to worry about the page speed? The important part is that our
>>> custom
>>> > CSS or JS is used only where we need it and that's i.e.
>>> theme-options.php
>>> > and yes we do use external styles. I would not worry about performance
>>> at
>>> > all. wp_head is the easiest and definitely the best option to do this
>>> so.
>>> >
>>> > Cheers,
>>> > Emil
>>>
>>> I think you are assuming that generated CSS will only be very small,
>>> whereas it could easily be all of the CSS used in the theme. Plus, if
>>> someone wants to improve their themes performance the theme review team
>>> presumably doesn't want to intentionally stop them from doing so.
>>>
>>>
>>>
>>> _______________________________________________
>>> theme-reviewers mailing list
>>> theme-reviewers at lists.wordpress.org
>>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>>>
>>>
>>
>> _______________________________________________
>> theme-reviewers mailing list
>> theme-reviewers at lists.wordpress.org
>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>>
>>
>
>
> --
> Philip Walton
>
> _______________________________________________
> 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/20110508/68005098/attachment.htm>


More information about the theme-reviewers mailing list