Closed (fixed)
Project:
Drupal.org content
Component:
Case studies
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
12 Aug 2012 at 18:52 UTC
Updated:
29 Nov 2012 at 20:22 UTC
Jump to comment: Most recent
Comments
Comment #1
laughnanThe last node link doesn't link to anything -- hopefully meaning that it isn't needed.
The initial thing that I really liked about this case study was providing some very quantitative information regarding the switch in terms of views and visits to the site. How can we go about condensing the material into one case study however?
Comment #2
Tezza commentedHi Alex - You could try contacting jrockowitz. It was my intention to do so after the sprint but I must have got distracted.
Since the move the inline images have broken, which should really be addressed even without promotion.
If you ping him an email, update the queue and we'll sit on it while we wait to hear back.
Comment #3
jrockowitz commentedWow, thanks for starting the process of promoting my case study. I immediately noticed it in a Google search for mskcc.org.
There is duplicate version on my website, http://www.thebigbluehouse.com/case-study/mskcc. I would gladly spend the time to re-upload all the images and review all the links.
If possible I would like to keep my complete list of the contrib & sandbox modules. Any Drupal developer I have shared this case study was very appreciative of being able to see the categorized modules with descriptions. At same time, if the case study is too long, then it is too long and these pages should be first thing to go.
Thanks again,
jrockowitz
Comment #4
Tezza commentedHi jrockowitz
My personal opinion: It's long but it's all relevant, and it's a great candidate for promotion. It would be worth reviewing the sandbox modules to ensure their development status is current.
I'll IRC some fellow reviewers and get a second opinion and ask that the 'Posted by' name is changed from Tezza to jrockowitz.
If you could update the inline images that would be great, as it is a live case study in the Community Showcase, and we'll review it for promotion.
Comment #5
laughnanIt is a long case study, but such a great read! I look forward to seeing the adjustments!
Comment #6
jrockowitz commentedThanks for help with this.
My sandbox modules are only for Drupal 6 and will most likely stay this way, since I have not done much D7 work and MSKCC is going to skip D7 and migrate to D8 when it is released.
I see sandboxes as personal (and really public) playgrounds. I even took my personal development distribution, aptly called 'jrockowitz' and put it in a sandbox (http://drupal.org/sandbox/jrockowitz/1782266).
I am open to any suggestions. I will update the inline images as soon as I have access.
Comment #7
Anonymous (not verified) commented+1 from me, this is indeed a fantastic in-depth case study! One of the first links didn't work for me, the one to your old software, the rest seemed to work ok.
It would be good to also have a summarised version for the less technical reader, as the writer says you don't want to leave much out of the full one for the tech but we are trying to attract the less technical viewer too!
Great work,
Steve
Comment #8
jrockowitz commentedThanks for making me the owner of the document. I am about the head off long weekend but first thing next week I will upload the images and check all the links.
Comment #9
jrockowitz commentedI uploaded the images and inserted them back into the document. I removed the hand-coded list of contributed modules and updated the 'Key modules/theme/distribution used:' list. I tweaked a few other things to help it read a little better in the new format.
I added back in a link to "Take a video tour of Memorial Sloan-Kettering Cancer Center’s redesigned website" for less technical users. Admittedly, the video is not about Drupal but shows off a 'cool' site built with Drupal using fancy animations.
Comment #10
lisarex commentedGreat case study, and a great site. You've done a great job illustrating with screenshots. And wow, lots of contributions.
I made a couple tiny edits directly but you can see/ reverse them in the revisions if you want.
Can you add the year you compiled those stats?
Otherwise, +1 for promotion for me.
Side thing where I get really picky: And 112 views, that is the Views module, yes? Is that 112 different Views or 112 displays within Views? Either way, this figure seems a bit odd to me, both from the naming confusion, the fact it's sitting on it's own line, and that 112 Views sounds an awful lot; as in is that really true and there was no way to streamline the views using arguments.
Comment #11
jrockowitz commentedThe edits are fine. I changed 'Site Stats (Yearly)' to 'Site Stats (for 2011)'.
Yep, the site has a lot of views due to the number of content-types and related sub-displays. Also, there is custom admin only view for each content-type. The project started out using a very early version of Views 6-x.2.x which did not allow display ids to be changed or sorted in the UI and the process of overriding (and I think cloning) a display was clunky. So I went with the rule that if I needed to override more than 2 aspects (ie filters, sorting, fields, display settings etc...) of the default view I would create a new view. With this said, the ability to organize one's displays in Views 3.x is so much better, when I upgrade the site to D8, I am going to have to redo all the views and will consolidate them, ideally having one view for each content-type.
Comment #12
Tezza commentedI've made a few edits (and re-edits!) to correct some minor typos such as double words, capitalisation and hyphenation, and the like. Can't guarantee I caught them all - and hyphenation is such a mine-field, er, mine field.
Also, changed a few D7's to D8's where these referred to the next major upgrade.
All looks good to me now. When jrockowitz approves of these latest edits I would suggest this one is ready to go.
Comment #13
jrockowitz commentedTerry, your edits look great. Thank you for spending the time, giving my case study such a thorough review. If anyone points out anymore issues, before or after the case study is promoted, I will make the needed corrections.
Comment #14
lisarex commentedGood editing, Tezza (I'm too impatient to be a proper editor :))
Ready to be promoted
Comment #15
Tezza commentedand... promoted :)
Comment #16
tvn commentedGood job everyone!
Tezza, when promoting you also need to change "Authored on:" date to the date of promotion, so that case study would appear in the slideshow etc.
Comment #17
jrockowitz commentedWow, this is a total honor. I want thank everyone for helping. ~jake
Comment #18
Tezza commentedJake - thanks for writing and posting it. Hope you have the time to inform us in similar fashion of the D6 to D8 project when the time comes.
tvn - understood. I'll catch up on IRC one day this week.
Comment #19
jrockowitz commentedTezza - MSKCC.org is my main project so I am already starting to plan the migration (and the case study) to D8.
BTW, can you please change the 'Posted ... on August 12, 2012' to 'Posted ... on October 13, 2012' ... I am looking forward to sharing this news with the MSKCC project team.
Comment #20
lisarex commentedI've updated the date, so it's in the slide show and should appear on the homepage whenever the cache rebuilds.
Comment #22
Tezza commented