Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
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
Comment #2
Andrea Szell CreditAttribution: Andrea Szell commentedComment #3
leighcan CreditAttribution: leighcan at Drupal Association commentedComment #4
leighcan CreditAttribution: leighcan at Drupal Association commentedI 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.
Comment #5
Andrea Szell CreditAttribution: Andrea Szell commentedHi 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
Comment #6
leighcan CreditAttribution: leighcan at Drupal Association commentedComment #7
leighcan CreditAttribution: leighcan at Drupal Association commentedOk. 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":
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?
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
Comment #8
Andrea Szell CreditAttribution: Andrea Szell commentedThanks a lot for your comments Leigh, will update the case study soon and get back to you.
Best,
Andrea
Comment #9
Andrea Szell CreditAttribution: Andrea Szell commentedHi there,
I am requesting a review based on the comments for tweaking this case study.
Thanks,
Andrea
Comment #10
Andrea Szell CreditAttribution: Andrea Szell commentedComment #11
dddave CreditAttribution: dddave commented+1
Very good, in-depth case study.
Comment #12
leighcan CreditAttribution: leighcan at Drupal Association commented+1 and promoted. Thanks for your patience.