[wp-trac] [WordPress Trac] #33755: Add Site Logo to WordPress Core

[WordPress Trac]

#33755: Add Site Logo to WordPress Core
-------------------------------------------------+-------------------------
 Reporter:  fatmedia                             |       Owner:
     Type:  feature request                      |      Status:  reopened
 Priority:  normal                               |   Milestone:  4.5
Component:  Customize                            |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  ux-feedback has-patch needs-testing  |     Focuses:  ui
  needs-unit-tests has-screenshots               |
-------------------------------------------------+-------------------------

Comment (by fatmedia):

 Replying to [comment:52 mark-k]:
 > @celloexpressions, it is not only a useless feature, its implementation
 will actually hurt more then help.
 >
 > Modern sites have minimum two logos, a desktop and a mobile. Now for a
 mobile you will want a retina version as well as a "plain" one. In
 addition the direction in which modern site design goes, you have two
 distinct logos for "above the fold" area and for the main menu (take a
 look at techcrunch), therefor there is no point talking about A logo, you
 need to be able to set several logos and when they should be used,
 otherwise themes will still need to add their own options for the
 additional logos which will just confuse users.
 >
 > Before smartphone became popular I would have agreed with the feature,
 but now it is just pointless.

 Your opinion, which you've already made pretty clear under your other
 username, isn't really helping this discussion. If you could provide
 something other than an anecdotal reference to how the logo for a huge,
 custom tech news site works, I think your points might be useful for
 improving the feature once it's been implemented. Failing that, it seems
 like you're just working to block something that you don't personally like
 for whatever reason.

 It's already been stated by people from .com and the JetPack team that
 users like the feature when it's available and that it generates minimal
 support overhead. That seems like strong enough evidence to justify
 including it to me.


 The entire point of this feature is to standardize something that's
 already being done in the wild in a myriad of different ways. If WordPress
 core can't provide a standard for something that's already in-use and then
 iterate on it to make it better, I'm not even sure what it is that we're
 doing here.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/33755#comment:53>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform