Closed (fixed)
Project:
Drupal.org content
Component:
Case studies
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
2 Sep 2012 at 19:30 UTC
Updated:
4 Jan 2014 at 02:24 UTC
Jump to comment: Most recent
This is an interesting one:
https://drupal.org/node/1765996
Would like to hear what other reviewers think about it.
Comments
Comment #1
tvn commentedI think it's interesting specifically because of it being Ipad app. The content of case study should be rewritten a bit. "Why Drupal was chosen" and "Brief overview" contain most of the info which better fits into "Describe the project". Tags like h2, h3 can be used for headings to make text a bit easier to read. Also I'm not sure if it's accurate to call Acquia the commercial entity for Drupal.
Comment #2
tvn commentedComment #3
Anonymous (not verified) commentedInformation re-organized and header tags added as suggested.
Comment #4
Tezza commentedOk, Isabel, I'll do a full review later this week and report back.
Comment #5
lisarex commentedSeems like a really well-written case study. I saw only one minor missing comma, but Tezza's review will pick up on that.
Two other things:
Comment #6
Tezza commentedLookbook lookbook Look Books - mixture of uses
ELLE DECOR Elle Décor - mixture of uses
In "Sharing CLBs via Social Media" you mention Auth. Is that correct or should it be OAuth? Either way if it refers to a module it's best perhaps to say "the Auth | OAuth module" and to include it in the module list.
I've made a few tweaks to the text and, here and there, added commas and parentheses to avoid ambiguity.
Please reply when you've reviewed the latest edits and have considered the comments mentioned above (mixed case and Auth) and those made in #5.
Comment #7
Tezza commentedComment #8
timwelsch commentedJust like the other case study we submitted, we've made some revisions to this one too over the last few months and would like to submit again for promotion. Also, thanks for the comments and feedback.
Comment #9
Tezza commentedMy comments in #6 have not been addressed, so there's that!
What is 'a 5 ECU server size'? Also, written the way it is it doesn't follow the "The Acquia Cloud comes with:" introduction.
Finally, you might want to pick a sector or two so that the case study may be found through 'Browse by category'.
I made a few small edits to correct some discrepancies.
Comment #10
Amazon commentedI've reviewed this case study and it looks good.
I elaborated on ECU and gave a link to the definition.
I changed "The Acquia Cloud" to Acquia Cloud as I thought it reads better.
I clarified the technical and service levels for upscaling and managing a server size increase to be more accurate.
I added the publishing category to this list.
I reached out to the author about Lisa Rex's request for images with a consistent border. However, I don't think that should hold up the publishing of this case study to the front page. I'll try to get clarification or link to the Auth module which I believe must be Oauth.
Comment #11
Anonymous (not verified) commented+1 from me, great case study! Would be good to get auth/oauth issue addressed first though. Agree images could be nicer with consistent border but also agree it's not a show-stopper.
Comment #12
webchickOK, sounds like there's consensus here. Promoted to featured.