Template talk:Gridiron primary color

Latest comment: 6 years ago by Ahecht in topic Module ready for testing

Changing Seahawks colors to enhance contrast

edit

Per the lengthy discussion on the NFLactive Infobox talk page, I am changing the colors used for the Seattle Seahawks to increase the contrast. The current colors are bright green on a dark navy background which is difficult to read, more so for those with colorblindness issues (such as me).
The team has four team colors (per the franchise page), Seahawks blue, dark navy, bright green and white and it seems that the two least contrasting were chosen for this purpose. Obviously to maximize contrast one of the choices should be white. For the contrasting color I'm chosing Seahawks blue, since that color is most representative of the team, IMHO. Please air concerns here before reverting this change.--Deejayk (talk) 03:28, 12 March 2009 (UTC)Reply

Vintage Buccaneers colors

edit

Would there be any objection to my adding the Tampa Bay Buccaneers' original colors to the template, to be used in articles covering the years 1976-1996? Just as the modern team has changed colors and distanced itself from the earlier editions of the team, it feels wrong to have the modern colors applied to those early lineups. GuySperanza (talk) 15:52, 17 August 2009 (UTC)Reply

Accessibility problems

edit

As I mentioned on my comment here[1] on WT:NFL#NFL color templates, many of the color combination generated by this template fail WP:COLORS: color combinations should have adequate contrasts so the text can be readable against whatever background it is printed on. Zzyzx11 (talk) 07:33, 29 December 2009 (UTC)Reply

Change the Seahawks blue from #03202f to #002244 as specified in their media guide.

edit

Please change the current color for the Seahawks.

The Seahawks specify the hex value of the blue they use in the media guide: http://www.seahawksmedia.com/images/Seattle-2012-logo-Slick.pdf

From:

|Seattle Seahawks =background: #03202f

To:

|Seattle Seahawks =background: #002244

HappyMonkeyPaul (talk) 00:47, 28 April 2013 (UTC)Reply

  Done :) ·Salvidrim!·  03:44, 29 April 2013 (UTC)Reply

Implementation of multiple color schemes

edit

I don't really like the way that teams with multiple color schemes are addressed in this and similar templates. Currently to use an old color scheme one has to look at the code of the template and determine the correct team name to use, as in this example snippet:

|Denver Broncos =background: #FB4F14
|Denver Broncos 97thru11 =background: #002244
|Denver Broncos 62thru96 =background: #F9461C
|Denver Broncos 60thru61 =background: #332B2A

The solution I would propose would be to implement an optional year parameter that could then be used as follows:

|Denver Broncos =
 {{#if: {{{year|}}} | 
  {{#ifexpr: {{{year}}} >= 2012
   |background: #FB4F14
   |{{#ifexpr: {{{year}}} >= 1997
    |background: #002244
    |{{#ifexpr: {{{year}}} >= 1960
     |background: #332B2A
     |background: #FB4F14
     }}
    }}
   }}
  |background: #FB4F14
 }}
|Denver Broncos 97thru11 =background: #002244
|Denver Broncos 62thru96 =background: #F9461C
|Denver Broncos 60thru61 =background: #332B2A

What this code does is use the year parameter to identify the appropriate color scheme. The way it is written it is fully backwards-compatible so that it would not have any impact on any page that currently use this template. However, it would simplify the implementation of the color schemes going forward. Any thoughts? — DeeJayK (talk) 16:53, 14 November 2013 (UTC)Reply

good idea, but we should do a bit of testing first to make sure the added complexity doesn't break anything. if necessary, we can also consider either (a) splitting the template using a string match with the first letter and/or (b) rewriting it in WP:LUA. this is what was done with Module:Portal, due to the massive number of entries. Frietjes (talk) 19:53, 14 November 2013 (UTC)Reply
I agree that we'd definitely want to do some sandbox testing before we implement something like this. I'm not sure I understand what you mean by "splitting the template using a string match." Can you elaborate or give me an example of an implementation of this approach? Thanks. — DeeJayK (talk) 20:50, 14 November 2013 (UTC)Reply
basically, you do a {{str left|team name|1}}, which returns the first letter, then call a subtemplate (or submodule) with the teams with names that start with that letter. this approach will only win if the switch is very long, with many team names. you get a performance improvement by splitting the large switch statement into 26 shorter switches, but a performance penalty from the initial 'str left' operation. this is how module:portal works. it first extracts the first letter of the portal name, then loads a data table corresponding to all portals which start with that letter. this level of additional complexity may not be necessary here. I don't know the technical limit. hopefully this will only be called a few times per page. Frietjes (talk) 22:49, 14 November 2013 (UTC)Reply
Thanks for the explanation. It doesn't appear to me that such an approach is going to be necessary for this template at this point in time. (Although it may be in the future if the scope continues to expand — it's gone WELL beyond the original NFL teams now.) I've gone ahead and implemented a test of my approach described above in {{NFLPrimaryColor/sandbox}}. I've begun testing and would welcome anyone else to take a look as well. Feel free to use the sandbox testcases. — DeeJayK (talk) 23:06, 15 November 2013 (UTC)Reply
Update: I've implemented similar changes to add a year parameter for the {{NFLSecondaryColorRaw}} template at {{NFLSecondaryColorRaw/sandbox}}. I'm planning on doing the same for the other similar templates for which this approach would apply and then will create test cases and perform testing for the whole ecosystem once it is completely sandboxed. — DeeJayK (talk) 21:55, 18 November 2013 (UTC)Reply
Update: I've now implemented similar changes in {{NFLTertiaryColorRaw}} and {{NFLPrimaryStyle}} and am testing. I have also posted a request for comment on the changes on the NFL WikiProject talk page. — DeeJayK (talk) 20:14, 19 November 2013 (UTC)Reply
we can deprecate the old syntax, and a tracking template to track the deprecated uses. thank you for the update. Frietjes (talk) 18:10, 22 November 2013 (UTC)Reply
Thanks for your input and thanks for looking over and cleaning up my changes. I've now moved my changes out of the sandboxes for ALL of the templates. Now, I'll work on updating the documentation and extending these changes to the other templates that use these. — DeeJayK (talk) 18:56, 22 November 2013 (UTC)Reply

Change Buccaneers Color to New Red

edit

The Red is #D60A0B, as found in new logo--Jack Cox (talk) 04:53, 21 February 2014 (UTC)Reply

Cleveland Browns brown appears too dark

edit

The template is using #312821, however it does not match the uniform graphics on the page nor the definition of seal brown on Wikipedia. This document http://moncpc.files.wordpress.com/2010/02/nationalfootballleague_frc_2000_sol_srgb.pdf says it should be #332b2a. A color picker used on the Browns website http://clevelandbrowns.com has #3F230D for the brown value. At any rate, the color being used looks way too much like the black of the Bengals which is an issue. Thanks. LightningMan (talk) 17:55, 13 May 2014 (UTC)Reply

HELP! COLORS!

edit

I am at my wits end...everything I try to fix the Los Angeles Rams colors fails. I got the colors to be correct for 1964-1972 and 1973-1994, but then it kills 1946-1963. When I try to fix 1946-1963, it has ranged from killing the entire color template to killing 1964-1994 for the Rams. So PLEASE, PLEASE, PLEASE, if someone could fix the colors for me it could be greatly appreciated.

1946-1963

Primary/Background
#F5D015
#F5D015

Secondary/Font Color
#183990
#183990

Tertiary/Outline
#183990
#183990









1964-1972

Primary/Background
#183990
#183990

Secondary/Font Color
white
white

Tertiary/Outline
white
white









1973-1994

Primary/Background
#183990
#183990

Secondary/Font Color
#F5D015
#F5D015

Tertiary/Outline
#F5D015
#F5D015









Thank you! --CASportsFan (talk) 22:22, 7 February 2015 (UTC)Reply

Washington Redskins colors

edit

The NFL logo slick at NFLCommunications.com (registration required) shows #660000, another user thinks it should be #773141 per this website. An open dropbox should not be a reliable source simply because we don't where it came from. The Redskins do not have a logo slick on their website, but simply at the NFL's communication website. It is pretty obvious that by looking at redskins.com that it is #660000, which is darker than #773141. The date on the public dropbox is "03.28.12", the one at NFLCommunications is "12.17.12". If someone wants to verify it, it is pretty simple to gain access to the website. If you look up the RGB codes (both the same on each slick), it is closer to #66000. Simply, the colors should be #660000 from the official logo slick at an official NFL website, not #773141 which is not an official website. Corkythehornetfan 10:23, 19 July 2016 (UTC)Reply

  • If you need to have a closed registration in order to source something, I don't think you are able to use that as a source. And I already told you that the dropbox is just a repository of stuff that the teams used to host on their own websites, as can be proven with this. If you are able to find a secondary source that states the Redskins officially use #660000, then that's great, but I don't think we should change it until then. And your last sentence is WP:OR; we need a direct source of what colors they use, not comparing them by eye. Pinging @Charlesaaronthompson:, who changed the color to the current one some months back, for their opinion. ~ Dissident93 (talk) 10:48, 19 July 2016 (UTC)Reply
    • Since I was pinged by Dissident93 (talk), I will provide my response here: I will agree with Corkythehornetfan (talk) that an open dropbox should not be used as a reliable source. I take full responsibility for any and all confusion regarding the open dropbox sourcing. Since Corkythehornetfan has access to the logo slicks at NFLCommunications.com, I think the HTML color code he provided ( #660000 ) should be used instead, since that is official color information, even though there is no URL source available (see User talk:Corkythehornetfan#NFL Communications for a broader discussion on the topic). Charlesaaronthompson (talk) 20:23, 19 July 2016 (UTC)Reply

Template-protected edit request on 12 January 2017

edit

I would like to change the formatting for the now-Los Angeles Chargers to reflect the team's decision to move from San Diego to Los Angeles for the 2017 NFL season. Charlesaaronthompson (talk) 17:54, 12 January 2017 (UTC)Reply

  Not done: please make your requested changes to the template's sandbox first; see WP:TESTCASES. — JJMC89(T·C) 18:27, 12 January 2017 (UTC)Reply
  Partly done: Chargers color fixed. As for the rest, there's a lot going on in that sandbox diff! This would be an additional −7312 byte change, with many teams removed. Was that intentional? Matt Fitzpatrick (talk) 14:11, 15 January 2017 (UTC)Reply
@Matt Fitzpatrick: Yes, that was intentional. If I became a template editor, I would propose to make these changes at the main template. Speaking of which, how do I become a template editor? Also, would you mind making these changes for me? Charlesaaronthompson (talk) 15:11, 15 January 2017 (UTC)Reply
Charlesaaronthompson, what was the purpose of removing/modifying that huge amount of text? Removing text seems like it would break a few things. Primefac (talk) 15:36, 15 January 2017 (UTC)Reply
Primefac Sorry, I must not have taken into account that the sandbox isn't as accurately updated as the regular template. I just wanted to restore the removed formatting for the Green Bay Packers, Chargers, and the Los Angeles Rams. That was my purpose. Yes, you're right: removing text does seem like it would break a few things. That part was not my intention. My intention is to have the template be as accurate as possible. Charlesaaronthompson (talk) 15:47, 15 January 2017 (UTC)Reply
Ah, no worries then. Something to think about in the future is to "reset" the sandbox with the current version in the main template before proposing any changes. That way your actual "here's what to change" is more obvious. As for getting TE rights - info is here (looks like you meet the reqs) and the request page is here. Happy to answer any questions relating to TE (probably not here, though, to avoid hijacking the conversation). Primefac (talk) 15:53, 15 January 2017 (UTC)Reply
Alternatively, maybe it's a good idea to split the template like {{NFLSecondaryColor}} and {{NFLSecondaryColorRaw}}, where the latter has a lower protection level? Then (almost) anyone could edit "NFLPrimaryColorRaw" as needed. Could be handy, since there's an ongoing need to update, at least as often as any team changes cities, names, or colors, and that need may outweigh the template's high-ish usage at this point. (Pinging George Ho who requested protection for this template last month.) Matt Fitzpatrick (talk) 16:13, 15 January 2017 (UTC)Reply
True, the template is highly used. However, I'm pinging Hut 8.5 about this, though he's less active at the moment. If that person doesn't respond for about one week (how about?) soon, either I or someone else must request lowering protection to ECP (different from semi-protection) instead at WP:RPP. George Ho (talk) 19:38, 15 January 2017 (UTC)Reply
I'm a little nervous about lowering the protection level as it has pretty high usage (32864 transclusions at the moment) and many of those are on fairly high profile articles. How frequently is this likely to need updates? It might be worth bringing in another admin who's more familiar with the subject matter. Hut 8.5 07:36, 16 January 2017 (UTC)Reply
Just as a note, I did a split version with the current version of the sandbox and {{NFLPrimaryColorRaw}}. Matt Fitzpatrick (talk) 10:40, 16 January 2017 (UTC)Reply
Meanwhile, I'll support the splitting. George Ho (talk) 08:30, 17 January 2017 (UTC)Reply

Per Hut's advice, I'm pinging BU Rob13 about this. I saw his name at the WikiProject NFL page. George Ho (talk) 08:10, 17 January 2017 (UTC)Reply

Definite no from me. Our NFL articles are heavily vandalized including by a few sockmasters. Opening up a template used on all NFL biographies would be very risky. ~ Rob13Talk 16:06, 17 January 2017 (UTC)Reply
For the record, this template has only been fully protected since last month. And in the many years before that, it doesn't look like its ever been vandalized. WikiOriginal-9 (talk) 18:37, 17 January 2017 (UTC)Reply
That may be, but I've noticed a lot more highly-count temples being protected lately (and 35k uses certainly qualifies as "high visibility"). Primefac (talk) 18:41, 17 January 2017 (UTC)Reply

Possibility (or politics) of risk aside, what about the splitting proposal by CharlesAaronThompson, shown in the sandbox? Pinging Rob and Hut—it's not about accessibility, editing, risk, and all that. George Ho (talk) 02:18, 18 January 2017 (UTC)Reply

The split template would be transcluded on just as many pages, so it would be protected too. ~ Rob13Talk 02:20, 18 January 2017 (UTC)Reply
Oh... That, Rob (shall I re-ping you?).... and I also meant whether you approve the proposal shown in the sandbox. George Ho (talk) 02:23, 18 January 2017 (UTC)Reply
I haven't reviewed it and don't really plan to. Not too interested in splitting one template into two when one is doing the job, though. ~ Rob13Talk 03:17, 18 January 2017 (UTC)Reply
I have no opinion about the split, I'm only paying attention to this because I was the one who protected the template. Hut 8.5 07:42, 18 January 2017 (UTC)Reply
  • This might be a solution looking for a problem. DMC511 and CharlesAaronThompson have constructively edited this template for years. Charles could have fixed the Chargers colors quickly but we had to wait and they were incorrect for days. WP:IAR on the number of transclusions because this page has never been vandalized. It's too hidden for vandals to find. And we don't protect pages just to protect them. See WP:PREEMPTIVE. Semi-protection is usually good enough for most things. WikiOriginal-9 (talk) 03:37, 18 January 2017 (UTC)Reply
Wizardman and Cbl62, your thoughts? George Ho (talk) 04:08, 18 January 2017 (UTC)Reply
Actually, WP:PREEMPTIVE refers to full protection. Other similar text is in every section of the protection policy except template protection, and that is intentional. Template protection is commonly used to pre-emptively protect high-risk templates. That's its only intended use case, actually. See also WP:HIGHRISK, a guideline. As an aside, WikiOriginal-9, I would absolutely seriously consider requests for the template editor user right from non-technical editors who wish to use it exclusively to edit this template. See WP:PERM/TE. Barring unusual circumstances specific to the editor, I would likely grant such requests, as would other admins, I believe. ~ Rob13Talk 04:45, 18 January 2017 (UTC)Reply
Yes, the general prohibition on pre-emptive protection doesn't apply to protection of high risk templates, and with good reason. The potential damage if this template gets vandalised is enormous - 30,000 pages would be vandalised at once. Nor are these obscure pages, as it looks like most NFL-related player and team articles would be affected. This vandalism would likely reach an enormous number of readers. While the average Wikipedia vandal isn't sufficiently technically sophisticated to do this, the cleverer and more devious ones are, and it does happen. These people would also find it extremely easy to get past semi-protection - all you have to do is register an account, wait four days and make ten edits (any edit will do). The template does need to be protected and it needs more than mere semi-protection with that number of transclusions. Hut 8.5 07:57, 18 January 2017 (UTC)Reply

The protection itself aside, I'm pinging Stanton about the split proposal, i.e. making changes as shown in the sandbox counterpart. If you approve, Stanton, can you change it? George Ho (talk) 19:52, 18 January 2017 (UTC); Re-pinging @SMcCandlish:. 18:02, 23 January 2017 (UTC)Reply

Template-protected edit request on 25 January 2017

edit

Please add the Baltimore Brigade DMC511 16:59, 25 January 2017 (UTC)

  Not done: it's not clear what changes you want to be made. Please mention the specific changes in a "change X to Y" format. — JJMC89(T·C) 20:47, 25 January 2017 (UTC)Reply
Please add the Baltimore Brigade using |Baltimore Brigade =background: #202946 DMC511 DMC511 03:26, 31 January 2017 (UTC)Reply
  Not done: please provide reliable sources that support the change you want to be made. See also comments at Template talk:NFLTertiaryColorRaw. StevenJ81 (talk) 23:26, 31 January 2017 (UTC)Reply
This source states that the colors are Blue and Dark Blue.DMC511 (talk) 23:34, 31 January 2017 (UTC)Reply
  Not done for now: Are you making up the actual colors for now, or do you have a source? The website only names the colors, it doesn't specify them. If what you're doing is trying to do your best to match the pictures there, at least say so. StevenJ81 (talk) 23:48, 31 January 2017 (UTC)Reply
Yes, he is just guessing because it would be pretty hard to find the official hex codes for these indoor football teams. They're not easily available like the NFL teams. WikiOriginal-9 (talk) 03:05, 1 February 2017 (UTC)Reply
Co-signed. Until official "actual colors" come out (with Hex codes), please don't make this more difficult than it has to be. Even slightly inaccurate colors are better than grey-on-black-on-white. Tom Danson (talk) 20:45, 15 February 2017 (UTC)Reply
  Done Fair enough. Marked inside that it's a guess for now, but that's ok. StevenJ81 (talk) 21:15, 15 February 2017 (UTC)Reply

Template-protected edit request on 28 January 2017

edit

I would like to update the historical colors for the Denver Broncos in order to ensure that they meet color contrast guidelines. Charlesaaronthompson (talk) 18:22, 28 January 2017 (UTC)Reply

  Not done: it's not clear what changes you want to be made. Please mention the specific changes in a "change X to Y" format. — JJMC89(T·C) 19:01, 28 January 2017 (UTC)Reply
@JJMC89: This edit diff is what I'm proposing be changed for the Denver Broncos at Template:NFLPrimaryColor. Charlesaaronthompson (talk) 19:21, 28 January 2017 (UTC)Reply
  Done — JJMC89(T·C) 19:38, 28 January 2017 (UTC)Reply
@JJMC89: Could you change one more thing for me, please? Change the field for Denver Broncos 62thru96 to Denver Broncos 62thru67? Charlesaaronthompson (talk) 20:30, 28 January 2017 (UTC)Reply
@Charlesaaronthompson:   Done The same should probably be done at {{NFLPrimaryColorRaw}} to keep them consistent. — JJMC89(T·C) 22:15, 28 January 2017 (UTC)Reply

Template-protected edit request on 25 February 2017

edit

I would like to change the San Diego Chargers' historical colors from 1974 to 1987. Specifically, I would like to change the HTML color code from  #00338D  to  #003087 . Charlesaaronthompson (talk) 08:33, 25 February 2017 (UTC)Reply

  Not done: please provide reliable sources that support the change you want to be made. — Train2104 (t • c) 14:50, 25 February 2017 (UTC)Reply

Concordia

edit

Update Concordia's primary colour, following rebranding: HTML colour code from  #800000  to  #812A3A  as per website.[1] Cmm3 (talk) 22:56, 26 February 2017 (UTC)Reply

References

  Done StevenJ81 (talk) 17:27, 27 February 2017 (UTC)Reply

Template-protected edit request on 29 March 2017

edit

Correct the Montreal Alouettes' primary colour: HTML colour code from  #1A5484  to  #003A70  as per team's website and logo.[1] Also refer to ColorWerx for year of change and colour code.[2]

Thanks. Cmm3 (talk) 15:52, 29 March 2017 (UTC)Reply

  Done I've updated all 3 instances of the color in the Alouettes' field. If there's anything historical that should be changed back, please reopen this editreq. – Train2104 (t • c) 14:19, 30 March 2017 (UTC)Reply
Nope, that's perfect, thanks. Cmm3 (talk) 15:01, 31 March 2017 (UTC)Reply

Template-protected edit request on 21 April 2017

edit

I would like to edit the string of values for the Detroit Lions so it looks like this: Charlesaaronthompson (talk) 03:18, 21 April 2017 (UTC)Reply

  Not done: Incomplete request. — JJMC89(T·C) 04:24, 21 April 2017 (UTC)Reply
@JJMC89: Here's what I want done. The coding is similar to the Green Bay Packers, but it differs like this:
  • Detroit Lions 2017:  #0076B6 
  • Detroit Lions 2012 thru 2016:  #005A8B 
  • Detroit Lions 2009 thru 2011:  #0066CC 
  • Detroit Lions 2003 thru 2008:  #0066CC 
  • Detroit Lions 1970 thru 2002:  #2A6EBB 
  • Detroit Lions 1934 thru 1969:  #005EB8 
I can't exactly paste the HTML coding here, but I hope you get the idea of what I want done. The coding is similar to the Green Bay Packers coding (there's 6 values). Just look at Template:NFLPrimaryColor to see what I mean. Also, here's the diff of how I changed the Green Bay Packers' color formatting, for a reference. What I'm proposing is similar, but for the Detroit Lions. Charlesaaronthompson (talk) 04:49, 21 April 2017 (UTC)Reply
  Done I the future you can edit the sandbox and request that it be synced. — JJMC89(T·C) 04:10, 22 April 2017 (UTC)Reply
Could you sync Template:NFLPrimaryColor using this diff? Charlesaaronthompson (talk) 07:20, 23 April 2017 (UTC)Reply

Template-protected edit request on 11 July 2017

edit

I would like to change Template:NFLPrimaryColor, per my edit diff. Charlesaaronthompson (talk) 23:53, 11 July 2017 (UTC)Reply

Needs testcases for each of the ranges in the two changed parameters. Happy to implement it when we're certain it works.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  02:03, 16 July 2017 (UTC)Reply
  Done Corkythehornetfan (ping me) 23:47, 22 July 2017 (UTC)Reply
Something isn't quite right. I can't figure out what tho.DMC511 (talk) 00:14, 23 July 2017 (UTC)Reply
Got it.DMC511 (talk) 00:25, 23 July 2017 (UTC)Reply
Thanks, DMC511! I don't edit this much and didn't pay close attention to when I made the edit. Corkythehornetfan (ping me) 00:27, 23 July 2017 (UTC)Reply
No problem, Corkythehornetfan! You've helped me out plenty of times in the past!DMC511 (talk) 00:53, 23 July 2017 (UTC)Reply

Template-protected edit request on 17 August 2017

edit

I would like to update Template:NFLPrimaryColor, per this edit diff. Charlesaaronthompson (talk) 21:21, 17 August 2017 (UTC)Reply

