Promote 'Naxxas' Case Study to Featured

Hey all,

Thanks for submitting this case study. Unfortunately, my first impression is that it's pretty listy and reads a lot like a marketing whitepaper. There's quite a bit of grammatical problems in the case study, which I'm happy to edit for you, but I think the case study itself definitely needs a lot of work. I see barely any mention of the Drupal platform in this, and the list of product features at the end is unnecessary unless those features are a direct result of Drupal's flexibility, or directly integrate with Drupal.

I'd like to see more of a story along these lines: "The client built a product, and needed a website that could do (tasks a, b, and c). We realized that Drupal would be a perfect solution for them because (reasons x, y z). Our team prioritized the design around the following key features. Here's an explanation of why each of the features are important, and here's how we made them each happen with Drupal. Here are the problems we ran into, and here's how we solved them. Here's what our launch process looked like. Finally, the metrics speak for themselves: our client has seen (conversion increases, reduced page load time, etc etc)."

It's a cool product, but the case study itself is quite rough and needs to be reworked extensively. Let me know how I can help you with this process.

Cheers,
Leigh

Hi there,

I can see that you've added a bit more mention of Drupal, but it's still not clear how and why Drupal was used in the section where you discuss the actual project. Please revise your case study to address the following points:

Edits that should be made in Describe the Project:
In the "Describe the project" section, you talk a lot about the platform you built. Is this platform powered by Drupal (app) or is it hosted on a Drupal website? (I personally was unable to check, because the capcha would not let me register for the site.)

I am under the impression that video conferences run directly on the website. How did you make this happen? What modules did you use? How did Drupal make this easier? This is also something you can address in your Goals section.

Edits that should be made in Requirements:
Your "Requirements" section talks a lot about the platform, but not much about Drupal. This comes back to my question further up. Does Drupal power this service, or does Drupal only host this service? If Drupal powers this service, I want to understand how you built it. What modules did you use to meet your client's requirements? What features in Drupal made it easier?

If Drupal only hosts this service, you need to remove the information about the platform yourself, and instead focus on the website. This case study needs to focus on the Drupal website you have built.

Edits that should be made in the Engagement Overview & Project Management sections
Your "Engagement Overview: QA" section would be a good place to discuss your workflow. What tools (other than Jira) did you use? How does the Drupal CMS software make this easier, or how is Drupal incorporated to this process?

The "Project Management approach" section is fine, though it might be interesting if you talked more about the Drupal aspects of the staging server.

Edits that should be made in your modules section
Please list the modules that you used on this website. You say that you chose 'modules/themes/distributions' "To build a platform that provides multi-user conference call platform, with add-on features like scheduling future conference calls, providing alerts, recording conference calls for future playback etc."

This is the section where we expect to see the most detail. Please outline every module you installed, and how that module helped you build a better website. If you built proprietary modules, this would also be the place to discuss them.

Please revise your case study to address each of the points I have outlined above. Once you have made the requested changes, I will look over it again.

Best,
Leigh

We are working on cleaning up Drupal.org-related issue queues. Many issues have been open for years with no resolution because there were no volunteers interested in taking on the task or staff time available to complete the work.

We are going through old issues and marking them as Closed (won't fix). If you feel your issue has been closed in error, please do comment on the issue and let us know. If we know something is critical, we may reconsider the closure of a feature request or bug report.

Thank you for your understanding while we work to clean up the Drupal.org queues.

-leigh