Hi there,

I would like to promote our The Telegraph Travel Guides App case study to Featured. The case study url is: https://www.drupal.org/node/2578227

Thanks a lot,
Andrea

Comments

Andrea Szell created an issue. See original summary.

Andrea Szell’s picture

Title: Promote [case study title] to Featured » Promote The Telegraph Travel Guides App to Featured
Issue summary: View changes
leighcan’s picture

Status: Active » Needs review
leighcan’s picture

Status: Needs review » Needs work

I like it. Really cool case study. Would you mind weaving some screen grabs into the text of the case study itself? There's an awful lot of text, so it would be nice to break some of that up.

Andrea Szell’s picture

Hi leighc,

Thanks a lot for your comments, I updated the case study by adding screenshots to the body https://www.drupal.org/node/2578227.

Please let me know if the case study requires further adjustments to get it promoted.

Best regards,
Andrea

leighcan’s picture

Status: Needs work » Needs review
leighcan’s picture

Status: Needs review » Needs work

Ok. Here's my feedback. What you have so far is good and there's a lot of content. I'd like not to add too much more text, but I would like more precision in discussing what's been done. For example

Under "Describe the Project":

For the backend development, we focused on using only one custom module (alongside building an internal tool that helps with caching, dependency injection, Drupal object handler - entity crud - adapter and more) and one feature module so that it can be easily maintained. This internal tool did most of the heavy lifting and provides functions that can be reused in our specific custom module. The combination of these tool/modules helped to improve the performance of the site for the editors/writers as the Travel Guides App handles a large scale of information to be presented to their users.

What does this mean, exactly? Can you get a little more specific about what the custom and feature modules do, and (more importantly) why they do it?

Despite the challenges that naturally come with working with a content-rich website, during the development phase we always endeavoured to make the UI as simple as possible without compromising the functionality and behaviour of the app. We considered various aspects such as navigation, layouts and the publishing process from the CMS to the app.

Again, I'd like a bit more clarity here. How did you make the UI as simple as possible? What does it meant that you considered various aspects? Were you focusing on accessibility? Ease of interaction? Simplicity of interface? Let's be really precise when describing what was done to make this site an outstanding example of what Drupal can do. The dashboards paragraph comes after this quote, so one way of phrasing it might be "we wanted an easy, user-friendly navigation that wouldn't bog our content editors down with unnecessary privileges, so we built two dashboards."

Near the bottom of the project section, Google spreadsheets comes up as an important aspect of their previous CMS. This really threw me for a loop, and I had to go back and reread several times to make sure I hadn't missed some mention of it earlier. So if you could elaborate a bit more about what the previous CMS looked like, what their pain points were, and how Drupal addressed those pain points, that would be a great addition to the "Why Drupal Was Chosen" section.

As a final note: When you've made the requested changes and posted in this issue requesting a review, please go into the issue metadata (under the text that says "add new comment") and change the issue's status to "Needs review." That's the best way to flag down a moderator to come take another look at your case study.

Let me know if you have any questions.

Best,
Leigh

Andrea Szell’s picture

Thanks a lot for your comments Leigh, will update the case study soon and get back to you.

Best,
Andrea

Andrea Szell’s picture

Hi there,

I am requesting a review based on the comments for tweaking this case study.

Thanks,
Andrea

Andrea Szell’s picture

Status: Needs work » Needs review
dddave’s picture

+1

Very good, in-depth case study.

leighcan’s picture

Status: Needs review » Fixed

+1 and promoted. Thanks for your patience.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.