Problem/Motivation

One thing we realized early in the initiative is that the data we can get from Drupal.org has a huge impact on the success of Project Browser. To that end, we decided to re-examine the category structure used to classify module projects today. Currently that list consists of 54 terms, with generic terms like “examples,” specific catch-all phrases like “content,” and unspecific ones like “other.” The ultimate goal is to consolidate the list of categories to a more manageable number, give them a more universal appeal, and make them easier to comprehend for everyone.

The initial approach was to update and refine the existing list of terms, which turned out to be problematic. During DrupalCon Europe in Prague, the list got a fresh restart during a BoF and the adjacent contrib day. Based on those results, an initial closed card sort was produced for a small group of volunteers. Since then, across several meetings, the category list has been iterated on, and scope notes were created for each term. They were cross-checked with additional input from early sessions at DrupalCon Portland, as well as ad-hoc impromptu feedback sessions along the way.

The current state isn’t perfect yet but is somewhat stable. We are looking for additional feedback from the community to challenge and benchmark the category list with (ideally) a diverse and wide range of modules sorted by a diverse and wide range of people, who are experienced and savvy in Drupal... and that’s where you come in!

Instructions - Start by opening this Google Template
https://docs.google.com/document/d/1c13vZolKX2gGtLvu8gtOiJhlyIJyFTzhZIgM...

Please make a copy of this Google Doc, follow the instructions in the doc, share your copy of the doc (blue button at the top right) so that anyone can view, and put the resulting shareable link in this issue.

Comments

leslieg created an issue. See original summary.

leslieg’s picture

Title: New Category Maintainer Feedback » New Categories for Project Browser - Maintainer Feedback
luke.leber’s picture

volkswagenchick’s picture

jwilson3’s picture

prabhu9484’s picture

heddn’s picture

I went through and attempted to categorize everything I've had contributions to in the past 12 or so months. Most everything was able to make it into a category. I do have some reservations about the "Administrator Experience" category. Concerns noted in the doc.
https://docs.google.com/document/d/1bz3tb1dTh1byGKHvuL7hsrlykaZZt7fTHvzS...

joelpittet’s picture

leslieg’s picture

Issue tags: +fldc23

Good to meet you at FLDC today @earthday47 . Thanks for taking the time to give inout on this issue - please share the link with other module maintainers so that we can get a good number of folks to weigh in before we make a final decision on the new categories.

Tagged the issue with fldc23

lauriii’s picture

joachim’s picture

https://docs.google.com/document/d/1QEGciDcFW2kuviblkciGGlB9qRGl1WJQuXJJ...

> I do have some reservations about the "Administrator Experience" category.

@heddn Good point about site builder != administrator.

Something like Field Tools is for site builders; User Flood is for administrators.

A LOT of my modules belong in 2 or even 3 categories, and it's really hard to decide on which one is the primary.

I think there's a need for a Community category, as I don't know where modules like Group and OG are supposed to go.

Overall though this feels really well thought-out, and the classification exercise really well set-up. Thanks to everyone in this initiative :)

joseph.olstad’s picture

I have nothing to add that wasn't already mentioned above, well thought out classifications with suggestions made for improvements, I suggest @leslieg has enough feedback to make a few changes and we can review again next year?

jurgenhaas’s picture

chrisfromredfin’s picture

Status: Active » Fixed

I cannot thank everyone enough for their time commitment here. I know it was a lot, but it was invaluable to us as we continue to revise and hone in on a new taxonomy for projects. #DrupalThanks!

chrisfromredfin’s picture

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.