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 Clientside Validation 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/2024-07-04/jQuery-UI-Selectable-fs8.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’s default branch. If you have a logo as the first image in the Images field 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

  1. Review any logos on this ticket.
  2. Provide design feedback if applicable.
  3. If multiple logos are provided, choose your preferred one.
  4. 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
CommentFileSizeAuthor
#8 client-validation3.png2.86 KBsourojeetpaul
#8 client-validation2.png3.97 KBsourojeetpaul
#8 client-validation1.png4.6 KBsourojeetpaul
#4 client-validation.png4.82 KBsourojeetpaul

Issue fork clientside_validation-3459445

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

Kristen Pol created an issue. See original summary.

kristen pol’s picture

kristen pol
she/her
Primary language English
Location Santa Cruz, CA, USA
commented
Title: Create logo for Clientside Validation for Project Browser Initiative » Project Browser: Create a logo for Clientside Validation
Project: Project Browser » Clientside Validation
Version: 1.0.x-dev » 4.0.x-dev
Component: Contrib changes » User interface
Issue summary: View changes
Issue tags: -Project Browser Initiative +Project Browser Logo
Parent issue: #3342533: [Meta] Create a logo for a contrib module »

Move to project's queue per @leslieg.

sourojeetpaul’s picture

sourojeetpaul commented
Assigned: Unassigned » sourojeetpaul

I'm picking this up!

sourojeetpaul’s picture

sourojeetpaul commented
Assigned: sourojeetpaul » Unassigned
Status: Active » Needs review
StatusFileSize
new client-validation.png4.82 KB

It was a bit tricky to showcase the functionality visually. This is what I came up with after a lot of brainstorming. Pls have a look...

kristen pol’s picture

kristen pol
she/her
Primary language English
Location Santa Cruz, CA, USA
commented
Status: Needs review » Needs work

Thanks! I don’t think it needs the person in it and it would be good if it looked more like a form

sourojeetpaul’s picture

sourojeetpaul commented
Status: Needs work » Needs review

Just one question Kristen,
If we remove the person from the logo then how we're going to decipher the 'clienside' aspect of the validation?
Any thoughts on that?!

kristen pol’s picture

kristen pol
she/her
Primary language English
Location Santa Cruz, CA, USA
commented

I see. I guess it’s fine to keep it. Just looks more cluttered IMO. We don’t have a “server side validation” module so I’m not sure it’s really necessary though. Perhaps have both versions and the maintainer can decide?

sourojeetpaul’s picture

sourojeetpaul commented
StatusFileSize
new client-validation1.png4.6 KB
new client-validation2.png3.97 KB
new client-validation3.png2.86 KB

Ok @kristen pol,
I'm sharing 3 variants for the maintainer to choose from...

manojsaha’s picture

manojsaha commented
Status: Needs review » Reviewed & tested by the community

Hello @sourojeetpaul
I like the first version among all the logos because it follows the proper guidelines for the requirements of Drupal module logo design. On the other hand, anyone can clearly understand that the form is for the client's side. So, I think this is one can be a good option.
I am moving the issue to RTBC++.

nikunjkotecha made their first commit to this issue’s fork.

nikunjkotecha opened merge request !27

nikunjkotecha’s picture

nikunjkotecha
he/him
Primary language Gujarati
Location India, Gujarat, Rajkot
commented
Status: Reviewed & tested by the community » Needs review

Thanks everyone for the great work, can someone please help review and approve the MR https://git.drupalcode.org/project/clientside_validation/-/merge_request... ?

I have lost touch with Drupal projects so not really sure MR is exactly as per requirement or we need something else?

sourojeetpaul’s picture

sourojeetpaul commented

Hi @nikunjkotecha,
Thanks for taking your time out and having a look at this! AFAIK for PB logo issues an MR with the logo.png is enough! I believe we're good to go now :)

nikunjkotecha’s picture

nikunjkotecha
he/him
Primary language Gujarati
Location India, Gujarat, Rajkot
commented

  • nikunjkotecha committed e0e54be1 on 4.0.x 
    Issue #3459445 by nikunjkotecha, sourojeetpaul, kristen pol, manojsaha:...
nikunjkotecha’s picture

nikunjkotecha
he/him
Primary language Gujarati
Location India, Gujarat, Rajkot
commented
Status: Needs review » Fixed

Thanks, MR merged, will release new version soon.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.