Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
Case study URL: https://www.drupal.org/node/2577849
Website URL: http://forestparkmap.org/
Hello,
I'm requesting a review of the Forest Park Map Drupal 7 website case study I created.
We created the website as a single page web app that showcases one of St. Louis' greatest treasures: Forest Park. The responsive, GPS-enabled map uses Leaflet and relies on Drupal's core caching and AJAX framework. We had some requests in the Reddit community for a detailed case study. Let me know if you have any questions or comments.
Thanks for your time!
Daniel
Comments
Comment #2
leighcan CreditAttribution: leighcan at Drupal Association commentedHi there,
Sorry it took me so long to get to this. It's a good start but I'd just like more of everything. Why did the client decide they needed a new website? What were the results? If you could tie building the site back to some of the experience you had in your MIT case study, that would be great.
Thanks,
Leigh
Comment #3
Daniel KorteHi Leigh! Thanks for your review. We've added some more content addressing your questions. Please take a look! Thanks again!
Comment #4
leighcan CreditAttribution: leighcan at Drupal Association commentedHi Daniel,
It's still feeling a bit sparse under the "Why Drupal" section. I understand why your organization chose to work with Drupal, but I'm still wondering why the park felt they needed a new site, what those needs were, and why Drupal was the best CMS for the job. So, for example, you could illustrate this point by saying,
"Forest Park needed a lightweight, responsive website to help visitors navigate the park. Drupal’s location node views allowed TOKY to load the exact data required for each user action with nothing extraneous, etc etc."
Essentially, I'd like a little more explanation around they "why" of the project. Why did the client need this? Why did you do the things you did? When I look at promoting a case study, I look at:
What were the pain points
How did Drupal meet them
How were the solutions implemented
Right now I'm not seeing much of the first bullet -- we have lots of information on the solutions, a little information on how Drupal does the thing, and next to no information on why this was necessary. For promotion into the featured section, we need to understand why the website was built (needs, challenges, etc) in order to really illustrate that Drupal is an amazing solution.
Let me know if you need more help or deeper explanations.
-Leigh
Comment #5
Daniel KorteThanks for reviewing Leigh! We've restructured and added more content. Let me know what you think. Thanks!
Comment #6
leighcan CreditAttribution: leighcan at Drupal Association commentedI love it. Great changes. After reading this case study, I want to go to the park and use the website as I wander around. Really well done.
Now all we need is a +1 from the community and we can promote to featured. Really fantastic work, Daniel.
Comment #7
Daniel KorteYou should! :) Thanks a lot!! Really appreciate it!
Comment #8
dddave CreditAttribution: dddave commentedBig time money! +1
Comment #9
leighcan CreditAttribution: leighcan at Drupal Association commentedThanks for your patience, Daniel! You've been promoted to Featured. You should show up on the front page of Drupal.org by the end of the day.
Best,
Leigh
Comment #10
Daniel KorteAwesome! Thanks everyone!