Welcome to the weekly Project Browser Initiative - Site Builders Subcommittee meeting. This meeting:
➤ happens right here every Tuesday at 1pm PT | 4pm ET | 9:00pm UTC
➤ is chat only (no audio or video)
➤ happens in threads (please add threads to propose an additional discussion topic)
➤ will be exported as a transcript and posted to the agenda issue
| AmyJune (volkswagenchick) |
Yes, this is the one I struggle with out of the 3 |
| leslieg |
I agree - too many options to choose from. We do have category descriptions now so I’ll make a ticket for incorporating those |
| leslieg |
@drumm any thoughts on how we incorporate category descriptions into d.o and pull them into the PB |
| rkoller |
in regards of cleaning up the categories. there was work and discussions in the google doc so far. but why not start to do closed card sorts based on those categories with a selection of module and see how they perform. could be done for one with contrib module maintainers as well as beginners. two different groups. that way you get an idea how the current iteration of categories performs. and then repeat the cycle after updating the categories based on the sort results and the feedback. |
| drumm |
Re descriptions - First should mock up where they would be useful to show up on Drupal.org. Form select elements don’t really have space to show descriptions unless they are very, very brief, otherwise the select element would go from being an overwhelming list of options to an overwhelming wall of text. So do the descriptions surface somewhere on project pages like https://www.drupal.org/project/token? On project browsing pages like https://www.drupal.org/project/project_module? Somewhere else? (edited) |
| leslieg |
@drumm Thanks for the input. I was struggling with the same questions, so looking for opinions |
| leslieg |
@rkoller yes, there was some good work put into that spreadsheet, including the descriptions. Trying to determine next steps on that. Agree that both module maintainers and our target audience are both important pieces to figuring out how we improved the set of categories. |
| leslieg |
For the top 100 modules, we have been selecting the top 3, maybe we start with the categories selected there so far. |
| rkoller |
i’ve suggested to display the category descriptions to the sighted users as well as the screen reader users in particular for project browser (#3293907: Provide brief summaries about each category) . using it on drupal.org it would make sense for example on https://www.drupal.org/project/project_module if you select a module category that before the modules of the particular category are displayed the short description what the category is about could be displayed |
| drumm |
Are the descriptions written for project maintainers or for end users? Where do the two audiences see something that’s helpful? |
| rkoller |
@leslieg well. i would suggest the following. you take the current updated state the categories are in. and take a selection of modules for the interviewees you have. and then let them think out loud how they would categories the selection of modules they get presented. could be either a subselection of the top 100 or the top 100. plus in case of maintainers the modules they contribute to. and you just listen and record their thinking and their choices. same for the beginners (maybe with a smaller amount of modules). but never the less. you quickly get an idea which categories work and which are problematic. |
| rkoller |
@drumm i dont know with whom in mind the descriptions were written so far. personally i would write the descriptions for everyone. that everyone is able to understand the gist of a category no matter if the user is visiting the first time or if it is someone working with drupal for a long time getting a brief primer on top of categories page what the modules listed underneath have in common. my initial idea was to aid screen reader users navigating (as layed out in the link pasted above) but i’ve realized it als helps sighted users to have a brief summary about the gist of a category. if the user is aware if it it can be glossed over in case the user is uncertain or even cant remember he or she or them could get a refresher. and in particular in the context of of “browsing” aka project browser i consider a summary what a category and the listed module/projects are about helpful for everyone. |
| leslieg |
The descriptions were written with the target audience of the project browser in mind - site builders and those new to Drupal. Thinking that getting inoput from a few current module maintainers might be helpful. Do you agree? |
| rkoller |
yeah thats what i meant. running a two tiered approach and test the updated categories with people new to drupal same as seasoned drupal people/maintainers. that way you take care that there isn’t too much jargon and drupalisms included and it is approachable and inclusive for everyone. then you quickly see which categories work and which need more discussions. (edited) |
| bsnodgrass (he/him) |
This is a difficult issue and it would be great to get it cleaned up. As a site builder I've always used the categories in limited fashion. Without a description, I'm not sure they are much use either as a site builder or maintainer and in many cases they might have changed meaning over time. Some kind of added description available as a hover or help text from the category name would be helpful for any audience.(is the description part of the project-browser install data?) My local is broken/not up to date ATM, so I can't check.@rkoller I like the idea of adding a questions about categories in the 1:1 Interviews, I don't see that in the list |
| rkoller |
@bsnodgrass (he/him) it shouldn’t be an interview. just an observed closed card sort with a set of deliberately compiled modules where you you just watch and listen when the person sorting is thinking out loud about the reasoning why module a) goes into category 23. and where are stepping stones. ideally there shouldnt be many or any questions. just for clarification if the think out loud choice is too ambiguous. and what you mean with ” i dont see that in the list”? |
| rkoller |
and the descriptions are only in the google doc so far (and there arent descriptions for every category yet) |
| bsnodgrass (he/him) |
I didn't see that in the list of interview items |
| rkoller |
ah thanks for clarification.well i just suggested to test and hone the category terms. and from my understanding the interviews were only with people new to drupal and with a list of questions. the category validation and improvement is a bit different. it is more like the exercise we did during drupalcon last year it was i suppose. but with a single person sorting and thinking out loud each time. the only thing to prepare would be sets of modules to sort. and i would wouldnt limit those sorts to people new to drupal. contrib. module maintainers and experience site builders would be the second group to do those exercises with. |
| leslieg |
:+1: |
| leslieg |
Here’s a link to the Categories plan spreadsheet referenced above |
Comments
Comment #8
leslieg commented