Promote the watchgmctv.com case study to front page

I'm not too sure about this one, primarily because it doesn't seem like high value marketing to me. First, the site was already in Drupal before the work described here, which makes it a bit hard to see where the value of what you completed lays. Second, there's way too much hedging of your statements, which makes the entire piece seem pretty weak (for example: "Hopefully, the collaborative effort between Mediacurrent and gmc has resulted in a more sophisticated, flexible and professional site.")

Unless this is changed to an overall piece on gmc's usage of Drupal, or a bunch more description is added to the "why D5 was a problem", I'm giving this a -1.

First, thanks for the feedback and taking time to review the request.
In regards to a few of the concerns you raised:

"doesn't seem like high value marketing to me…"

We formatted the case study in a way that primarily addresses the “how’d you do that…” type questions that seems in line with other front page posts. For example, we walk someone through the design/theming process, what the goals were, our challenges, and how Drupal was leveraged – think of this as less of an upgrade as a complete re-build in v6 of Drupal (with extra features the previous site did not have).

"way too much hedging of your statements…"

I re-read the case study and "way too much hedging" seems to be painting with a wide brush stroke. In the one example you cited, I think you are correct in that “hopefully” was a poor word choice – inserting the client’s direct feedback though sounded more like a self-serving testimonial for Mediacurrent, which was not our intent. Here is what gmc said:

"Mediacurrent's experience and expertise in Drupal helped our team bring to life a new feature-rich web site to promote and integrate a constant flow of ongoing initiatives both on-air and online."
-- Mark Wolfe - Manager: Digital Media Design + Development

To me, this underscores a client that had a positive experience with Drupal and would provide validation to those with similar requirements.

"which makes it a bit hard to see where the value of what you completed lays…"

In my opinion, the name recognition of the client (they have a cable television network and comparable if not higher traffic numbers than most other front page posts) has significant value. The real value is in showcasing one more example of a successful Drupal site. I'm really not sure why it would even be relevant if they were already on Drupal (there was not a case study generated for the previous v5 site)? The front page request is about increased exposure. The fact that someone could learn that gmc was on Drupal, and chose to stay on Drupal when their v5 site was becoming outdated, has significant merit.

"why D5 was a problem..."

It really was not a problem - they had a site that needed a major face-lift based on their brand drastically changing. We did not want the case study to focus on what was wrong with the old site v. sharing with the community our lessons learned, what modules were used, custom solutions applied, how we tackled theming, incorporated in the new brand, handled content migration, etc.

Again, we appreciate the constructive feedback and hope this addresses any concerns others may have - as I am sure you can relate drafting a case study is time-consuming, and we would not have submitted if we did not think the write-up would be beneficial to others in the community.

I don't find any reference to the correct screenshot size, but the screenshots should be smaller; silverwing or gdemet can say which size we normally use.

300px wide on the screenshot image.

Thank you, silverwing. I also found a comment where you report the file size should be 50 KB.

Thanks - we will make those file size adjustments.

I think this is a worthy case study for the home page, but it needs some copy editing. This week is pretty full with the Drupal 7 launch and associated announcements, but I'll assign this to myself for review.

I've made a number of copy edits and activated Full HTML format so that the images now appear on the post. This looks fine to me; my only remaining question is that there is some discussion of custom modules that were created and/or existing modules that were patched, yet no explanation of whether any of these custom modules or patches would be released back to the community or not. If you could address this question here in the issue queue with some copy that I could flow back into the case study, it would likely get my +1 for promotion. Thanks!

One last beef from me is with this sentence: "America's favorite channel for uplifting music and entertainment featuring specials, movies and series the whole family can enjoy". Please qualify it with "America's favorite channel for uplifting COUNTRY music". I don't want foreigners thinking that most Americans listen to country, because we most certainly don't. For the record, I personally would rather listen to the Drupal song (or even the dreaded Kitten Killers) on repeat for a year on end rather than being forced to watch some dude whine about his truck, or get all sappy bout "Merica, F yeah!" for even a couple of hours...

Looking at the site in question, it looks like gmc features "uplifting" music in a variety of genres, not just country. I can definitely appreciate the concern that the way the sentence is worded might lead some to believe that the "uplifting" genre is one of America's favorites, as opposed to what it actually means, which is that for people who like "uplifting" music, gmc is their favorite place to listen to it.

I've reworded that sentence to read, "...is a channel that features uplifting music and entertainment, including specials, movies and series that the whole family can enjoy." which I think factually describes their content without any implications about what Americans do or don't enjoy.

Thanks Jeff - I think if you could provide a sentence or two for the beginning of the "Custom Modules" section that elaborates on what was (or wasn't) contributed back and why that would be helpful. Otherwise, this looks great to me.

I am going to add those sentences to the page.

I added the required sentences, and slightly changed the rest of the text (e.g., the organisation was sometimes referred as gmc and sometimes as GMC; I changed gmc with GMC) or the HTML markup (e.g., I changed <b> with <strong>).

I believe that while not traditional usage, in this case "gmc" should appear in all lowercase, as that seems to be the company's brand identity and is how they refer to themselves (http://www.watchgmctv.com/about-us). I think this should be changed back, but otherwise this has a +1 from me.

I will change that in minutes, when I will return to my netbook (doing it from an iPod is not the best).
I thought that, being an acronym, it should be written in upper case (the fact sometimes it was written in upper case confused me); I didn't check how they write it in their site (as I should have done).

I fixed my mistake.

@kiamlaluno - confirming that lowercase is the correct acronym...thanks for updating.

Does the case study go into a rotation to appear on the front page - was not sure what the next steps were from here?

+1 - though I hate the lowercase gmc.

Added you to the schedule on January 21

Missed this on Friday, but it's promoted now.