@Charlesaaronthompson: I understand the switch statement work, but why did you remove the option "Denver Broncos 97thru11"? Is it unused? – Train2104 (t • c) 12:59, 18 August 2017 (UTC)Reply
@Train2104: I removed the option "Denver Broncos 97thru11" because the Broncos have used the same color codes since they unveiled their current logo in 1997, hence the reason why I am proposing this edit change at Template:NFLPrimaryColor. Charlesaaronthompson (talk) 02:21, 19 August 2017 (UTC)Reply
I see several uses of various NFL color templates with this parameter. You'll have to remove them before this edit can be implemented, or else those pages will break. – Train2104 (t • c) 02:32, 19 August 2017 (UTC)Reply
I disagree with the request. The reason 97–2011 have different colors is because their primary jersey was navy. In 2012 they changed their primary jersey to orange. reference DMC511 (talk) 11:35, 19 August 2017 (UTC)Reply
OK, nevermind then. I withdraw this edit request. It seems like it's too much effort and work to update the colors in all the templates, and not all editors are in agreement, so the consensus is not there. I will withdraw this request. Charlesaaronthompson (talk) 21:04, 20 August 2017 (UTC)Reply

Template:NFLPrimaryColorRaw

edit

The template Template:NFLPrimaryColorRaw was created as a proposed split from the main template. If split is necessary, the template should be copied from the current version of the main template, and the main template should use this version as proposed in the sandbox. May I copy the whole source of the main template into the "Raw" template right away? Should the template be changed to be similar to Template:NFLSecondaryColorRaw and Template:NFLSecondaryColor? --George Ho (talk) 05:53, 21 November 2017 (UTC)Reply

