2

I am developing a WordPress theme, and when reading the Codex article on Theme review, WP recommendeds against allowing custom favicons in a theme. Does anyone know the reason for this recommendation?

From the Codex:

Favicons
Themes are recommended not to implement custom favicon functionality.
If implemented, favicon functionality is required to be opt-in, and disabled by default.
If implemented, favicon functionality is required to support user-defined favicon images

1 Answer 1

2

Probably because a thing like a favicon is not necessarily tied to the on-page design, but to the branding of a site in general.

In other words: it's not specifically part of the "display" of the site. If a theme does choose to implemented it, an ender user might not want it (opt-in only) or they may want to use their own favicon (user-defined) to fit with their branding.

3
  • 2
    And that awkward moment when you see that über theme's default favicon in your site...
    – brasofilo
    Dec 5, 2012 at 15:58
  • Okay, that makes sense. I'm setting it up as opt-in and not including my theme's favicon, so it sounds like that should be okay.
    – chowwy
    Dec 5, 2012 at 16:34
  • 1
    Also, when a user changes themes, they don't expect their favicon to go away. Favicon functionality should be in a plugin.
    – Otto
    Dec 5, 2012 at 23:20

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.