Marketing Team Meeting Notes – December 13, 2017


Marketing Team Vision

Our vision for the Marketing Team is to be the go-to resource for strategy and content for other WordPress teams.

Getting Involved

All are welcome and encouraged to join in, comment on posts, and participate in meetings and on projects:

Today’s Meeting

The marketing team has unified at WCUS. Here is the document for our meeting notes. Feel free to read the scroll back in Slack.

Task of the Day:

Working on ‘WP Jargon Glossary for New People’ card.

Team members found some acronyms and group names (meta, polyglots, core) confusing, as well as tools (ie trac); how to find/update P2, taxonomy and accessibility terms, open source, and many others.

Some well-known WordPress sites have created their own glossaries, such as WP Beginner and wpmudev. There’s also Codex, which was noted as useful when learning CSS but not necessarily for encouraging people to become contributors.

Glossary Criteria/Rules

Criteria: We want the glossary to be newbie-friendly and searchable. One proposal was to build sections and alphabetize terms within each section. Minor note: be careful with camel casing (ex WordPress; WordCamp; cPanel – any brands that need to represented consistently)
@harryjackson1221: “PHP, MySQL and LAMP/LEMP should all reside in the same section.”

There may be certain terms in the glossary that can have more than one meaning, we should include all if we can

Potential Additions

@jeremyfremont mentioned he worked on a general Internet jargon glossary, whose terms may be useful to copy and paste. Many of the terms defined here are not WordPress specific, but there are a handful that may be useful. No copyright concerns as he wrote and defined all the items.

Useful for Later

@skarjune noted the Handbook should be used for the Glossary, but we cannot add any plugins. Design and setup on ORG are locked down.

Bridget’s idea: Include the glossary in our handbook.

Questions for Later

What’s the best way to organize our glossary? Alphabetical? Sub-categories? Alphabetize and then link from categories? Categorized with an alphabetized index? Perhaps a compromise btw section and alpha? We’ll ask the design team for help after we’re done.

Should we define what a wordpress.org profile page contains? (ex: You want a gravatar because…)

One of our Trello boards is a trac onboarding doc we need some help with (put a pin in this item and request assistance)

How far into team-specific terminology do we want to get? “There’s stuff like GTE that’s used a lot in #polyglots or deputy by the community people.”

@abhanonstopnews: may be worth having someone review some of the channels to see what terms frequently come up which might need to be added to the glossary?

Action Items

@harryjackson1221 will create categories (ex: Community; Hosting/Servers; Development) and @AfshanaDiya can alphabetize. Anchor links to accomplish TOC? Page jumps? What about adding IDs they link to?

@skarjune has seen a placeholder but not any implementations of anchors in other handbooks. He will check with meta team for advice/examples.

PS:

Notes taken by: @alisonsmith

Meeting attended by: @bridgetwillard @Harryjackson1221 @sereedmedia @dhruvpandya @miker @abhanonstopnews @bseekins @nuanel @riankinney @AfshanaDiya @meher @skarjune @newyorkerlaura @jenblogs4u @westcountymedia @jeremyfremont

#content