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

WordPress Trac noreply at wordpress.org
Sat Feb 20 21:18:48 UTC 2016


#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 mikeschroder):

 Replying to [comment:78 DrewAPicture]:
 > This feels incredibly rushed to me.
 >
 > The first patch appeared 10 days ago, and 4.5 beta 1 is next week. I'm
 skeptical that we can ship something ''polished'' and user-test-iterated
 by then without pulling a lot of resources from other areas ''also''
 rushing to hit the beta 1 deadline.

 I agree that the development of the feature has been quick, but most of
 the contributors working on it have been separate from other areas, and/or
 those areas have already hit their deadline, so I don't feel like it's
 going to hurt other projects.

 > Citing the initial user tests @karmatosed documented in comment:77, I
 think inclusion of a Logo feature should run through the full feature
 plugin process before it ''ever'' gets to a point of core inclusion.

 I'm pretty mixed here.  The user tests were interesting. One bit of
 feedback that was good (and makes me lean in the direction you've
 mentioned) from the first test is that the user initially looked in
 "Header."

 That said, most of the difficulty the users faced seemed to stem from them
 not recognizing the Customizer as the place to go to modify the way their
 site looked, rather than a problem with the logo feature itself.  This
 makes me wonder if there's a way to test in a way that does not reflect
 these problems -- which we should definitely tackle -- on a feature that
 we're separately considering.

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


More information about the wp-trac mailing list