Front Page Request for new case study: Vancouver Magazine Redesign

I've updated the post with the new images. Ideally the images should be attached to this issue and the HTML updated so they are hosted on drupal.org's infrastructure.

I also don't see this on http://drupal.org/node/280488 - could you schedule it in there?

The writeup seems great to me. I'm +1 on promoting it.

This case study shows a lot of promise. It's great to see case studies of this quality develop organically. However, it does needs some review. In particular, it needs to be reviewed for use of capitalization Drupal, HTML and CSS are some examples. All sentences should begin with caps. See "the primary menu", "the secondary menu" bullets.

The flow of the case study could be improved visually if the images are positioned beside the text, particularly the examples of custom modules. Images needs to be local to keep the front page loading quickly.

Normally we mention the development shop at the end of the case study. This keeps down criticism about front page posts being too promotional.

Some sentences need review, such as "This helped tons because we had real content coming back rather than greeking or our ideas of what content should or would be in an article, restaurant listing or popup list.".

The list of of Key contributed modules should be organized in some obvious fashion and have completed descriptions ideally. So I would organize them alphabetically, or numbered if they are in order of importance.

I agree with Kieren's points. The only one I wonder about is how to naturally speak about the project background without mentioning Grey or ImageX. I'm fine with moving the shop names lower so that the article appears less commercial but I wouldn't want to do so if it impacts the flow.

Before this gets promoted to the front page I'd like to jump in with some last minute edits and suggestions. In general I think that the write-up is informative and unfolds in a logical fashion. However there are some inconsistencies with the tone and a tendency for long sentences (watch out for anything than runs to 3+ lines). To help with some final polish I've created a list of potential edits below. Please do not consider any of the changes "blockers" to this being promoted. As I said, I feel that the writeup is already of a high-quality and informative. On the technical side, both myself and Ben (the lead ImageX developer on the project) have reviewed for accuracy and everything checks out.

Potential Edits:

• Uoi should link to vanmag.com at some point.
• "Vancouver Magazine publishes over 500 restaurant reviews every year, covers local events as well as writes original articles on local subject matter." This sentence is still a bit awkward.
• Remove "a lot of" from the sentence about Dreamweaver. In the next sentence "By moving away from that" can be changed. Perhaps just saying "By leveraging a modern CMS..." would be simpler.
• The sentence starting with "This was a particularly tough decision" uses "tough" twice.
• In the sentence starting with "Also, being a resource for local knowledge" you can remove "Vancouver and the Lower Mainland of BC" to simplify as the location is self evident. As well, vocab should be "Vocabulary".
• Instead of "inputted" use "entered".
• "automated scraping type application" wont be clear to many readers.
• The last two paragraphs in the "Rapid Prototyping section can be combined. As well, the last sentence can be simplified and/or split in two.
• While I laughed at "spooked", "form-zilla", "genius programmers" "I heart" I don't think they are consistent with the overall tine. Same with ending a sentence with etc. and :).
• For headings "A few" can be replaced by "Examples of"
• "Javascript Aggreygator" - typo
• Frontpage Feature Queue - is there any specific reason that this is custom developed when there are systems like Nodequeue? That would be my first question in the comments. :)

Great work Andrew!

The post is up on the front page so I'm closing the issue. Thanks for the perseverance with all of the edits!