[theme-reviewers] Themes and Favicons

Chip Bennett chip at chipbennett.net
Tue Oct 19 21:31:24 UTC 2010

But what Plesk, shared hosts, or even WPMU do isn't really under our

IMHO, the *best practice* is to expose the option to the user. What
Developer freedom (or judgement) would we be restricting by requiring the
option be exposed to the user?

" If users don't like the favicon, they're not forced to use that theme."

This take-it-or-leave-it sentiment is completely antithetical to the
user-freedom philosophy that underlies both WordPress and the Theme


On Tue, Oct 19, 2010 at 4:06 PM, Austin Matzko <austin at pressedcode.com>wrote:

> On Tue, Oct 19, 2010 at 3:47 PM, Chip Bennett <chip at chipbennett.net>
> wrote:
> > The reason I think it should be *required* to provide a user
> configuration
> > setting is, as I've already stated, because the Favicon is part of the
> site
> > identity/branding, and not part of the Theme.
> My point is that where issues are not clear-cut, there shouldn't be
> *requirements.*  You say favicons should be determined solely by an
> individual site's branding; Plesk, many shared hosts, and WPMU back in
> the day disagree (by providing their own favicons by default).  So why
> not give developers some freedom to work it out using a measure of
> judgment?  If users don't like the favicon, they're not forced to use
> that theme.
> It's OK if there are contingencies that have not been specifically
> regulated.
> _______________________________________________
> 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/20101019/e6f95f0a/attachment.htm>

More information about the theme-reviewers mailing list