How eMusic Transitioned From Clunky CMS To WordPress

eMusic LogoLinuxInsider.com has a great case study published from the CTO of eMusic.com, Richard Caccappolo on how the website transitioned from using a clunky CMS to WordPress. While reading the case study, the first thing that struck me was the following: “we found that WordPress was an ideal solution to suit all of our CMS needs.” Anyone who STILL thinks that WordPress is just for blogs really ought to change their mindset. While reviewing the different CMS solutions available, Drupal became a strong candidate but thanks to the persuasion of Scott Taylor who is the lead PHP developer for eMusic, they opted to go with WordPress instead. The case study goes on to describe tips on ensuring a smooth transition, why plugins are both a good and bad thing, and how eMusic decided to use bbPress along with BuddyPress to provide a more flexible platform for their community. After reading the case study, stop back and watch Scott give a presentation on the transition process from WordCamp San Francisco 2011. Watch in full screen mode to read the slides.

If you could ask Scott a question or two regarding the huge transition, what would it be?

There are 9 comments

Comments are closed.