Template-protected edit request on 4 December 2017

edit

I would like to change the HTML color code for the Ottawa Redblacks to  . My edit diff is found here. My source is the team's brand guide and the media page. Brand Guide Media Page (I right-clicked and selected 'Inspect Element' in Microsoft Edge to discern the color code). Charlesaaronthompson (talk) 00:21, 4 December 2017 (UTC)Reply

  Done.  — SMcCandlish ¢ >ʌⱷ҅ʌ<  08:33, 4 December 2017 (UTC)Reply

Template-protected edit request on 25 February 2018

edit

I am updating/correcting all U Sports (previously CIS) teams colours to match branding guides and/or logos from the schools' websites. Since almost all of them were needing to be changed, I am requesting that the entire section below:

<!-- START Canadian Interuniversity Sport (CIS) teams -->
|Acadia Axemen = background:#C03
|Mount Allison Mounties = background:#C03
|Saint Francis Xavier X-Men
|St. Francis Xavier X-Men = background:#000067
|St. Mary's Huskies
|Saint Mary's Huskies = background:#800000
|Bishop Gaiters
|Bishops Gaiters
|Bishop's University Gaiters
|Bishop's Gaiters = background:#461B7E
|Concordia Stingers = background:#812A3A
|Laval Rouge et Or = background:#900 
|McGill Redmen = background:#F00
|Montreal Carabins = background:#4169E1
|Sherbrooke Vert et Or = background:#00502F
|Carleton Ravens = background:black
|Guelph Gryphons = background:#F00
|McMaster Marauders = background:#903
|Ottawa Garnet and Gray
|Ottawa Grenat et Gris
|Ottawa Gee-Gees = background:#8F001A
|Queen's University
|Queens University
|Queens University Golden Gaels
|Queen's University Golden Gaels
|Queens Golden Gaels
|Queen's Gaels
|Queen's Golden Gaels = background:#FC3
|Toronto Varsity Blues = background:#00204E
|Waterloo Warriors = background:black
|Western Ontario Mustangs = background:#554295
|Waterloo Lutheran Golden Hawks
|Wilfrid Laurier Golden Hawks = background:#3D168B
|Windsor Lancers = background:#00005A
|York Lions = background:red
|Alberta Golden Bears = background:#183118
|Calgary Dinos = background:#C00
|Manitoba Bisons = background:#272223
|Regina Rams = background:#00502F
|Saskatchewan Huskies = background:#006735
|Simon Fraser Clan = background:#B5111B
|University of British Columbia Thunderbirds
|University of BC Thunderbirds
|UBC Thunderbirds = background:#245CC8
<!-- END Canadian Interuniversity Sport (CIS) teams -->

Be replaced with this:

