Skip to content
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

Delete more icons #2872

Merged
merged 5 commits into from
Jan 27, 2019
Merged

Delete more icons #2872

merged 5 commits into from
Jan 27, 2019

Conversation

chris48s
Copy link
Member

These are more subjective, but I think switching to simple-icons for these 2 gives us something which is clearer by default on both main badge styles.

Scrutinizer

before:

after:

Superuser

before:

after:

@shields-ci
Copy link

shields-ci commented Jan 25, 2019

Warnings
⚠️

This PR modified helper functions in lib/ but not accompanying tests.
That's okay so long as it's refactoring existing code.

Messages
📖 ✨ Thanks for your contribution to Shields, @chris48s!

Generated by 🚫 dangerJS against 1544872

@chris48s chris48s mentioned this pull request Jan 25, 2019
3 tasks
@paulmelnikow
Copy link
Member

Again, appreciate your working through these!

Scrutinizer looks great 👍

The proportions on Superuser are way better post-change, however I like our two-color version. Do you have thoughts on under what circumstances we would keep a two-color logo?

@paulmelnikow paulmelnikow added the service-badge Accepted and actionable changes, features, and bugs label Jan 26, 2019
@chris48s
Copy link
Member Author

Its probably a bit of an unfair comparison. If I apply the same process as #2873 to the 2-colour version so it properly fills the viewbox, you get this:

My reason for proposing the switch is that I think the black on dark grey doesn't provide enough contrast, but I don't have deeply held views on it. As I say, these ones are pretty subjective. Happy to just update the 2-colour version one with this version if you prefer.

@paulmelnikow
Copy link
Member

It’s subjective for sure. The light one looks great, obvs. The dark one is borderline though I like it and think works okay.

Alternatively, we could make it display all blue on the dark background.

@paulmelnikow paulmelnikow temporarily deployed to shields-staging-pr-2872 January 27, 2019 16:47 Inactive
@chris48s
Copy link
Member Author

Lets go with the 2-colour one but scaled correctly.

we could make it display all blue on the dark background.

Looking at what logos are left, there are a few multi-colour logos where applying logoColor does something sensible-ish (this would be one of them), but mostly it doesn't. I think what we should probably do is try and make sure any multi-colour logos we hold in our own icon set look good on both of our default backgrounds, allow the logoColor param only if the logo defines a single fill="" attribute in the <svg tag (e.g: dependabot, discord) but just ignore logoColor if the logo uses >1 colours. That's another PR though..

@paulmelnikow paulmelnikow temporarily deployed to shields-staging-pr-2872 January 27, 2019 16:50 Inactive
@shields-deployment
Copy link

This pull request was merged to master branch. This change is now waiting for deployment, which will usually happen within a few days. Stay tuned by joining our #ops channel on Discord!

After deployment, changes are copied to gh-pages branch:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
service-badge Accepted and actionable changes, features, and bugs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants