- 🇺🇸United States leslieg
Agree with suggestion. Updating summary and moving to RTBC
- 🇺🇸United States leslieg
Agree with Administration Tools asoit Empowers site builders and administrators with no-code tools to maintain the site. Not really a Developer Tool so wouldn't select that category
Updating summary and moving to RTBC
- 🇺🇸United States leslieg
While there were some good suggetions, Chris and I reviewed the module and feel the best category to use is Integrations
Updating summary and moving to RTBC
- 🇺🇸United States leslieg
Agree with suggestions. Updating summary and moving to RTBC
- 🇺🇸United States leslieg
Agree with suggestions. Updating summary and moving to RTBC
- 🇺🇸United States leslieg
Agree with suggestions. Updating summary and moving to RTBC
- 🇺🇸United States leslieg
Agree that this falls under Site Structure. Doesn't really fit into definitions of Content Display or Site Search
Updating summary and moving to RTBC
- 🇺🇸United States leslieg
Agree with Integrations. Updating summary and moving to RTBC
- 🇺🇸United States leslieg
Agree with suggestions of Site Structure and Administration Tools
Moving to RTBC
- 🇺🇸United States leslieg
Agree with suggestions. Updating summary and moving to RTBC
- 🇺🇸United States leslieg
Agree with suggestions.. Updating summary and moving to RTBC
- 🇺🇸United States leslieg
@chrisfromredfin suggested Integrations, content display, developer tools
- 🇺🇸United States leslieg
Agree with the suggestions in #9
Updating summary and moving to RTBC
- 🇺🇸United States leslieg
Agree with suggestions. Updating summary and moving to RTBC
- 🇺🇸United States leslieg
@chrisfromredfin suggested Integrations, content display, developer tools
- 🇺🇸United States leslieg
Agree with those 3 categories.
Updating summary and moving to RTBC
- 🇺🇸United States leslieg
@chrisfromredfin suggested Integrations, content display, developer tools
- 🇺🇸United States leslieg
Agree with Performance and adding Integrations.
Updating summary and moving to RTBC
- 🇺🇸United States leslieg
Agree with Administration Tools.
Updating summary and moving to RTBC
- 🇺🇸United States leslieg
Agree with #8 to use Automations and also Security fron #6 and #7
Updating summary and moving to RTBC
- 🇺🇸United States leslieg
Good possibilities for categories. Chris and I discussed this and feel that Administration Tools is the best fit since it empowers site builders and administrators with no-code tools to maintain the site. Development isn't needed to use it and although it does relate to the other 2 suggestions, it doesn't really fit into the descriptions.
- 🇺🇸United States leslieg
We felt that it's better suited for Developer Tools as it "Empower developers with tools that assist with developing and debugging the frontend or backend of the site." Users most likely wouldn't expect to find this under Content Editing experience.
Updating summary and moving to RTBC
- 🇺🇸United States leslieg
Agree with #7 that this falls under just Access Control. We didn't think Content Editting Experience as it doesn't really fit into "Enhance the editorial interface and improve the processes and workflows around creating, editing or removing content."
Updating Summary and moving to RTBC
- 🇺🇸United States leslieg
Agree that this falls under Developer Tools. Doesn't really fit under Integrations or Decoupled. Updating summary and moving to RTBC
- 🇺🇸United States leslieg
After discussing with Chris, we feel Integrations is the key category and also that Performance should be used. Updating summary and moving to RTBC
- 🇺🇸United States leslieg
This really doesn't fit into Content Editing Experience since it's about how the content is displayed only. Agree with only having category Content Display. Updating summary and moving to RTBC
- 🇺🇸United States leslieg
updated issue summary and moving to RTBC after discussing with @chrisfromredfin
- 🇺🇸United States leslieg
Agree with Administration Tools. It doedn't fit into Import and Export or Integrations per the definitions.
Updating Issue Summary and moving to RTBC
- 🇺🇸United States leslieg
chrisfromredfin and I reviewed this and feel that this falls under Administration tools. It's not really about how the content is displayed.
updating summary and moving to RTBC
- 🇺🇸United States chrisfromredfin Portland, Maine
This is only providing an API - so is just a Developer Tools.
- 🇺🇸United States chrisfromredfin Portland, Maine
Integrations - since there's an external library it's gluing on; and,
Administration Tools - since it's empowering the site builder to use this library with a no-code tool
- 🇺🇸United States chrisfromredfin Portland, Maine
Integrations for sure as top choice. I think it would be worth adding as Administration Tools as well, since it's primarily aimed at the Site Builder for enhancing the UX.
- 🇺🇸United States chrisfromredfin Portland, Maine
This belongs in Integrations, since it's gluing an external service onto Drupal.
- 🇫🇷France vbouchet
I think "Administration Tools" is still a valid category. it does not do anything specific around "Accessibility" (which would be a potential category) and it does not change the "Content Editing Experience" (which would be a potential category as well).
I suggest to stick at:
1. Administration Tools - 🇫🇷France vbouchet
The module is today categorised into:
1. Administration Tools
2. Developer ToolsThese categories are still part of the curated list and make sense to me.
"Access control" definition is "Grant or restrict access to content, assets, or site functionality, or extend the authentication/login process.". I don't think it really applies here as it only impact how config is exported/imported.
"Import and Export" definition is "Help transfer content and data into or out of the site, by migration, backup, or exposing data to external systems." It can tentatively be a third category but I personally don't think "content and data" apply to "configuration".
- 🇺🇸United States leslieg
I agree with Content Display in #6. Since this module only changes the display of Views, I would not add Media. It does provide a Views style plugin to Slick Carousal so I think Integrations is ok. While developers can use this module I think it falls more under Integrations than Developer Tools.
Updating Issue Summary and moving to RTBC
- 🇺🇸United States leslieg
Agree with Performance. Would add Integrations as well. These are the two categories on the Drupal.org Project page.
Updating Issue Summary and moving to RTBC
- 🇺🇸United States leslieg
Agree with #4. Replace Media category currently selected on the project page with Site Structure
Updated Issue Summary and moving to RTBC
- 🇺🇸United States leslieg
Agree with #5 Content Display and Media. These are the places that target audience would most likely use to find this module
Updating Issue Summary and marking RTBC
- 🇺🇸United States leslieg
I agree with leaving the current category of e-commerce. I would keep just the core category. Integrations are more related to submodules. User Engagement is meant for interacting with others by using the site so I would not add that. Both good thoughts though.
Updating Issue Summary and moving to RTBC
- 🇺🇸United States leslieg
Uodated Issue Summary with proposed categories and moved to RTBC
- 🇺🇸United States leslieg
Agree with #5 to add Developers tools. I would suggest removing Site Structure and Content Display. Moving to RTBC
- 🇺🇸United States leslieg
Agree with keeping only Content Editing Experience. Moving to RTBC
- 🇺🇸United States leslieg
Agree with keeping category of Developer Tools. Moving to RTBC
- 🇺🇸United States leslieg
Agree with keeping two categories on the Drupal.org projec page- Content Editing Experience and Content Display. Recommend removing Developer Tools. Moving to RTBC
- 🇺🇸United States leslieg
Agree with Content Editing Experience and Media. Moving to RTBC
- 🇺🇸United States leslieg
Agree with the proposed category of Security. Moving to RTBC
- 🇺🇸United States leslieg
Agree with the current category of Performance. Moving to RTBC
- 🇺🇸United States leslieg
Agree with comments in #7. Those also match the categories currently selected on the project page. Moving to RTBC
- 🇺🇸United States leslieg
I agree with the current categories on Drupal.org - Access Control and Content Display. Moving to RTBC
- 🇺🇸United States leslieg
I feel the only category needed on this one is "Content Editing Experience". That's the main use of the module.
I don't think it meets the criteria for "Import and Export" (Help transfer content and data into or out of the site, by migration, backup, or exposing data to external systems). It also doesn't really fit under "Administratration tools" except that a site admin needs to enable the option
- 🇺🇸United States leslieg
Agree that those two new categories in #5 seem reasonable. Let's suggest all three and let the module maintainers decide. MOving to RTBC
- 🇺🇸United States leslieg
Also agree with #6. Still in Needs Review so moving to RTBC
- 🇺🇸United States leslieg
Still in Needs review. Agree with #6. Updating status to RTBC
- 🇺🇸United States leslieg
Agree with comments in #16. Moving to RTBC and removing two extra categories from Proposed Resolution