[wp-meta] [Making WordPress.org] #7531: Hook automatic documentation

Making WordPress.org noreply at wordpress.org
Fri Apr 12 05:47:37 UTC 2024


#7531: Hook automatic documentation
------------------------------+---------------------
 Reporter:  coquardcyr        |       Owner:  (none)
     Type:  feature request   |      Status:  new
 Priority:  low               |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+---------------------
Changes (by dd32):

 * priority:  normal => low
 * type:  enhancement => feature request


Comment:

 For the vast majority of WordPress users, unfortunately I don't think the
 effort of adding automatic hook documentation for plugins is going to be
 overly useful.

 As I'm sure most will know, most plugins don't include any hooks of use at
 all, and when they do, often they're incorrect or not totally usable.

 Plugins can choose to document their existing hooks in their readme, or on
 their support site already. I'm aware of a few who do.

 See also: #3126 (List WP-CLI commands), and that the plugins page lists
 Blocks that the plugin includes (But this is partially because we needed a
 way to find a plugin by a specific block slug IIRC)

 That all being said; We already have a hook documentation extractor that
 we'd use for this, if we chose to do it. What's used for
 developer.wordpress.org extractions from Core https://github.com/WordPress
 /phpdoc-parser

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


More information about the wp-meta mailing list