Problem/Motivation
The Project Browser Initiative wants nice project logos for better UX. The logo will be displayed on the card for your module in the Project Browser (as well as on drupalcode.org as your project avatar, and on drupal.org on your project page).
The Entity Usage module needs a logo for this objective.
Proposed resolution
- Create a logo that is 512x512 square dimension in PNG format without animations.
- The file size should be 10k or less.
- Use a lossy image tool (such as pngquant) to reduce the file size while keeping the image quality at around 80%.
Examples:
https://www.drupal.org/files/issues/2022-11-11/jqueryui_datepicker_min.png
https://www.drupal.org/files/issues/2023-05-03/Embed-Project-Logo.png
https://www.drupal.org/files/issues/2022-04-28/pathauto-fs8.png
https://www.drupal.org/files/issues/2022-09-23/search_api.png
https://www.drupal.org/files/issues/2022-09-23/Rest%20UI.png
https://www.drupal.org/files/issues/2023-08-16/entity_queue_3.png
https://www.drupal.org/files/issues/2022-10-04/views_slideshow_logo_1.png
https://www.drupal.org/files/issues/2022-09-30/redis-project-browser-cub...
https://www.drupal.org/files/issues/2022-09-23/DropzoneJS_v2-min.png
https://www.drupal.org/files/issues/2023-08-14/File_Metadata_Manager_2.png
MAINTAINERS: Once a logo is reviewed and approved, it should be added to the root folder of your project's repo, and be named
logo.png. This must be present on your project’sdefault branch. If you have a logo as the first image in theImagesfield on your project page, please remove it. The logo will be displayed on the cards in the Project Browser grid and list views.
Review steps
- Review any logos on this ticket.
- Provide design feedback if applicable.
- If multiple logos are provided, choose your preferred one.
- Ensure logo meet the requirements:
- 512px by 512px square
- PNG format
- no animations
- 10k file size or less
- reasonable image quality
- visually represents the project
| Comment | File | Size | Author |
|---|---|---|---|
| #22 | earrow-fs8.png | 3.83 KB | AaronDeutsch |
| #20 | entityicon-fs8.png | 6.68 KB | AaronDeutsch |
| #18 | Entity-Usage2.png | 5.91 KB | sourojeetpaul |
| #18 | Entity-Usage1 (1).png | 4.05 KB | sourojeetpaul |
| #16 | Entity-Usage1.png | 6.56 KB | sourojeetpaul |
Comments
Comment #2
kristen polMoving to project's queue per @leslieg.
Comment #3
marcoscanoThanks for filing this in! I am +1 with this idea, however I have 0 skills in designing or producing a logo. If anyone wants to contribute, I will gladly add it to the repo.
Thanks!
Comment #4
kristen polCool 😎 I’ll check with my team
Comment #5
AaronDeutschhello! this is a design I made for this. The two blocks represent the entities and the lines in between them represents their relationship. Let me know if there is anything I need to change!
Comment #6
kristen polI like it 👍 I guess it doesn’t convey the “usage” part though… thoughts?
Comment #7
marcoscanoThank you for working on this! 🙏
I agree it would be ideal to have a visual representation of the "hierarchy" that the relationship represents: there is always a "source" entity and a "target" entity, these relationships are not bi-directional. In other words, this module tracks "what entity (or entities) is this entity pointing to". Do you think it's possible to iterate and try to capture that?
Thanks again!
Comment #8
AaronDeutschThanks for explaining it to me better! I made some changes that I think improve the design. Let me know what you think! I'm open to tweaking it more
Comment #9
kristen polThanks! Seems like an improvement. I wonder if there should be an arrowhead on one end?
Comment #10
marcoscanoThank you for working on this!
I agree with this, if we could make the line an arrow, it may be more explicit the source->target hierarchy?
Thanks!
Comment #11
sourojeetpaul commentedHi @AaronDeutsch,
I would echo with @Kristen Pol's comment here! As @marcoscano mentioned, we're not talking about bi-directional relationships in this module, so it' would be great if we use an arrow with a proper demarcation of source and target entity. Also I didn't get any visual clue about the "usage" part from the logo!
Hence moving it to NW for further improvement.
Comment #12
kristen polThanks. I’ll ping Aaron so he can update with the arrowhead… I’m not sure how to indicate the usage though so open to ideas
Comment #13
sourojeetpaul commentedHi @Kristen Pol,
Updating arrowhead seems pretty straight forward, but incorporating the idea of "Usage" is indeed bit tricky.
We might need to modify the whole logo here then. I'll brainstorm more on this Monday.
Comment #14
AaronDeutschHere it is with an arrow
Comment #15
kristen polThanks. The size is a little too big
Comment #16
sourojeetpaul commentedHi @Kristen Pol,
I've made my own version my taking inspiration from the above one. Tried to incorporate the concept of "Usage" part. Pls have a look!
Comment #17
kristen polThanks. This may not show up well in project browser due to the small details. I’ll see if Aaron can reduce the size on his and the maintainer can pick
Comment #18
sourojeetpaul commentedHi @Kristen Pol,
I've made two other variants as well yesterday. Pls have a look if that meet the requirements, though I preferred the uploaded one:)
Comment #19
kristen polThanks. Those are better than your first one IMO. I’ll ping Aaron again just to have another option
Comment #20
AaronDeutschI tried simplifying it a bit because I think the main icon gets the point across without being too cluttered. It's my understanding that these icons are mostly going to be viewed from far away, so making them more recognisable and clear seems important. Just putting this here as another option
Comment #21
kristen polI just wanted #14 but the file size fixed :)
Comment #22
AaronDeutschmy apologies. here it is
Comment #23
kristen polThanks 🙏 now there are 4 to choose from 😆
Comment #25
marcoscanoThank you all! I picked the last one and added it to the repo 👍
Comment #26
kristen polThanks 🙏
Comment #27
sourojeetpaul commentedThanks :)