I'm giving this a shot as part of MidCamp 2024:
Enables your site to search within file attachments. Think of it as giving your site the ability to read and search inside PDFs, documents, and more via a few extraction methods.
Thanks!
I like #6 📌 Create a short description for the Paragraphs Editor Enhancements project Needs review the best as it encompasses most of the functionality of the module.
I like the logo, but the file should be named logo.png as that is the requirement. Thanks!
The logo in #1 meets the requirements in terms of size, but the file should be named logo.png.
This logo can work, but one of the requirements is that the files is named logo.png.
Reviewing this as part of MidCamp 2024, #7 📌 Facets - Add a short description RTBC works and meets the criteria.
This can work and meets the criteria, but it would be great to have a few other options so that we have better representation.
For me #9 📌 File metadata manager - Add a short description Needs review works and meets the criteria.
I think #20 meets the criteria and uses the original logo used by the module maintainers, so I would assume they would want to use that instead of changing it.
Uploading new file patch, since I set the boolean value to a string previously. This is needed for 10.1.x
Adding patch file.
We also tested this and works as expected. We are also interested in a stable release asap. Thank you!
We tested this internally with a multi-value media filed and works as expected. Thank you!
Proposed resolution:
Twig Field Value module helps the frontenders to get partial data from Drupal field render arrays. It gives them more control over the output without using preprocess functions.
I would remove this part "It can be used to create single or multiple field values such as content." from the proposed resolution since there is no mention of that in the readme.md or the description of the module here Twig Field Value → .
I think #2 would be enough, not sure if icons fall under "media" as proposed by @brianbrarian though.
#6 is approved👍
Approved 👍!
I agree with #5, "utility" would be great to add.
#2 meets the criteria, but he also raises a good point, if this module should be included or be part of this initiative at all?
#2 seems correct to me as well.
#2 meets the required criteria, thank you @hebl.
I believe #4 makes sense to me as well. The maintainer states on his blog that it's for spam protection Introducing the Honeypot form spam protection module for Drupal
I agree with number #4 seems more future proof.
I personally like option3 with the blueish background gradient, but It's bigger than the requirements in size(KB) and 460*460 instead of 512*512.
The logo at #4 looks great and meets the required criteria.
Can one of the requirements be that logos stick to a certain color palette or a few colors approved by the community or maybe something that matches the Olivero theme or the default theme? I'm not a designer but it would be nice to have some consistency when looking at ll the logos. As of right now they are all over the place in term of colors/background/no background. Some designer input and guidance would be appreciated.
This looks good and meets the required criteria.
This looks good and mets the required criteria.
This looks good and meets the criteria.
I also like the GTM-logo-1 variant and I confirm that it's meets the criteria.
"Node Field" sounds better to me, since the initial comment.
We used this NodeField plugin and works as expected.👍