-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Logo Refresh Stage 2 #61
Comments
First drop of palette and subproject designs: Please let us know any feedback! |
Could we try a different set of logos for all of the subprojects? I'd be curious to see some other options. Fulcio: An arrow is unrelated to a certificate authority As discussed at the community meeting, it would also be good for Rekor and Fulcio to include a mention of a transparency log and certificate authority respectively. |
Regarding Concept 3 in the colour schemes, red-on-blue and blue-on-red are hard on the eyes. They can be quite hard to resolve if you have poorer eyesight. |
Depending on the shades of red and blue, these colors are frequently related to US politics. |
Worth adding we've requested some options for rekor and new logo for gitsign so far, can also ask for other options for the other subprojects. |
Perhaps rekor monitoring? |
Updated palettes and some new logo concepts for fulcio, with some notes from designer: Palette: I've worked in that that lighter blue, and I completely understand about the blue on red! In setting up the colour palette options, I was verifying everything through a colour contrast checker to make sure that we have plenty of combinations that pass the contrast requirements for accessibility and the blue/red combination does pass for larger text but it’s not a combination that we need to use by any means, or might pull out occasionally if something calls for a funkier effect for decorative purposes where legibility isn’t a concern 😊 Of course some of the project logos will be changing, but I’ve used them as examples of the coloured project logos anyway just to give an idea of different ways we can use the colours across a series of logos. I don’t recommend we make ’Sigstore’ match the length of the project name because each project’s name is a different length. That means that the size of ’Sigstore’ would change from project to project, and in places where the project logos are displayed together, it starts to look wonky and inconsistent. In case it’s just a size concern though, I’ve included a version where the Sigstore name is larger but still consistently sized for consideration 😊 |
For Fulcio: Concept 1: Reminds me of the @ sign, evocative of email. I don't think that's a good fit for a CA, since code signing certs can include a number of identities besides email. Concept 2: This logo is very similar to the GCP Certificate Authority Service logo, the one in blue that also uses a ribbon. Concept 3: I like the shield motif, but I would prefer just the shield rather than two shields intertwined. Maybe continuing to iterate on security-like objects in a shield? |
More input via sigstore slack thread: https://sigstore.slack.com/archives/C01DGF0G8U9/p1655845396863019 |
Updated palette with RGB numbers, accessibility usage (to be part of brand guidelines once logo refresh is complete) |
The palette guidance on whether a colour can be used in regular or large type is very helpful. |
Updated full set of logos with suggested subproject colours on the same page as the main Sigstore colours for reference. To be reviewed at community call on July 5th. Feedback welcome on this issue too. |
Feedback from community call: swap gitsign logo to green and avoid using red logos. |
The gitsign logo will be swapped to green. @lukehinds @bobcallaway @dlorenc please let me know any other feedback before we finalize the palettes & logos. |
Updated versions: |
much nicer! |
+1 from me. |
+1 |
+1, thanks! |
Closes sigstore#61 Closes sigstore#67 Signed-off-by: Tracy Miranda <tracy@chainguard.dev>
Following on from the logo refresh work done in #55 this issue tracks the follow up work, which is:
The text was updated successfully, but these errors were encountered: