
Army-Navy 2007 has passed, and I’m going to share with you a few lessons learned from covering the big game.
Before reading this post, it’s probably a good idea to check out our Army-Navy coverage, if you haven’t already. I’ll start off with discussing what Stripes did in years past.
Usually, Stripes would send a photographer to the game and grab some photos and make a photo gallery. Stripes does not have any domestic sports writers, so my paper usually did not cover the game from a written standpoint. FYI, Stripes is only published overseas for U.S. troops and DOD members.
Stripes.com, however, gets about 2/3rds of its readers from the U.S. Thus, we have a different audience to cater to, and we should begin covering stories that matter to people stateside. A few months ago I brought up the idea of Stripes doing a special feature for the Army-Navy Game because it would be a great way to expand our audience, especially stateside.
Plus, Army-Navy is the kind of event Stripes should be covering in depth in the first place. I then began making a list of stories and angles I wanted to cover the game and events surrounding it from. This was my first year at Stripes, which is why I didn’t cover the game last year.
Goals:
To cover Army-Navy and everything surrounding it from a myriad of angles in several different formats. I wanted to tell the story of what this game meant to people, and how it is different than other college football games.
This was not going to just be a feature that could have been done in print. In fact, it was a Web-first feature, where content was taken from the feature and put into print later on.
Some things were left on the cutting room floor:
We didn’t do video (our cameras will not arrive until January or so), we didn’t make it out to West Point or Annapolis to interview students before the game and we didn’t have a commenting feature on the site (although we accepted e-mail comments that we put up if they were good).
Here is what made it:
We had seven written pieces (leading up to the game, on game day and day after stories), two audio slideshows, a big photo gallery with about 100 photos from the day, numerous other photos (from last years game, this years game and the press conference before it), comments from fans and others and additional audio. All of this was packaged together in a stand-alone site made with (X)HTML, CSS and Ajax.
How did it go?
For the most part, it went pretty well. It was more time consuming than normal because our Web staff was under staffed, and we were training two new people a few days before the game. I was the only one the editorial staff had at the time to code the feature and to do the audio editing, which meant for some really long hours. Plus, I was the lead writer for the feature because our Washington Bureau does not have a sports writer.
But the feature came off smoothly because I reused a lot of the code from a previous special feature I did. It gave me the basis for the page, while I had to change the look of it. I did have to write a bunch of new IDs and classes because this feature was much bigger and incorporated a lot more content.
The feature accomplished what I hoped it would — it covered the game and the pageantry from a variety of angles. Army-Navy is a lot more than just a football game. In fact, that is only part of it.
The audio slideshows were the perfect way to convey what the pep rallies were like at the Pentagon. No written text could do them justice. You just have to hear and see it, and the pep rallies are probably too fast to capture well with a video camera (there is a bit of running needed to keep up with those young academy members as they go through the halls of the Pentagon).
Why the Web?
This is the kind of story that isn’t possible to tell properly in print. I Twittered live from the game with my thoughts and observations on how the game was going. We put up updates as the game went along and had photos from the game on our special feature during the game.
We had a story about the pre-game festivities up at half time, and our recap was up shortly after the game. Later that night I added audio clips and photos to our story about the pre-game festivities.
Honestly, printing a recap a day after a football game happens is so 1980s. People want it immediately and they want lots and lots of photos. And much, much more.
You can’t cover an event like Army-Navy with just text and photos like a newspaper does. You need the multimedia content. And the ability to put more than 100 photos up about one event is something that the print will never be able to do.
What to differently?
This feature created a lot of buy in from the print staff. It was the first feature that I have led at Stripes (from not just an online perspective, but from a story and content one as well). A lot of print staffers are finally seeing what is possible online, and how we can do features on our Web site that really extend our brand and serve our readers better.
Plus, what’s good for Stripes.com is good for the print edition too.
We’ll be doing video next year and hopefully making trips out to both campuses a week or two before the game to get some more color from the students. It would also be nice to attend the pep rallies at both schools.
Allowing people to comment on stories, and a better way for people to send us comments, photos or other content would also make this feature better. It could use some more interactivity.
But in the end, the purpose of this feature was to tell the story of Army-Navy as best we could, while informing people as deeply and quickly as possible.
This feature was for the fans.
P.S. Special thanks to the whole Stripes Washington Bureau for helping out the Web staff. You guys are incredibly busy covering the Pentagon and Capital Hill, but you still managed to get us photos of the pep rallies (Lisa Burgess and Jeff Schogol) and help give us great color coverage on game day (Leo Shane III). Bureau Chief Pat Dickson and his whole staff have been big supporters of the Web staff and stripes.com. You can’t create cool features without buy-in from print staffers.