Agree with suggestion. Updating summary and moving to RTBC
Agree with suggestion. Updating summary and moving to RTBC
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
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
Agree with suggestions. Updating summary and moving to RTBC
Agree with suggestions. Updating summary and moving to RTBC
Agree with suggestions. Updating summary and moving to RTBC
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
Agree with Integrations. Updating summary and moving to RTBC
Agree with suggestions of Site Structure and Administration Tools
Moving to RTBC
Agree with suggestions. Updating summary and moving to RTBC
@chrisfromredfin suggested Administration tools
Agree with suggestions.. Updating summary and moving to RTBC
@chrisfromredfin suggested Integrations, content display, developer tools
Agree with the suggestions in #9
Updating summary and moving to RTBC
Agree with suggestions. Updating summary and moving to RTBC
@chrisfromredfin suggested Integrations, content display, developer tools
Agree with those 3 categories.
Updating summary and moving to RTBC
@chrisfromredfin suggested Integrations, content display, developer tools
Agree with Performance and adding Integrations.
Updating summary and moving to RTBC
Agree with Administration Tools.
Updating summary and moving to RTBC
Agree with #8 to use Automations and also Security fron #6 and #7
Updating summary and moving to RTBC
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.
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
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
Agree that this falls under Developer Tools. Doesn't really fit under Integrations or Decoupled. Updating summary and moving to RTBC
After discussing with Chris, we feel Integrations is the key category and also that Performance should be used. Updating summary and moving to RTBC
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
updated issue summary and moving to RTBC after discussing with @chrisfromredfin
Agree with Administration Tools. It doedn't fit into Import and Export or Integrations per the definitions.
Updating Issue Summary and moving to RTBC
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
Agree with Media. Marking this as RTBC
Agree with #11 also, Marking as RTBC
Closing this issue as it is not part of the Top 100. Maintainers will be given instructions for creating logos for their modules. Instructions will include adding log as logo.png in the root directory of their code
Moving to RTBC - Will include that note to the maintainer
Agree with Content Display. Moving to RTBC
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
Agree with #7. Moving to RTBC
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
Agree with #4. Replace Media category currently selected on the project page with Site Structure
Updated Issue Summary and moving to RTBC
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
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
Uodated Issue Summary with proposed categories and moved to RTBC
Agree with #5 to add Developers tools. I would suggest removing Site Structure and Content Display. Moving to RTBC
Agree with keeping only Content Editing Experience. Moving to RTBC
Agree with Developer Tools. Moving to RTBC
Agree with keeping category of Developer Tools. Moving to RTBC
Agree with keeping two categories on the Drupal.org projec page- Content Editing Experience and Content Display. Recommend removing Developer Tools. Moving to RTBC
Agree with Content Editing Experience and Media. Moving to RTBC
Agree with the proposed category of Security. Moving to RTBC
Agree with the current category of Performance. Moving to RTBC
Agree with comments in #7. Those also match the categories currently selected on the project page. Moving to RTBC
I agree with the current categories on Drupal.org - Access Control and Content Display. Moving to RTBC
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
Agree that those two new categories in #5 seem reasonable. Let's suggest all three and let the module maintainers decide. MOving to RTBC
Agree with #6. Moving to RTBC
Also agree with #6. Still in Needs Review so moving to RTBC
AGree with #6. Still in Needs review so moving to RTBC
Still in Needs review. Agree with #6. Updating status to RTBC
Agree with comments in #11. Moving to RTBC
Agree with comments in #16. Moving to RTBC and removing two extra categories from Proposed Resolution
The proposed logo in #6 does not meet the requirements for Project Browser:
- Create a logo that is 512x512 square dimension in PNG format without animations. Suggested file size should be 10k or less. Note: Please do not round the corners of the PNG itself unless there is some compelling branding reason. Corners are rounded automatically when displayed in the Project Browser.
- Use a lossy image tool (such as pngquant tool or the tinypng.com online service) to reduce file size while keeping the image quality at around 80%.
- Place the logo in the root directory of the Git repository for your project, on the default branch. The logo file should be named logo.png. The logo will appear on Drupal.org project pages, to the left of the project name. Logos are cached and may take up to an hour to show.
Removing the module name from the proposed description in #4 and updated the Summary to include this as the Proposed resoluiion.
"Transforms a Drupal website into a Progressive Web App (PWA), enhancing user experience with faster load times, offline access, and app-like functionality"
Note - This was the proposed resolution form #2 - The Progressive Web App (PWA) module turns a Drupal site into a PWA. It enables local caching and offline capabilities, and it makes the website installable on supporting mobile devices.
Closing this as duplicate of https://www.drupal.org/project/project_browser/issues/3303510 📌 File metadata manager - Add a short description Needs review which is already RTBC
This seems like a good combination of both suggestions: "Provides a widget on content entry forms for inline management (creation, modification, removal) of referenced content (entities)."
Note - this is the first suggestion- it was added only to the Proposed resolution in the summary which I have replaced with the most recent suggestion. "Offers a widget for managing related entities within a primary entity form. Ideal for parent-child relationships. Supports referencing existing entities.
Updated issue summary and moved to RTBC
seantwalsh → credited leslieg → .
seantwalsh → credited leslieg → .
seantwalsh → credited leslieg → .
Yes they currently need to be png format. The logo is used on the Drupal.org project page and on gitlab, in addition to Project Browser. The limitation currently comes from Gitlab.
In some cases svgs have been uploaded to the issues as well, but just for possible use in the future,
Agreee with recommendation in #5. Moving to RTBC
ChrisDarke → credited leslieg → .
"Some of the items on the right panel below do not yet exist. I imagine I should leave a placeholder."
@bernardm28. Which items in the right sidebar are you refering to?
@chrisfromredfin started work on this at DrupalCon Portland 2024 and will be continuing on that
closing as this is a duplicate of 3283034
Updated the issue summary to reflect the recent change to reduce the number of Categories from 55 down to 19.
Updated the issue summary to reflect the recent change to reduce the number of Categories from 55 down to 19.
Updated the issue summary to reflect the recent change to reduce the number of Categories from 55 down to 19.
Updated the issue summary to reflect the recent change to reduce the number of Categories from 55 down to 19.
Updated the issue summary to reflect the recent change to reduce the number of Categories from 55 down to 19.
Updated the issue summary to reflect the recent change to reduce the number of Categories from 55 down to 19.
Updated the issue summary to reflect the recent change to reduce the number of Categories from 55 down to 19.
Updated the issue summary to reflect the recent change to reduce the number of Categories from 55 down to 19.
Updated the issue summary to reflect the recent change to reduce the number of Categories from 55 down to 19.
Updated the issue summary to reflect the recent change to reduce the number of Categories from 55 down to 19.
Updated the issue summary to reflect the recent change to reduce the number of Categories from 55 down to 19.
Updated the issue summary to reflect the recent change to reduce the number of Categories from 55 down to 19.
Updated the issue summary to reflect the recent change to reduce the number of Categories from 55 down to 19.
Updated the issue summary to reflect the recent change to reduce the number of Categories from 55 down to 19.
Updated the issue summary to reflect the recent change to reduce the number of Categories from 55 down to 19.
Updated the issue summary to reflect the recent change to reduce the number of Categories from 55 down to 19.
Updated the issue summary to reflect the recent change to reduce the number of Categories from 55 down to 19.
Updated the issue summary to reflect the recent change to reduce the number of Categories from 55 down to 19.
Updated the issue summary to reflect the recent change to reduce the number of Categories from 55 down to 19.
Updated the issue summary to reflect the recent change to reduce the number of Categories from 55 down to 19.
Updated the issue summary to reflect the recent change to reduce the number of Categories from 55 down to 19.
Updated the issue summary to reflect the recent change to reduce the number of Categories from 55 down to 19.