[wp-meta] [Making WordPress.org] #7577: Discussion: Plugin name length, readability and consistency.

[Making WordPress.org]

#7577: Discussion: Plugin name length, readability and consistency.
------------------------------+---------------------
 Reporter:  dufresnesteven    |       Owner:  (none)
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+---------------------

Comment (by dufresnesteven):

 > We should also consider the use-case of the two different screens
 because although it may seem similar, it's not. Search in admin area or
 .org site is for "discoverability" so users can find the solution they're
 looking for --- the plugin screen in admin area is for site management.

 I am sensitive to the difference in context between discovering and
 managing and agree it is a notable distinction. For it to matter, we do
 have to agree that the plugin name is the primary driver of
 discoverability. If we don't find that is the case (I personally don't
 think it should be), I don't see the value in supporting a path that makes
 deviation possible based solely on the fact that they are different
 contexts without specific use cases where it makes sense for them to be
 different.


 ----

 Maybe starting with better guard rails for the display name, regardless of
 whether it comes from the readme.txt or plugin headers may be a better
 approach. I wouldn't want plugin authors to move the not-so-user-friendly
 plugin names that we see in the readme.txt to their Plugin headers to
 maintain their (unfair?) ranking. That isn't a better outcome for end
 users.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/7577#comment:8>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org