I used to have separate sections of this site dedicated to my portfolio and my code samples. After awhile, I realized that how I was displaying code samples was wrong, and I applied that logic to my portfolio as well. As such, my portfolio is now a part of my blog, shared with this category.
A look at DetroitHockey.Net’s 25th Season logo on the site’s 24th birthday.
Today marks the 24th birthday of DetroitHockey.Net, my Detroit Red Wings-centric hockey site and the first site I ever created.
Normally the 24th birthday would be the start of the 25th season but in the world of COVID, timelines aren’t what they once were. Nonetheless, earlier today I unveiled a 25th Season logo at DH.N.
I’d been doodling quite a bit in the lead-up to the site’s 24th birthday. I knew I wanted to differentiate the 25th Season logo from the 20th Season logo by putting the “25” front and center, rather than the site logo, but I had a hard time with anything beyond that.
I was trying to avoid using a bounding shape and was focusing on just using “25” and the site logo when I realized I couldn’t make those work the way I wanted to. I didn’t want to do a shield (the DH.N logo) inside of another shield, so I went with a circle as the bounding shape. I felt like the circle needed to be broken up to help distinguish the anniversary logo from the site’s “promotional” logo, so the ribbon came in and the site logo was lowered to break the bounding circle at the bottom.
The ribbon gave a good place for most of the anniversary-related text. Like it is in the site’s “promotional” logo, “DetroitHockey.Net” arches across the top part of the bounding circle.
The four stars across the bottom part of the logo represent the four Stanley Cup Championships the Red Wings have won since the site was founded in 1996.
My one complaint about this is that it feels like there is empty space before and after the “DetroitHockey.Net” text. It’s necessary to have some space to let the individual elements breathe but that feels like just a little too much and I couldn’t figure out a better way to handle it.
The number of times I have “quit” the Grand Rapids Griffins’ annual jersey design contest is comical at this point. Last year I even publicly announced that I was done. Then they went and made this year’s edition 90s-themed and I was drawn right back in.
Two years ago the Griffins requested an 80s-themed “fauxback” jersey as part of their contest. I loved it because it raised the question of what makes an 80s-themed jersey.
As I wrote at the time, there were many jersey design elements that became more prevalent in the 1980s, but it was really color that defined the decade. The Griffins were dictating the colors for their contest, though, so I was really curious what they would deem “80s enough” to win. In the end, and perhaps unsurprisingly, I strongly disagreed with their choice, which left me feeling like the question of what makes an 80s jersey was unanswered.
This year, with the challenge being to create a 90s-themed jersey, I believe there are much stronger trends to work with.
While the 1980s saw only two NHL teams relocate and only one go through a major rebranding, the 1990s saw seven expansion teams, three relocations resulting in new team identities, and a whole slew of redesigns. Many of them used the same design elements and most of those changes have since been reverted, resulting in a set of looks that are uniquely 90s.
As such, when the Griffins announced the theme of this year’s contest, for me it wasn’t so much a matter of figuring out what they were asking for as it was figuring out how to make all of those design options work together. An idea popped into my head almost fully-formed. As such, despite my “retirement,” I was drawn back in.
As an aside… I am writing this on August 2 for publish after the design contest is over. I usually spend the entire design period tweaking, then write up my design thoughts and publish them along with my submission right at the deadline. This year, as part of an attempt to put less effort in, I’m submitting my design on the second day of the contest and writing this up for publish after voting is over.
There are six distinctly 90s elements to this jersey. I’ll note who used them in the NHL to show just how prevalent they were (I’m choosing the NHL because their identities are generally more stable and documented than minor leagues).
From their inaugural season to the AHL’s league-wide redesign in 2009, the Griffins’ jerseys featured a shoulder design that was meant to represent the wings of their mascot. I’ve brought them back here. It’s something that’s unique to the team from the era in question.
By using this shoulder pattern, I was unable to take advantage of another trend of the 1990s: alternate logo shoulder patches. They just don’t work on that background.
Diagonal Sleeve Stripes
Diagonal sleeve stripes were used in the NHL prior to the 1990s (specifically, by the Pittsburgh Penguins, Hartford Whalers, and Vancouver Canucks) but in the 90s there were nine teams that introduced them or brought them back, bucking the trend of standard straight stripes. The aforementioned Penguins, Whalers, and Canucks all used them. The expansion Mighty Ducks of Anaheim and Florida Panthers and the relocated Phoenix Coyotes did as well. Redesigns or third jerseys for the Calgary Flames, New York Rangers, St. Louis Blues, and Washington Capitals all featured diagonal sleeve stripes.
Angled Hem Stripes
Most – but not all – teams who introduced diagonal sleeve stripes also paired them with a nonstandard angled set of stripes at the hem. Anaheim, St. Louis, and Washington all went with an asymmetrical version of this element while Calgary and Pittsburgh chose to make a “V” shape of their stripes. Additionally, the Colorado Avalanche featured a mountain-like design along their hem.
I really dislike the asymmetrical look – even if it’s iconic – and the gap in Pittsburgh’s design, so my concept uses something similar to what Calgary’s 1998 third jersey had.
The vertically-arched nameplate was introduced to the NHL by the Detroit Red Wings in 1982. In 1990 it was copied by the Rangers. The Avalanche used it when they relocated in 1995 and the Panthers switched to it in 1998.
While this is hardly a widespread design element from the 90s, the fact that it quadrupled in use over the decade and that the Griffins are the farm team of the originators makes me comfortable including it in the design.
In 1967, the Penguins made their debut wearing rounded numbers, dropping them after a single season. The Rangers broke from tradition in 1976, switching to a completely different jersey that included rounded numbers, which only lasted until 1978. The Red Wings switched to “fancy” numbers for the 1982-83 campaign before immediately switching back. For the first 75 years of the NHL, those were the only times a team didn’t wear some form of block number on their jerseys.
Then the Tampa Bay Lightning came along. After spending their inaugural campaign in a standard – though drop-shadowed – block font, in 1993 they italicized their numbers. That same year, the NHL’s All-Star Game featured jerseys with rounded numbers rather than block. One season later, the Flames had italicized numbers while the Lightning had moved on to a custom “paintbrush”-like font. One more season later, seven teams had at least one jersey that didn’t use a block font.
By the summer of 1999, 14 teams were using a non-block font on at least one of their sweaters.
The Griffins debuted with a custom number (and name) font and I was highly tempted to go back to it. In the end I chose to stick with a slightly-more-generic rounded font, similar to those used by Calgary, Nashville, Phoenix, the Carolina Hurricanes, and the San Jose Sharks.
Tampa Bay’s “paintbrush” numbers might be more memorable than any of them but I just didn’t think they fit the design. My goal (whether it’s the request of the Griffins or not) is to make the most-90s jersey that still looks good, not just cram as much 90s stuff into a jersey as possible.
Angry Mascot Logo
The last element of the jersey is the Angry Mascot Logo. San Jose debuted represented by a Shark biting a hockey stick in half. Florida’s first logo featured a Panther pouncing forward. The New York Islanders rebranded to focus on a fisherman holding a hockey stick, staring angrily.
In the minor leagues the trend of “fierce” logos was even more visible. Between the AHL and the IHL, no fewer than 13 teams introduced branding – of various qualities or rendering – featuring some combination of a snarling animal or fearsome creature between 1990 and 1999, including the Albany River Rats (1993), Carolina Monarchs (1995), Chicago Wolves (1994), Cincinnati Cyclones (1992 and 1993), Denver Grizzlies (1994), Hamilton Bulldogs (1996), Hartford Wolf-Pack (1997), Indianapolis Ice (1996), Kentucky Thoroughblades (1996), Lowell Lock Monsters (1998), Beast of New Haven (1996), Saint John Flames (1998), and Syracuse Crunch (1994).
I have to admit, I don’t like this trend. The Griffins’ original logo does not meet my criteria for “fierce” and I find it to be a better logo than either their current mark or the one I’ve created here. But to stick with the trend, I’ve swapped majesty for musculature. That said, I do feel like, in doing so, it’s moved out of 90s and become a little more modern.
I submitted this jersey in red because I think it looks best. That said, another perceived trend of the 1990s was “black for black’s sake,” seeing teams add black as a team color and introducing black jerseys simply because it was a color that sold well at the time. With that in mind, I created a full jersey set that includes a black alternate.
The funny thing (though I suppose how funny it is depends on how far this design goes in the contest) is that I’m not sure I actually even like this design. It’s easily my least favorite submission to the Griffins’ contest over the years. Given what they’re asking for, though, I think it nails it.
I called “black for black’s sake” a perceived trend because it simply didn’t happen in the NHL the way that it’s portrayed at times. There are other elements that I ignored because, while everyone “knows” 90s design was all about them, it turns out the facts don’t match up with that.
The Calgary Flames added black as a trim color in 1995 with a black alternate jersey in 1998. The Washington Capitals included black as a trim color in their 1995 redesign and added a black alternate in 1997. The Philadelphia Flyers already had black trim and their 1997 alternate was black. That’s three of 28 teams.
Teal? That was just the San Jose Sharks, with the short-lived New York Islanders “fisherman” jerseys using it as an accent.
Similarly, there’s Tampa Bay’s “paintbrush” crazy numbers. Yeah, the Lightning used them for six seasons. And the Mighty Ducks of Anaheim had a one-season alternate with a crazy number font. But that’s it. It didn’t take the league by storm. It was really just one team and a quickly-abandoned alternate for another.
Finally, there’s asymmetrical striping. I called it “iconic” above but it was just Anaheim and St. Louis who used it. Two teams. More teams used symmetrical angled stripes, but those don’t stick in our collective memories. The Islanders’ fisherman jerseys were technically asymmetrical but not in the way we typically think of.
We’ll see how many of these perceived trends end up being applied to designs in the contest.
As I detailed at DH.N itself, the Detroit Tigers forced me to change the site’s logo, claiming that DetroitHockey.Net’s Old English D conflicted with their trademarked Old English D. I don’t agree with this assessment but I also can’t fight it.
Thankfully, I had a little bit of a hint that the Tigers would do this, so I’d begun brainstorming ideas for a new logo, just in case. With the Old English D expected to be unavailable to me, I started thinking about other symbols of Detroit.
I ruled out the Spirit of Detroit statue because I think it’s somewhat awkward to work with, plus Detroit City FC uses it in their badge and trading conflict with one team for another seemed like a bad idea.
From there, I started thinking about Detroit’s flag. I’m a big fan of quartered flags – like those of Detroit, Maryland, Panama, and the Dominican Republic – and thought that I could follow the Baltimore Ravens’ example and use elements from the quartered flag in a shield.
With Detroit placing the city’s seal at the center of their flag, I thought that might be a good place to work in a set of crossed sticks, carrying that forward from my previous designs. I simplified the elements of the flag, reducing 13 stars, three lions, and five fleurs-de-lis down to one each.
The idea didn’t work as well as I had hoped. None of the elements looked quite at place there. The sticks didn’t fill the center circle well and said circle pushed the elements of each quarter into an awkward position.
I thought more about the quarters of Detroit’s flag and what they represented. France, England, and the United States (with the latter taking up two of the four quarters), the three countries that have laid claim to Detroit. The flag is basically about how they came together. DetroitHockey.Net takes those things and adds a fourth: hockey. So I decided to remove the center circle and break the shield up into five sections. I also changed the colors so that the red from Detroit’s flag became “DetroitHockey.Net Red,” the yellow became more of a gold, and the blue darkened to match the red.
This was closer to what I was trying to do, but still didn’t seem right to me, so I worked on tweaking how the shield was broken up. Along the way I changed the size of the shield and the angle and number of the stripes. I settled on seven stripes as it represented the seven Stanley Cup Championships won by the Red Wings at the time that the site that would become DetroitHockey.Net was founded in 1996.
The final changes were to switch to a slightly lighter shade of blue, then emphasize that blue.
For a site representing the Red Wings, the extra blue didn’t seem to be a fit, so I rolled back to my previous attempt and went with that.
Given the importance of the number nine in Red Wings history, I feel it’s highly appropriate that my final design was the ninth iteration.
With so much gold in the new logo, I felt it was appropriate to bring that color into an updated version of the roundel mark I use for the site.
Finally, I sketched out a version of the logo that combines the shield and the roundel by taking the elements from the shield and placing them inside the inner circle of the roundel.
I may never use that design but I’m keeping it around for now.
With the change, the new DetroitHockey.Net logo timeline is as follows:
The circumstances of the change have really clouded my own judgement on this one, but early reaction is positive.
As much as I loved the old logo and spent time building a brand around it, there was a lot of empty space and the black border tended to merge with the red a bit. When designing merchandise, I found myself defaulting to monochrome versions of the logo to resolve that issue.
The new logo is more complicated and requires a little more explanation than I’d like but I really like how the combination of red, gold, and blue turned out. I still have concerns about the red and gold evoking too much of a Detroit City FC feel but, to a certain extent, that’s like saying the old colors were too similar to the Chicago Blackhawks. I’m not too worried about it.
In 2016, I didn’t like that the crest on my submission and the shoulder logo both used the same griffin silhouette. I thought it looked good but was just a little lazy. Also, I had intended to enter a red jersey in the contest and was convinced to switch to black at the last minute, so I wanted to return to that idea.
Additionally, at the end of the 2014 contest there was a lesson that I had learned and promptly forgot: Minor league sports teams like logos that have their team name included. I wanted to take that into consideration this time around.
Keeping all of that in mind, I created a new crest for the red version of my 2016 entry.
I changed the shape of the shield just to change things up a little. Across it is a banner reading “Griffins” in a vaguely old-German font that I think matches the heraldic crest. Above that is a stalking griffin in silhouette – because the griffin in the shoulder logo is standing on two legs, I wanted this one to be down on all fours (though only three are really seen).
Like the griffin in the shoulder logo, this new griffin features a pair of homages to other logos. The tail is the tail that was used in the Griffins’ original logo while the wing is based on the Winged Wheel logo of the Red Wings.
I put the new logo on the red jersey design from 2016 and I thought I was good.
But then I kept thinking.
In 2016, the jersey I actually liked best was the white one, which I wasn’t allowed to submit because the Griffins specifically asked for a dark jersey. This year, not only did they not make that requirement, but their promotional calendar has dates for fan-designed jerseys to be worn both before and after New Years’; which is when the American Hockey League switches from wearing white jerseys at home to dark ones.
I decided to switch to the white jersey. Which immediately gave me trouble with the crest again.
I designed the new crest to work best on red. It’s primarily black with a heavy white outline. That outline disappears on a white jersey, so what to do?
I tried out several different color swaps. Added outlines. Took the opportunity to play with the sleeve numbers a little, then immediately abandon that idea.
In the end, I decided to go with a logo that mixed elements from my previous submissions with some of my new ideas.
The extra outline on the shield helps set it off on the white jersey while not outlining the “banner” keeps the logo from getting too heavy.
And those are combined with the previously-created shoulder logo, which sits opposite the logo of the Griffins’ parent club, the Detroit Red Wings.
One final note is that I use a template that doesn’t allow for a laced collar to be displayed. I would expect one to be used, as shown here.
Aside from the Grand Rapids Griffins, I don’t normally enter jersey design contests. In general, I don’t like “fan designed” jersey contests because rarely does an actual fan of the team win.
I made an exception this year, though, for the Kalamazoo Wings. I can’t rightfully call myself a Kalamazoo fan given their rivalry with the Toledo Walleye, who are affiliated with the Grand Rapids Griffins and Detroit Red Wings, who I actually am a fan of.
The K-Wings do hold a special place in nostalgia for me, though. They were the visitors in the first hockey game I ever went to, a Thanksgiving game against the Muskegon Lumberjacks when both teams were in the old International Hockey League and I was about five years old.
So I decided to give the Wings’ contest a shot and, in all honesty, it didn’t go in the direction I expected it to at all.
My initial thought, since all existing K-Wings marks were off-limits, was to turn to mythology. “Hermes had a winged helmet, didn’t he?” In addition to winged sandals, yes he did. So I set about trying to do something like that.
In my head, I was thinking something kind of like the old Ottawa Senators logo, with the team name in a partial roundel broken by the wings of the helmet. It turns out that “Kalamazoo Wings” is a really hard name to work with without getting letters upside down at some point on the circle.
Also, in all of the logos I’ve worked on in the past, I’ve never tried to draw a face. As I continued working, I got closer to what I wanted. I abandoned Hermes and his traveller’s cap and went for a more Nordic full helmet, but the contest deadline came up quickly and I had a conference and a short vacation planned. It just wasn’t going to come together.
In parallel with the helmet-based logo, I was putting together an alternate logo based around a K in a shield with wings. I liked the general shape right from the start but tried a variety of fonts for the K, colors, etc. That process actually went well, and partway through I realized that I had a couple different options I could run with.
As I ran out of time, I decided that I needed to switch gears. I had a solid logo in my intended alternate and I had a tertiary that could become a secondary in a pinch (which I was in). I had a jersey design already in place from a previous Griffins contest so I pulled the plug on continued sketching and called it done.
The crest, as previously mentioned, is a K inside a shield with wings. In gold and blue, I think it has a bit of an art deco vibe.
That shield is repeated without the wings on the shoulder logo, where it’s adorned with a pair of crossed hockey sticks and the letters KWHC – Kalamazoo Wings Hockey Club.
The jersey itself features a red body and blue sleeves. I wanted to do contrasting-color sleeves as they give the jersey the “winged” look of the Detroit Red Wings’ away jersey, something I think is appropriate for another team named the Wings.
It’s not what I was aiming for but I think it looks good. It’s probably not different enough from the K-Wings current design to win the contest, which is why I’m disappointed that I ran out of time to work on the winged helmet idea, which I think was pretty unique.
At my day job our codebase is kept in a handful of self-hosted Git repositories. We have a tool that runs nightly, emailing out a digest of all of the previous day’s commits.
It’s kinda cool but I have the tendency to ignore it as a wall of text. I prefer more granular messaging and since we’re also using Slack, I saw an opportunity to do something with a post-receive hook to get a message as changes came in.
Posting from Git to Slack isn’t revolutionary. There are a tons of solutions for this out there. In fact, my original attempt just used a modified version of Chris Eldredge’s shell script, which I grabbed off of GitHub. However, my Bash-foo is weak and we’re a PHP shop so I decided to write a solution based in PHP (though heavily based on Eldredge as I had that code in front of me).
To fire off the PHP script, the post-receive hook looks like this:
That’s simplified a bit as the actual hooks use an absolute path to the script but you see that the script accepts the oldrev, newrev, and refname arguments.
As for the PHP script itself, it looks a bit like this (I’ve sanitized some things to remove references to our internal services).
We get details about what’s being pushed and build a message out of all of that. Simple enough. So lets break that down a little bit.
If the old revision is empty, it means we’re creating something. If the new revision is empty, it means we’re deleting something. Otherwise it’s an update of something that already existed and continues to do so.
Whatever the change type, we get more information about the old and new revisions by using the backtick operator to run the get cat-file -t command for each revision number.
If the change type is a create or an update, we’ll use the old revision data to reference things going forward. If it’s a delete we’ll use the new revision data.
This is just a bunch of logic that looks at the refname and the revision type and determines exactly what you’ve pushed. If we can’t figure out what it is, we exit with an error.
We determine the repo name based on the path the hook is running from and we get the user it’s running as so we know who did the push we’re about to notify people of.
Now we start building the message that will be posted to Slack. The message begins in the form of “[reponame/branchname]. If it’s a create or delete, we then note what was created or deleted. If it’s a commit, we note the number of commits and who they were pushed by.
We’re going to start building a series of messages (what Slack calls “attachments”) detailing items from the Git log pertinent to this push. We use the git log command and define our format. We get the author name with %an, the hash with %h, the commit message with %s and the commit body with %b. Those are all separated by five ampersands, with each item separated by five at signs. We use those goofy separators so we can split on them later, as it’s unlikely anyone enters those in text.
Here we actually build our message. The text property of a Slack attachment can be markdown, so we pretty it up a little bit. The fallback property is plaintext so it doesn’t get that formatting. The result is the hash, then the commit message, then the author. If there is a longer commit message, it gets added after that.
We’re not done with that text yet, though. We have a loosely-followed naming convention for our commits and we can use that to link back to other systems that might have more information about the commit. Anything that was a Jira task should start with the task number in the format “[ABC-1234]” but sometimes it’s “(ABC-1234)” or “[ABC] (1234)” or “[ABC](1234)” so we account for all of those. Similarly, references to our ticket system sometimes use “TICKET” or “BUG” or “SUPPORT” and sometimes have a space or a dash and sometimes use “HOTFIX” and… You get the idea. There are probably better regular expressions to use here but these work. So we find references to our Jira cards and link back to them, then find references to our support system and link back to it, where there’s a script that will do some additional parsing to figure out where to go.
With all of that done, we build an array for this attachment, defining our text, our fallback text, a color to display alongside the attachment, and confirming that there is markdown in our text field.
Once we’re done looping through our data from the git log and building our attachments, we put together the message and send it off via Curl. The message is just an array, which then gets JSON-encoded and posted to our webhook URL.
It’s fire-and-forget, so we don’t make any note if the webhook doesn’t respond or anything like that.
For a short time we had an additional message attachment that included diff data but we decided we didn’t want our code getting posted to Slack so we removed it.
As I said, there are tons of solutions for this out there, this is just one more.
As I’ve noted in the past, I have a love-hate relationship with the Grand Rapids Griffins’ annual jersey design contest. I have the tendency to put more thought than they probably intend into my own entries and, while I was a finalist last year, I don’t think I ever come close to winning.
This year I was going to skip out on the endeavor entirely until they added an impossible new wrinkle to the contest: Design a 1980s “fauxback” jersey.
The Griffins were founded in 1996, hence the “fauxback” requirement. The idea is to come up with a look that represents a Griffins team that existed in that decade. Which raises an interesting question: What makes an 80s hockey jersey?
The shoulder yokes of the Minnesota North Stars, New Jersey Devils, and Buffalo Sabres all jumped out at me, though all but New Jersey’s found their origins in the 70s. Likewise the 70s birthed the over-the-shoulder stripes of the Winnipeg Jets, Toronto Maple Leafs, and a handful of All-Star teams.
I thought about modern teams that throwback to the 80s and how their identities have changed since then. The Edmonton Oilers’ logo is virtually untouched but changed from royal blue and orange to navy blue and copper (then back to royal blue and orange, and now navy and orange). The Calgary Flames were bright red and yellow in the 80s, darkening their red and adding black in the 90s. The Los Angeles Kings went from purple and yellow to black and silver. The Devils went from red and green to red and black.
What makes an 80s hockey jersey? It’s not so much the striping pattern or the logo… It’s the colors. The bright colors of 1980s hockey design were virtually abandoned in the 1990s. In addition to the previously-mentioned changes, the 90s saw the North Stars go from bright green and yellow to forest green and metallic gold. Like the Oilers, the New York Islanders abandoned royal blue and orange (only to – also like the Oilers – eventually return to it). The Hartford Whalers gave up green and royal blue for green, silver, and navy.
Which is a problem for this contest because the Griffins explicitly stated that entrants should use the team’s current colors, with the jersey base color being red or black.
By my count, in the 1980s across the National Hockey League, the American Hockey League, and the International Hockey League, only the Chicago Blackhawks (and some of their affiliates) used a red, black, and white combination. The metallic silver the Griffins now use was unseen in the NHL until the 90s, though the Kings added grey in 1988. Teams in the 80s used yellow, not the gold in Grand Rapids’ current identity.
As such, I don’t think it’s possible to have an “80s fauxback” that uses the Griffins’ current colors. That didn’t stop me from trying, though.
My first sketch used the Winnipeg/Toronto-style over-the-shoulder striping and a Edmonton Oilers-like logo, with a griffin silhouette over the word “Griffins” in a circle. I also dropped gold and silver from the color scheme to simplify things. The logo felt forced, though, and the striping seemed too modern, so I scrapped that idea.
Next I ignored the logo and tried a striping pattern based on the Buffalo Sabres. The shoulders featured a black yoke with white and gold outlines. The sleeves and waist had a black/white/gold/white/black stripe set. I actually like this idea a bit but, again, there was nothing that made me think “80s” so I moved on.
Just to see if it led to anything, I cloned the North Stars’ 1988 jersey set, swapping green for red and yellow for gold. This led me to believe that the gold just wasn’t going to work and I needed to go back to red, white, and black.
Starting with a red jersey, I added thick stripes in white and black – separated by a thin red stripe – to the sleeves and waist. I then included a yoke in black with a white outline. I realized I had something similar to the Devils’ 1982 home uniform and decided it was 80s enough to move forward. I also decided that between the North Stars, the New York Rangers, various NHL All-Star teams, and some of the 1988 Olympic teams, a drop-shadowed number represented the 80s pretty well, too.
For the logo, the Moncton Hawks jumped out at me, with their bird head and abstract wings inside a circle. I tried going in that direction with a stylized wing attached to a griffin head with an outstretched claw, all merged together with the team’s name as a wordmark. It didn’t look like a griffin to me so I decided to go in a different direction.
Next I went simple. A griffin silhouette in a circle with “Grand Rapids Griffins” around it. Specifically, this was based off of an old Muskegon Mohawks jersey that I couldn’t figure out the exact year for. The wing came from the Detroit Red Wings’ logo while the tail was from the Griffins’ original logo as a pair of homages. It looked more 1960s than 1980s, though, so I went back to the abstract griffin idea.
I removed the circle and added in the bottom half of the griffin’s body. This gave me an opportunity to reuse the tail from the Griffins’ original logo, as with the silhouette logo. Then I switched up the griffin’s head to look more like an eagle and less like a dragon. At this point, I had my crest, and I decided not to worry about shoulder logos because, by and large, they weren’t used in the 80s.
While I’ve submitted the red, black, and white design, I still don’t think it’s 80s enough. The colors make it look 90s to me.
I tried simplifying the design to just red and white and, while I think it looks more 80s, I don’t think it looks as good. In the end, the design has to look good enough to win.
But I come back to the idea that, by forcing the modern colors, the Griffins have unintentionally made any submission less 1980s. I tried the team’s colors from before their rebrand two years ago – red, white, and blue – and feel that it’s a design that screams 80s. I just can’t use it.
Wrong colors or not, as I said at the start, I don’t expect to win this thing anyway. Based on last year, the voters seem swayed by submissions that look like they came out of a catalogue or a video game, not flat designs in the template I use. I don’t get to submit all the thought I put into it. But it will be interesting to see what the voters think an 80s jersey is.
Update 8/21/2017, 8:50 PM: My design is up for vote today, which gets me thinking about my design more. I now think I should have included a circle behind the logo, as I originally attempted. It helps make it look more 80s than 90s.
Though it’s too late for the contest, I’ve updated the red jersey I submitted to include the circle, added it to the blue variant that I think the team should actually wear, and created white versions of each.
I launched FantasyHockeySim.com as a spinoff of DetroitHockey.Net last summer and the visual elements of it were a rush job. Getting the site out the door was my priority, so I stole design elements for FHS from DH.N and put together a logo that didn’t say “fantasy hockey” at all.
Awhile ago I ranted about the Detroit Red Wings’ “Hockeytown” logo and how the only way it said “Hockeytown” was literally, with the text splashed across it. I’d done the same thing with the FantasyHockeySim.com logo, as crossed sticks said “hockey” but the only way it said “fantasy hockey” was via the FHS acronym across the front. Even then, it looked more like the logo for a high school hockey team than for simulated fantasy hockey software.
While stuck on a development project, I decided to take a crack at a new FHS logo.
Because I like shield-based logos far too much, my first pass centered around different shields. Eventually I put together one that I really liked the look of and started building alternate logos around it.
I showed the “final” set (the shield logo and “promotional” versions featuring additional text) around and realized I hadn’t solved the problem I was trying to handle in the first place. The logos still only said “fantasy hockey” literally, and even then it was only the promotional ones.
I stepped back from it and didn’t think about it for awhile until an idea came to me during my drive into work a couple weeks later.
Representing hockey in a logo is easy. Sticks, pucks, all sorts of imagery is available. How do you represent “simulation” though? Well, simulation means computers and code and, even to a layman, X/HTML’s angle brackets are recognizable as code. So I wrapped a pair of crossed hockey sticks in angle brackets and went from there.
The first issue I hit with the logo was that the crossed sticks looked a bit like an X, so I changed their position and added lines representing tape to the blades. After that, I decided to give up on my attempt at a monochrome logo, changing the color of the angle brackets to help separate them from the sticks (with the added effect of appearing as syntax coloring).
As I worked on a primary version of the logo, I also created an alternate version and a “promotional” version. The promotional logo features the “bracket” logo inside a roundel containing the “Simulated Fantasy Hockey” descriptor and the site name while the alternate is simplified version of that, without the text.
The biggest issue with the alternate and promotional logos was making sure the broken inner circle of the roundel didn’t appear like it was supposed to be attached to the angle brackets. To handle that, I shrank down the width of that inner circle and made the break in it wider. Changing the color of the brackets completed the effect.
The FHS site still needs a redesign to get away from borrowing so much from DH.N but at least now the logo is original and descriptive.
Two years ago I entered a design featuring a griffin silhouette on a shield as the primary logo, with the jersey in “vintage” white, blue, and red. The shoulder logo was a roundel with an interlocking GR logo the team had previously used. Last year I tweaked the logo to make the griffin’s wing a little cleaner, switched up the shoulder logos, changed the number font, and updated the colors to go along with the Griffins’ color change, but the striping pattern stayed the same.
This year I thought for certain that I was going to enter another red jersey, so I started with my previous design. I swapped out the “vintage” colors and simplified the striping pattern. Rather than black numbers with a white outline, I went with white numbers outlined in black as they would be more legible. I kept the player’s jersey number in the collar webbing because, as I’ve said before, I loved that feature of their old alternate jersey. I also brought back the shoulder logo from my original entry as a 20th Season patch no longer made sense. Finally, I broke down and put the Winged Wheel logo of the Detroit Red Wings on one shoulder, as the Griffins do that on their standard jerseys to denote their parent club, no matter how much I dislike the practice.
I felt like that design was too simple, though, so I continued evolving the design. For the second generation, I switched the order of the sleeve colors and removed the shoulder yoke. I wanted the Griffins’ jersey to have an homage to the alternate colored sleeves of the Red Wings’ white jersey. I also brought back the black numbers outlined in white as I figured for a one-shot jersey, legibility is less of a concern (in fact, the Griffins wore dark red numbers on a dark blue jersey for one game two seasons ago).
Unfotunately, I thought that looked far too close to the design of the Texas Stars. While the Griffins selected a design two seasons ago that was basically a color swapped Iowa Wild jersey, I wasn’t comfortable submitting something like that.
As such, I decided to fully embrace the alternate-colored sleeves. I made the jersey body red with a black stripe bounded by white and the sleeves black with a red stripe and white outline. I also changed up the shoulder logo, replacing the interlocking GR with the griffin silhouette I used on the crest as I didn’t want to re-use one of the team’s existing marks, even modified.
At this point, I thought that I had my final design. I started showing it to a handful of people and near-universally the feedback was that they wanted to see a black version. Of course, I had started out trying to make a red jersey, so at first I ignored this. Eventually I hit the point where I had to listen to what my informal focus group was saying and did a switch of the colors. While a quick Twitter poll showed 53% of fans would have preferred a red jersey, 100% of people who saw both the red and black jerseys picked the black one. As such, the black one was my final design.
There are some coincidental homages in this design. The Grand Rapids Owls, an International Hockey League team in the late 1970s, wore jerseys with red sleeves that had black stripes outlined in white. Additionally, the Red Wings sold “fashion” jerseys (alternate jerseys that were never actually worn in-game) that had a black body with a red stripe at the waist, red sleeves with a black stripe, and numbers that match this design. The stripes did not include a white outline.
The Griffins explicitly stated that they wanted a dark jersey from this year’s contest. I imagine that’s because of the AHL’s new rule that will see light jerseys worn at home until Christmas and dark jerseys after that. Previously there had been some flexibility with regards to alternates but I’d guess that’s out the window with these new rules.
At any rate, just for fun, I created a white version of my submission.
As I mentioned, the primary logo is carried over directly from last season’s submission, aside from the color switch. This is a logo full of homages. The shape of the shield is that of the DetroitHockey.Net logo as a reference to my previous work. The feathers on the griffin’s wing are those of the Winged Wheel. The griffin’s tail is that of the original Grand Rapids logo.
The shoulder logo went through a number of revisions as I sorted out what color it would be placed on, how much detail should be included, and what element would be inside the roundel.
While I think that having a silhouetted griffin on both the crest and the shoulder is a bit repetitive, I see the different uses to be somewhat like how the Tampa Bay Lightning have a lightning bolt on both the crest and the shoulder.
As I’ve said every year, I don’t expect to win this contest. This year is interesting because ten finalists will be determined by fan vote and then the Griffins staff will decide. Additionally, this year submissions do not have to follow a standardized template. If I had to guess, the vote will skew towards submissions that look like they come out of a video game, as they come across as the most impressive. Whether or not those are actually the best designs will have to be seen.
Update: After posting this I noticed that the shoulder logos are incorrectly depicted on the view of the back of the jersey. They should be switched so that the Winged Wheel is on the right shoulder and the roundel is on the left, as they appear in the view of the front of the jersey. I’m not going to update the graphics, just use your imagination a little.
With the fantasy side of the site gone and no longer reliant on the rarely-used DH.N Community Forums, I reworked DetroitHockey.Net to remove the forums. I also pulled out my custom blog software and replaced it with WordPress.
The idea behind going to WordPress was that, while I enjoyed writing my own blog software, it left me somewhat behind the times as far as what the site was capable of. It’s a wheel I don’t want to reinvent, so instead I learned how to tap into native functionality of WordPress to do the things I wanted to do.
With the loss of the forums and the continued simplification of the site content, I was able to go with a more streamlined design. The header features the site logo (I launched with the 20th Season logo in place but it will revert when that season ends), an advertisement, and one navigation bar. This is in contrast to the old version of the site, which had a logo, three navigation menus, a login menu, an ad, and a set of links to forum discussions.
I also took the opportunity to implement the sub-navigation menu system that I developed for FantasyHockeySim.com.
The home page features seven recent headlines from the WordPress-driven news section, an embedded Twitter feed (replacing a custom developed version of the feed display), the score of the most recent Red Wings’ game, and a calendar showing the current month’s schedule (with games denoted by opponent logo).
The individual article pages use a modified version of the WordPress Twenty-sixteen theme, wrapped in the DetroitHockey.Net template.
The only other page that was heavily modified was the DH.N Contributors page, which pulls from the WordPress user system.
This version of the site is intended to be transitional, with further revisions coming after seeing how the forum-less site is used.