11/15/2022 Categories discussion - Zoom call
Attendees
- Phil Norton (phillipnorton42)
- AmyJune (volkswagenchick)
- James Shields (lostcarpark)
- Bob Snodgrass (bsnodgrass)
- Ralf Koller (rkoller)
- Thijs Boots (tinto)
- Chris Wells (chrisfromredfin)
- Leslie glynn (leslieg)
Term hygiene:
- Do the terms conform with the American English dictionary
- Are special characters and punctiation being avoided?
- Differentiate between compound terms (aka leximes) & precoordinated terms
compound term : multiple words representing a single concept
precoordinated term: joining two or more concepts in order to describe a narrower concept more precisely
General benchmark criteria [Martin, Lisa Maria (2019): Everday Information Architecture. A Book Apart]
Clarity
- straight forward labels with a familiar language free of confusion and ambiguity
- category labels and navigation are not the place to establish corporate lingo or experiment with affordance (twitter moments) creativity is wonderful but not at the expense of clear accurate communications.
- clear doesn’t have to mean dull.
- don’t accept the most obvious label that pops into your mind automatically -> push back and explore further.
- it is possible to be clear and accurate while also conveying your brand story and values.
specificity
- avoid miscellaneous or catch all categories with generalized labels (waste basket taxonomies) at all cost.
- these sometimes show up when there are larger classification problems on the site leading to a handful of terms that don’t seem to fit anywhere in particular.
- they can also appear when the labels simply aren’t specific enough to accurately describe the content -> like junk drawers they will clutter up over time.
inclusivity
- we are often well intentioned but impact matters more than intent - so be purposeful about inclusivity.
- get input from diverse groups of users and colleagues.
- ask yourself how might these labels be misconstrued or harmful?
consistency
- use similar language, syntax and or parts of speech for labels that will be read in a group - for instance use all verbs, all gerunds or all nouns.
- consistency can speed up understanding and create an appealing linguistical rhythm
- be aware - consistent language doesn’t always lead to consistent meaning and meaning is much much more important.
General thoughts
- remember our target audience of site builders and those new to Drupal, but make sure categories make sense to experienced Drupalists as well
- lots of mudules fit into multiple categories
- consider more general names such as "media and images" as opposed to just "media" which may lend itself to just modules in the media ecosystem
- some category names (information architecture and content delivery for example) will probably not be understood by our target audience
- input from those new to Drupal is important.
- Leslie will try to get input during NEDCamp Contribution day on Friday. 11/18
Category discussions:
Access control access to content, possibly to be split to add authentication as a separate category
- Consider whether Authentication fits in Access Control or Security.
Accessibility - Bob's description is good, needs a few tweaks.
Content authoring - Lots of overlap of modules in other categories. Maybe role of content editor - produces content on a daily basis. don't lump too much in here - media and layout. Other categories don't really fit media or images. Is this just text based authoring? Might be worth changing the name of this category. Perhaps "Content editing" or "Content management" might have better intent.
- Some consensus that categories needed for modules relating to layout and media, though possibly avoiding those names to avoid limiting the categories to specific modules/ecosystems.
Content Delivery - Discussion around if this category is actually inclusive. Developers seemed to know what this category was about. People new to Drupal did not. Should merge this category with Import/Export or even Integrations?
- Some confusion with display of content, and noted that currently no category covers how content is displayed.
Data Privacy -
Next Steps
- Everyone will look at the categories before our next meeting and rate each as:
- = not useful, highly problematic
0 = may be useful, worth discussing (the right direction but needs some refinement)
+ = useful
- Next meeting will be held Tuesday 11/22 at 4:00 PM EST (same time as this week)
Asynchronous meeting
Reminder that today's site builder subcommittee meeting with be a synchronous call to discuss next steps on Categorization. The zoom link will be added in the threads at 4:00 PM EST
Welcome to the weekly Project Browser Initiative - Site Builders Subcommittee meeting
1️⃣ Today we will be holding a zoom call to discuss next steps for project categorization. The call will be recorded. Join us at https://drupalassoc.zoom.us/j/82469509462
| AmyJune (volkswagenchick) | volkswagenchick |
2️⃣ link to categories.numbers document https://files.slack.com/files-pri/T06GX3JTS-F04AUV81G5C/download/categor...
| leslieg | added document |
3 Categories.xlsx Excel Spreadsheet
| leslieg | added document |
4️⃣ Thanks to everyone who participated in the call today. We started to review the categories found in the Categories,numbers document (thread 2 above) Meeting notes can be found at https://pad.drutopia.org/p/project_browser_categories (edited)
| leslieg | added link to meeting notes |
5️⃣ Please share your thoughts here if you were unable to attend the call. All input is welcome (edited)
| rkoller | could either one of you @leslieg or @chrisfromredfin create a google spreadsheet ( so that it is under the correct account like others created for project browser). that way we could move the spreadsheet into a collaborative one. i could copy things over and also create extra columns for the evaluation of category names we agreed on yesterday. so everyone could add their ratings before the meeting next week |
| leslieg | Yes we will do that @rkoller |
Participants:
volkswagenchick, leslieg, rkoller, chrisfromredfin, tinto, philipnorton42, lostcarpark, bsnodgrass
Comments
Comment #9
leslieg commentedComment #10
leslieg commented