<!-- START U Sports teams -->
|Acadia Axemen = background:#D20D44
|Mount Allison Mounties = background:#98002E
|Saint Francis Xavier X-Men
|St. Francis Xavier X-Men = background:#002A5C
|St. Mary's Huskies
|Saint Mary's Huskies = background:#98012E
|Bishop Gaiters
|Bishops Gaiters
|Bishop's University Gaiters
|Bishop's Gaiters = background:#4F2D7F
|Concordia Stingers = background:#7D303E
|Laval Rouge et Or = background:#EB1C24 
|McGill Redmen = background:#EE2E24
|Montreal Carabins = background:#0062AE
|Sherbrooke Vert et Or = background:#008358
|Carleton Ravens = background:black
|Guelph Gryphons = background:#C20430
|McMaster Marauders = background:#7A003C
|Ottawa Garnet and Gray
|Ottawa Grenat et Gris
|Ottawa Gee-Gees = background:#651D32
|Queen's University
|Queens University
|Queens University Golden Gaels
|Queen's University Golden Gaels
|Queens Golden Gaels
|Queen's Gaels
|Queen's Golden Gaels = background:#FEBE10
|Toronto Varsity Blues = background:#003063
|Waterloo Warriors = background:black
|Western Ontario Mustangs 
|Western Mustangs = background:#4F2683
|Waterloo Lutheran Golden Hawks
|Wilfrid Laurier Golden Hawks = background:#3D168B
|Windsor Lancers = background:#0E1E32
|York Lions = background:#C8102E
|Alberta Golden Bears = background:#007C41
|Calgary Dinos = background:#E32525
|Manitoba Bisons = background:#251A06
|Regina Rams = background:#174835
|Saskatchewan Huskies = background:#00693E
|Simon Fraser Clan = background:#A6192E
|University of British Columbia Thunderbirds
|University of BC Thunderbirds
|UBC Thunderbirds = background:#004785
<!-- END U Sports teams -->

That should make it easier for you to update, rather than doing it individually. Thank you.

Cmm3 (talk) 17:31, 25 February 2018 (UTC)Reply

  Note: I've made the requested change in the sandbox (diff). Will sync to live in a few days if there are no objections. Matt Fitzpatrick (talk) 03:38, 27 February 2018 (UTC)Reply
  Done Matt Fitzpatrick (talk) 18:52, 2 March 2018 (UTC)Reply

Template-protected edit request on 28 May 2018

edit

Hello,

Please change Ottawa RedBlacks = background:#AB1E2D to Ottawa RedBlacks = background:black

Reference: https://www.ottawaredblacks.com/media/ (dominant colour is black, secondary colour is red)

Thanks Cmm3 (talk) 15:42, 28 May 2018 (UTC)Reply

Charlesaaronthompson requested the change to AB1E2D late last year here. --Ahecht (TALK
PAGE
) 21:25, 4 June 2018 (UTC)Reply
I see. The primary colour here was changed from black to red despite no changes to the team's branding since 2014. I am requesting that it be changed back. The website, the logo, and the uniforms all have black as the dominant colour. I'm open to hearing Charlesaaronthompson's thoughts as well for the initial change in December. Thanks Cmm3 (talk) 02:27, 6 June 2018 (UTC)Reply
@Cmm3 and Ahecht: Since I was tagged in this section, I will reply. The main reason why I have rendered the primary color for the Canadian Football League (CFL)'s Ottawa Redblacks as  #AB1E2D  (red) instead of  #000000  (black) is because the team's primary color is indeed red, not black. My URL references for this are the 2017 CFL Guide & Record Book, the team's Brand Guide, and the team's 2016 Media Guide. We go by the team's primary branding color, not the team's primary jersey color. That's why the primary color for the Ottawa Redblacks is red. Actually, the HTML color code for the Redblacks' red is  #AC202D . I discerned this color code from this CFL.ca .JPG image and Paint 3D. The primary color for the Redblacks is still red. Charlesaaronthompson (talk) 19:43, 6 June 2018 (UTC)Reply
@Charlesaaronthompson and Ahecht: Hey Charles, none of those references list red as the primary colour, it just lists it first among red, black, and white. Additionally, the link you have here Brand Guide lists the shade of red as Pantone 187 C, which is listed on Pantone's website as  #A6192E . Because there are no articles that list red as the "primary" colour, I am still requesting that black be reverted to the dominant colour. Functionally, this is also to differentiate the team from the Calgary Stampeders, whose dominant colour is red with black as the complementing colour. And I am also requesting that the correct shade of red be used. I would recommend using Colorwerx, which has a very good grasp on the correct shades for teams. The CFL website's logos aren't always accurate (hence why you've had to change it twice). Thanks Cmm3 (talk) 01:04, 7 June 2018 (UTC)Reply
@Cmm3 and Ahecht: OK, I have now changed the colours for the Ottawa Redblacks at Template:NFLPrimaryColor, Template:NFLTertiaryColorRaw and Template:NFLAltPrimaryColor so that the primary colour is  black  and the tertiary colour is  #A71930 . Charlesaaronthompson (talk) 04:24, 7 June 2018 (UTC)Reply
  Done This appears resolved Galobtter (pingó mió) 14:14, 8 June 2018 (UTC)Reply

Requested move 4 June 2018

edit
The following is a closed discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. Editors desiring to contest the closing decision should consider a move review. No further edits should be made to this section.

The result of the move request was: Move (technical move requested) - as stated in the discussion, this is a sensible stop-gap until a module can be coded. (non-admin closure) ƒirefly ( t · c · who? ) 09:10, 14 June 2018 (UTC)Reply



– This template is used for CFL, Arena/Indoor football, and other international leagues in addition to NFL, so the NFL name no longer makes sense. Ahecht (TALK
PAGE
) 21:34, 4 June 2018 (UTC)Reply

Let's take the opportunity to lose the CamelCase — Martin (MSGJ · talk) 11:36, 5 June 2018 (UTC)Reply
Agreed. I updated the request. --Ahecht (TALK
PAGE
) 17:23, 5 June 2018 (UTC)Reply
I've starting putting together the database necessary to do so at Module:Gridiron color/data, but it's not quite straightforward given how past years are handled in two different ways (and one way isn't Y2K compliant). However, there's no reason to hold up the move while the module is being built. --Ahecht (TALK
PAGE
) 01:08, 6 June 2018 (UTC)Reply

The above discussion is preserved as an archive of a requested move. Please do not modify it. Subsequent comments should be made in a new section on this talk page or in a move review. No further edits should be made to this section.

Module ready for testing

edit

@MSGJ, Corkythehornetfan, Dissident93, Charlesaaronthompson, DMC511, JJMC89, Matt Fitzpatrick, Frietjes, Zzyzx11, Deejayk, and Cmm3: Pinging the regular contributors to these templates (and contributors to the move discussion) — I appologize if I missed anyone. I have created a lua module at Module:Gridiron color/sandbox and implemented it in the sandbox versions of the templates in the move request:

The color data is stored at Module:Gridiron color/data. Please try out these templates and let me know if there are any bugs or corner cases that I missed, and if not, I will go ahead and switch things over. --Ahecht (TALK
PAGE
) 13:37, 14 June 2018 (UTC)Reply

Ahecht, what is the <!__ END UFL teams -- for? typo? Frietjes (talk) 13:39, 14 June 2018 (UTC)Reply
@Frietjes: Good catch. It's actually a typo in Template:NFLTertiaryColorRaw that was introduced in 2016 that got carried over. I fixed it in both. --Ahecht (TALK
PAGE
) 13:46, 14 June 2018 (UTC)Reply
Seems fine to me... is it just me or why do the V·T·E and [view] show in black? Maybe it is just too early in the morning for me... Corky 15:53, 14 June 2018 (UTC)Reply
@Corkythehornetfan: The V·T·E links in which template? --Ahecht (TALK
PAGE
) 17:25, 14 June 2018 (UTC)Reply
@Ahecht: I tested it in several NFL team templates (I.e. {{Washington Redskins}}, {{Dallas Cowboys}}) and when the template was placed in the navbox, the vte and view links showed black font... again, it may be way too early for me and may be because it's the sandbox template being used. 😁 If others haven't asked about it, I'm sure that's the case! Corky 17:38, 14 June 2018 (UTC)Reply
@Corkythehornetfan: Looks like {{NFLAltPrimaryStyle/sandbox}} wasn't included in the move list or updated. It should work now (see Template:Dallas Cowboys/sandbox and Template:Washington Redskins/sandbox). --Ahecht (TALK
PAGE
) 19:25, 14 June 2018 (UTC)Reply
@MSGJ, Corkythehornetfan, Dissident93, Charlesaaronthompson, DMC511, JJMC89, Matt Fitzpatrick, Frietjes, Zzyzx11, Deejayk, and Cmm3:   Done The module has been implemented for all the listed templates. We've already squashed one bug with infinite loops, but please let me know if you see any weirdness.
I've also implemented a contrast check function in {{Gridiron primary style/sandbox}} and {{Gridiron alt primary style/sandbox}} to address the accessibility issues brought up above (which you can test at Template:Gridiron primary style/testcases and Template:Gridiron alt primary style/testcases). Let me know at Module talk:Gridiron color#Accessibility problems if you have any feedback on that feature before I implement it in the main module. --Ahecht (TALK
PAGE
) 16:22, 22 June 2018 (UTC)Reply
Sorry for being late to the party. You guys have done an awesome job, but there seems to be a broken connection between the new template that isn't allowing for college teams colors to show for college coaches who played in the NFL. See Jeff Brohm, Jim Harbaugh. DMC511 (talk) 23:43, 26 June 2018 (UTC)Reply
@DMC511:   Fixed. --Ahecht (TALK
PAGE
) 18:50, 27 June 2018 (UTC)Reply