Case study url: https://www.drupal.org/node/2513096
Hello Webmaster,
In order to Contributing to the Drupal community, we have written a Leading Case (attached file) of the project University of San Andrés (UdeSA).
In Tooit we believe that this case can be useful information for other developers that want to build websites with Drupal for organic institutions such as, educational institutions, government agencies, etc.
Using modules like OG and Workflow in combined way, is a model that we discover very powerfull for Content Management Systems in large organizations.
Please, we ask for a review of the case, because we consider very important your support at this stage of the project.
Thank you in advance
Luciano Caccia
Co-Founder at Tooit
Comment | File | Size | Author |
---|---|---|---|
Udesa-leading-case-EN.pdf | 2.12 MB | luciano.caccia |
Comments
Comment #1
leighcan CreditAttribution: leighcan at Drupal Association commentedThe case study has a lot of info about what Tooit did, but I feel like it's light on content about what Drupal did. Can you talk a little more about your methodology and how you worked with Drupal in the process? How did Drupal uniquely address the site needs?
Ultimately, I'd like to see more information on why this is an exceptional Drupal site. Also, there are a few typos that could stand to be corrected.
Comment #2
luciano.caccia CreditAttribution: luciano.caccia commentedThank you Leighc,
It clear your point. I will change the approach of the content and request a new revision.
Thank for yours advices
Comment #3
leighcan CreditAttribution: leighcan at Drupal Association commentedHi there,
I'm going to go ahead and close this issue due to inactivity. Feel free to reopen it once you've made the suggested changes to the case study.
Best,
Leigh
Comment #4
luciano.caccia CreditAttribution: luciano.caccia commentedHi Leighc,
Sorry about the delay, but we were busy the last weeks.
I updated the content bearing in mind your advices.
Please, Could you review the case again?
Thank you so much.
Comment #5
luciano.caccia CreditAttribution: luciano.caccia commentedHello Webmaster,
Could you check the updates in this post please?
Thanks in advance
Comment #6
leighcan CreditAttribution: leighcan at Drupal Association commentedHi there,
I've looked over this. There are some structural changes I plan to make within the next week or so. I am currently traveling for work but should be able to find a few spare minutes to edit this case study soon.
Thanks for your patience.
-Leigh
Comment #7
leighcan CreditAttribution: leighcan at Drupal Association commentedHi there.
I apologize for the delay in getting this back to you! Thank you for your patience.
I went through and made some corrections but ultimately, I came away from this case study with a lot of questions. The whole thing feels very disjointed, more like a list of features and modules without any context as to why you did what you did. In the next round of edits, I'd like to see more of a story (problem/solution/outcome.) For example, what were the client's needs? You say that you need a site that's mobile-friendly, that has organic collaboration tools and a content approval workflow. But there's mention of different products, and of tools that support various methodologies. Perhaps you could do some re-structuring so that the case study reads more like this.
1. Description of the general problem. (Example: the client needed a mobile-friendly site with strong editorial workflows, that could support numerous academic departments.) This is a good place to lay out the research you did with the Comms department and what your findings were.
2. Description of how you broke the problem into smaller chunks. Did you use agile methodology? Did you use scrum? Sprints? How did you break those sprints up? This would be a great place to elaborate on the work plan that you presented to the Board.
3. Descriptions of how you solved each of the problems. This could look like:
4. Results. This can be a recap of the client's satisfaction, whether you saw interesting upticks in any of the KPIs, etc.
Ultimately, the featured section is a showcase for websites that do really amazing things with Drupal. I'm sure that this site does do amazing things, but we need a clearer picture of what it does, how, and why that's incredible.
Thanks.
Comment #8
leighcan CreditAttribution: leighcan at Drupal Association commentedHi there,
Due to inactivity, I'm closing the issue. Please feel free to reopen it once you have made the requested changes.
Best,
Leigh