Closed (fixed)
Project:
Drupal.org content
Component:
Case studies
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
9 Aug 2012 at 20:55 UTC
Updated:
4 Jan 2014 at 02:24 UTC
Jump to comment: Most recent
Peer 1 was a great client and definitely made the whole project go very smooth. We wanted to get our case study promoted because we thought it was great example of the type of work our dev team can deliver.
Comments
Comment #1
tvn commentedSite is looking good, definitely worth of Featured section. Case study however needs some improvements.
- Main image needs to have height of at least 440px
- Any community contributions you can list?
- "Describe the project (goals, requirements and outcome)" section is now just a list of "key functionalities" - it should describe the project better, it's goals, requirements, how it was built, what was the project management process and outcome.
Please refer to the guidelines for more field by field information http://drupal.org/node/1588136
Comment #2
timwelsch commentedHi tvn,
-We posted a better image to meet the 440px requirement.
-Unfortunately for this particular work we did not have any contributions that we could list.
-We added some new sections per your suggestions.
Comment #3
Tezza commentedBeautifully designed website.
For me, the case study is a bit light on detail. It reads well enough, and all the salient points are covered but not too many questions are answered. It's just a tad generic.
First thing I did was visit the site as soon as I reached the URL (just after 'Why Drupal was chosen'). Love the easeInOut(?) slideshow and the Our Customers widget. Love the way the top menu adjusts when I scroll down the page and its mega-menu stylee menu items. Love the three menu items half-way down the page. But returning to the case study I read nothing about these key features.
I know jQuery is not Drupal is not jQuery et al, but incorporating jQuery into Drupal can be a tricky business - more so, perhaps, with D6.
I know case studies are not a noobs training ground, but I'd like to see a bit more techie detail in the case study, perhaps to cover the above?
I dunno, the website is a fine example of inspirational Drupal, no doubt about that. Perhaps others will think that's enough for promotion. I wouldn't object, but it would be nice to learn something in the process.
Happy to grammar and spell check the case study when we're happy with the content.
Comment #4
Tezza commentedComment #5
Tezza commentedComment #6
timwelsch commentedWe've made some revisions to our case study over the last few months and would like to submit again for promotion. Also, thanks for the comments and feedback.
Comment #7
Tezza commentedI've had a read through the updated case study. Obviously, reviewing for Featured is not an exact science but I'm not sure the improvements - which are very welcome - are enough to tip the balance in favour of promotion.
The additions were necessary but pretty generic so I think it still lacks some detail, as per my earlier comment.
The website remains impressive.
I've corrected a few typos and some formatting.
Comment #8
Amazon commentedHi, I reviewed this case study. It's a great description of the benefits of using Drupal, and the business background that lead to the adoption. There's good technical description of popular contributed modules.
I think it's good to go for the front page. It's important that Drupal sites promoted to the front page reflect a broad range of Drupal adoption and they don't all have to be technical powerhouse sites or descriptions.
Comment #9
webchickI can see Tezza's POV on this. There are things in this case study that sound interesting to get more info on, but details are very light. (e.g. what sort of workflows are supported? what modules were used for SEO-friendly URLs? What CRM are they using, and how was it embedded? How was the integrated knowledge base constructed? etc.)
OTOH, Amazon's correct that it's nice to have a range of case studies, and it seems like this qualifies in terms of the profile of the company. And I suppose if people have specific questions about how this or that feature is implemented, they could always ask in a comment on the case study.
Therefore, tentatively marking RTBC. If no objections, I can go ahead and promote to featured in a couple of days.
Comment #10
Tezza commentedPromoted :)