-
Notifications
You must be signed in to change notification settings - Fork 52
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
Update Rams Color Scheme #290
Comments
I am currently investigating this and here is a comparison between the current colors in the nflverse and the "offical" team colors used in the nfl api. The latter provides only primary and secondary colors Currently nflverseOfficial in APIDifferences
|
I think I'd be in favor of changing all of these to update to the new version except Seahawks secondary |
I'm not sure how everyone else uses these, but I like the primary color to be dark enough to put white text on. NO's new gold would be pretty close and I changed the Raiders primary from silver to black in my own color set a while ago for that reason. JAX made a big PR thing about teal being their "primary color" in February, so I'm surprised they don't have that as one of their official colors. Personally, I think teal is more identifiable with the Jaguars than either black or gold. The teal I use is hexcode
I don't like white as a secondary color since I use white as my panel background usually, so I have been sticking to black as the Jets secondary and light grey as the Colts secondary. Only other significant change I have with the API is that I use Powder / Gold as the Chargers colors. Obviously do what you want with these, but I saw this and thought I'd share my approach! |
+1 for @guga31bb and @ajreinhard suggestions! |
I think |
I thought about this as @ajreinhard mentioned it but it would be very close to the Rams imo |
Yeah, but this way it's close to Titans too... That's why I said for some lighter blue... |
Yeah I agree. It's kinda impossible to make it perfect |
It looks like we should update the Rams colors
The text was updated successfully, but these errors were encountered: