[wp-meta] [Making WordPress.org] #3577: Add Dictonary for Captioner on WordPress Events

[Making WordPress.org]

#3577: Add Dictonary for Captioner on WordPress Events
-------------------------+---------------------
 Reporter:  Travel_girl  |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:
Component:  Handbooks    |  Resolution:
 Keywords:               |
-------------------------+---------------------

Comment (by coffee2code):

 The recently-released [https://make.wordpress.org/docs/style-guide/
 Documentation Style Guide] includes a [https://make.wordpress.org/docs
 /style-guide/word-list/ Word list and usage dictionary] section that
 fulfills a large part of this request.

 While that guide would not be appropriate for listing WordPress companies,
 people, and commonly referenced plugins/themes, it definitely should
 include technical terms, abbreviations, acronyms, etc that one would
 expect to encounter in the WordPress sphere.

 As @casiepa [comment:3 noted], some of the contributor teams have their
 own glossaries of terms. (Having a universal glossary has also been
 proposed in #4522.)

 Some existing glossaries:
 * https://wordpress.org/support/article/glossary/
 * https://make.wordpress.org/marketing/2018/02/28/wordpress-jargon-
 glossary/
 * https://make.wordpress.org/core/handbook/glossary/
 * https://make.wordpress.org/polyglots/handbook/glossary/
 * https://developer.wordpress.org/block-editor/handbook/glossary/
 * https://make.wordpress.org/community/handbook/community-team/glossary/
 * https://make.wordpress.org/test/handbook/glossary/ (this one is very
 test domain specific)

 Obviously there is a definite need for cross-team collaboration to try to
 create a universal glossary (with each team amending the glossary within
 the context of their own handbooks for team-related terms).

 In that vein, the [https://make.wordpress.org/tv/handbook/ Make
 WordPress.tv team's handbook] seems the most appropriate place for a
 captioner's glossary. That could pull the general terms from the
 (hypothetical) universal glossary and supplement it with the companies,
 people, plugins/themes, etc.

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