[wp-meta] [Making WordPress.org] #174: Link to generally related functions/classes

[Making WordPress.org]

#174: Link to generally related functions/classes
---------------------------+-----------------------
 Reporter:  samuelsidler   |       Owner:
     Type:  task           |      Status:  assigned
 Priority:  high           |   Milestone:
Component:  Developer Hub  |  Resolution:
 Keywords:  has-patch      |
---------------------------+-----------------------

Comment (by DrewAPicture):

 Replying to [comment:31 keesiemeijer]:
 > How do you see the extra taxonomy terms added? Manually, by users or
 mods, or some other way?

 Along the lines of the existing
 [https://make.wordpress.org/core/components/ core components list], I'd
 probably add a prompt on the reference article somewhere asking users to
 help us improve relevancy by suggesting related components.

 There's long been discussion about shoring up the `@subpackage` tags in
 the file headers to match the components list so we could do just such
 "categorization" at the devhub level. The thinking is that initial
 categorization would happen automatically from the parsed file headers,
 and more specific drilling-down happen by associating specific sub-
 components at the reference level.

 So it would certainly be a multi-prong effort, but I think there's value
 in (at least) pursuing the subpackage audit, even if we don't primarily
 consider it in defining relevancy to other elements.

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