Case Study: Packt Publishing

Hi Julian - The front page schedule is a little dominated by DrupalCon this week, but we'll be sure to review this after that's over.

I've gone through and made some formatting changes and added optimized versions of the images to the post.

I see a couple of references in the comments to some performance issues and a request for more information on the shopping cart configuration. I'd also like to see more language about how and why Drupal was chosen for the project.

If you'd like to edit the post to make those changes, just post an update here, and we'll change the input filter on the post so you can make further edits to it.

Hi Julian -

Are you planning to make further edits to the post so that it can be considered for front page promotion, or should I close out this issue?

Thanks Julian -

I've changed the input format back to "Filtered HTML" so that you can edit the text of the case study if needed; in particular, as I mentioned above, some more language about how and why Drupal was chosen for the project (given that Packt publishes books on a wide variety of open source content management platforms) would be great.

I've reviewed and tweaked the changes and turned on Full HTML format. I think this case study looks great, and it gets a +1 from me, but I would feel better about it if someone from Packt or the development team could respond to the concerns raised about performance in the comments, specifically http://drupal.org/node/776740#comment-2885266

Once we get a +1 from another site maintainer, I'll be more than happy to add this to the front page promotion schedule.

@gdemet I can followup on my earlier comment, which you reference. Packt and/or their supplier seems to have done a good job fixing (most of) the performance issues with the site. Unability to connect no longer seems to appear, and authenticated response times, while still rather slow (more than 5 seconds to fetch a page once authenticated) are no longer critical like they were at the time I did this comment, and are now actually usable.

Note that although it is no longer critically slow, Alexa stills classified them as very slow, 89% of all sites being faster.

@fgm: That's great to hear! If you or someone at Packt could post a reply in that thread letting folks know that the situation has gotten a lot better since that comment was made, I think it would clarify things tremendously. Right now, there's no indication the issues have been fixed, which could reflect poorly on Drupal's reputation running high-performance sites.

@gdemet: comment added in the other issue.

@julianpackt: yes, we should be. Hopefully presenting the redesign of Le Figaro.

The response looks good to me, and now we just need a +1 from another site maintainer/webmaster to get it on the front page schedule.

+1

Promote this.

Thanks Bill! It looks like there's a DrupalCon Copenhagen story that's been added to the home page schedule for today, but I haven't seen any mention of it in this queue. I'll follow up with some Copenhagen folks to see if we need to promote that story today, which would push this case study to Thursday or Friday; otherwise I'll promote it today.

The Copenhagen story will be ready to go in an hour or so.

I'll create an issue and link to it from the front page schedule.

Putting this on the schedule for Friday, 6/18.

Promoted.