The Project Browser Initiative is working on a new page for adding and installing modules. The default display of the Project Browser will show Drupal modules that have a release that is compatible with the version of Drupal the site is using. A card will be displayed for each of the modules (projects). The key components displayed on the card will include a logo, a short description and the categories this module belongs to.

The number of categories was recently reduced from 55 down to 19 to help folks searching for modules to more effectively use the category filter.

First, read through the module’s project page on Drupal.org . If needed, spin up the module on SimplyTest.me or DrupalPod to understand what the module does. Then review the Category Definitions and suggest 1-3 categories for the module. (When in doubt, err on the side of fewer, not more!)

Project page: https://www.drupal.org/project/redirect

Proposed Categories

  1. Content Editing Experience
  2. Administration Tools

Comments

ChrisDarke created an issue. See original summary.

chrisfromredfin’s picture

Component: Documentation » Contrib changes
Issue summary: View changes
leslieg’s picture

Status: Active » Needs work
pearcraft’s picture

Four categories are currently listed for Field Group.
1.) Content, 2.) Content Construction Kit (CCK), 3.) Fields & 4.) Utility

As Project Browser will support only Three categories,
I propose that the Utility category be removed as it is the least specific category for Field Group.

pearcraft’s picture

Status: Needs work » Needs review
leslieg’s picture

Postponed until a new smaller list of Categories is finalized.

leslieg’s picture

Issue summary: View changes
Status: Postponed » Needs work

Updated the issue summary to reflect the recent change to reduce the number of Categories from 55 down to 19.

tishmg’s picture

I'm working on this one. #Portland2024

tishmg’s picture

Issue summary: View changes
Status: Needs work » Needs review

Content Editing Experience should be the category for this because it affects how the content admin UI looks.

kbeck303’s picture

I'd like to propose adding the following categories to the list

Administration Tools - because it is used to setup, enhance, configure, or maintain the site.
Content Editing Experience
Developer Tools - because it assists with developing the backend of the site.

bsnodgrass’s picture

Issue summary: View changes

I agree with Administrator Tools and Content Editing Experience.

Given that tools such API modules like Ctools, devel, twig tweak, and drush would all be considered Developer Tools, including Field Group in this list could be confusing for a basic site-building audience.

Adding Administrator Tools to the Issue Summary, Still needs review.

bsnodgrass’s picture

Issue summary: View changes

Added project page to Summary: https://www.drupal.org/project/redirect

@leslieg Can you review?

leslieg’s picture

Status: Needs review » Reviewed & tested by the community

Agree with comments in #11. Moving to RTBC

leslieg’s picture

Status: Reviewed & tested by the community » Fixed

Gave credit and marked this issue as fixed.

Status: Fixed » Closed (fixed)

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