[Meta] Twig Field Value Project updates for Project Browser

Problem/Motivation

The Project Browser Initiative is working on a new Browse page for the Extend functionality. The default display of the Project Browser will include the most popular Drupal modules for the version of Drupal the site is using. A card will be displayed for each of the modules (projects). Three key components displayed on the card will include a logo, a short description and the top categories this module belongs to.

https://www.drupal.org/project/twig_field_value →

How to work on a child issue

1. Search the project_browser issue queue → for issues tagged with "Project Browser Top 100"
2. Open the Top 100 Module google spreadsheet and check columns in columns D-F to see what others have already found related to the project you are working on.
3. Determine which of the child issues you are working on and follow the steps below:

Logo

1. Write a comment on the child issue that you are working on one of these steps
2. Design a logo for the module via consensus.
3. Create a logo that is 512x512 square dimension in PNG format without animations. Suggested file size should be 10k or less. Use a lossy image tool (such as pngquant) to reduce file size while keeping the image quality at around 80%.
4. Upload the logo to the child issue, embed the logo and add your thoughts to anything already added by other contributors in the Proposed resolution section of the issue summary
   • Change the issue status to "Needs review"

Short description

1. Write a comment on the child issue that you are working on one of these steps
2. Review the "Short description meets needs" cell for the project in the spreadsheet. There should be a comment on that cell describing what the issue is.
3. Come to a consensus about updating the short description. The short description should answer the question - what does this module do in a non-technical way.
4. Write a new short description (200 characters or less) and add your thoughts to anything already added by other contributors in the Proposed resolution section of the issue summary.
   • Change the issue Status to "Needs review"

Categories

1. Write a comment on the child issue that you are working on one of these steps
2. Review the current categories for the project and come to a consensus on new categories. If the category doesn't exist, suggest adding it.
3. List the top 1-3 proposed categories that the project should have and add your thoughts to anything already added by other contributors in the Proposed resolution section of the issue summary.
   • Change the issue status to "Needs review"