[theme-reviewers] Themes and Favicons

[Chip Bennett]

Theme Developers who don't want to mess with the site's Favicon aren't
burdened in any way whatsoever. I don't see a problem with requiring a
certain implementation of an optional feature.

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*.

I ran into one Theme just this week that changed the Site Title. The default
setting was the Theme Name. Even though this scenario isn't explicitly
addressed by the Guidelines, I still required that the Theme Developer
change the default setting to bloginfo( 'title' ) - because users will (and
should) not expect the title displayed in the site header to be the Theme
Name - or anything other than what they define as Site Title.

I see the Favicon as incredibly analogous. For users who configure a
favicon.ico, they should not have to worry about the Theme changing it
without their permission.

Chip

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

> On Tue, Oct 19, 2010 at 3:32 PM, Chip Bennett <chip at chipbennett.net>
> wrote:
> > it is
> > *required* to provide a user configuration setting, disabled by default
>
> Why should it be required?  There are already so many rules; why
> burden developers with more?
>
> This mandatory option goes against the WordPress philosophy of not
> having excess options.  Also, WPMU once came with default favicon, and
> there wasn't any such option (that I remember).
>
> Perhaps you could recommend that there be a way to change the favicon,
> either by option or filter.
> _______________________________________________
> 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/0eb9048c/attachment.htm>