BBC Magazines is the
magazine publishing division of the British
Broadcasting Corporation (BBC) and it seems that according to Dries Buytaert, BBC has used Drupal for a number of their online publishing sites:

• BBC Music Magazine
• BBC Countryfile
  Magazine
• BBC Focus Magazine
• BBC Who Do
  You Think You Are Magazine
• BBC History Magazine
• BBC Home And Antiques

Recently our agency here in Singapore has finished the first phase of a major publishing site for Expat Living. Work is underway to improve on the overall experience and feature list.

Drupal rocks! 

2 times consecutive winner, Drupal content management system has done it again! According to this CMS Report 'Drupal was announced the winner in Packt Publishing's 2009 award for Best PHP Based Open Source CMS. Instant replay at the finish line may have been required as Packt reports that Wordpress and Joomla! were not too far behind the leading CMS.'

According to an article from Packt Publishing, Drupal, the platform that Ad.WRIGHT team is very competent in, day in... day out... is voted the best overall Open Source Content Management System. That is great news for our Ad.WRIGHT team and at the same time, great news for our customers!

Here are some of the excerpts:

After three intense months of voting, Packt Publishing can today announce that Drupal has won the Overall 2007 Open Source CMS Award. With 18,000 votes on Packt’s website, coupled with the expert opinions from a panel of judges, Drupal succeeds Joomla! as the overall winner and receives a cheque for $5,000.

Joomla! and Drupal occupied first and second places in 2006, with their quality proving to be popular with the judges again this year. Joomla! retains its position in the top three, coming second and winning $3,000, with CMS Made Simple in third collecting $2,000.

Initially released in 2001, Drupal has grown to become one of the most downloaded Open Source Content Management Systems with one of the most enthusiastic and committed communities. "This is a great honor for the Drupal community and the thousands of individual developers who've contributed to the project" confirms Drupal developer and core contributor Jeff Eaton. "We've worked hard to make Drupal as flexible, as scalable, and as accessible as possible. It's a great week for all of Open Source; the winners in every category have shown that OSS can produce powerful solutions for a wide range of needs" he concludes.

On choosing Drupal... Harvard Science site recently went through a revamp and decided to go with Drupal platform for the development.

Here is a little excerpt on the process:

Choosing a CMS
During the six months before I began building the HarvardScience site, the Harvard News Office had been working with designer Claudio luís Vera of Studio Module. The result was 28 beautiful templates, which had been chiseled, filed, and polished to the client's adoration. Unfortunately, during this time the News Office had still not made up its mind about what CMS to use. In fact there was still some muttering about how a custom CMS was the way to go.

So approximately six months ago, I built the first draft of HarvardScience using Drupal over the course of a weekend. The result was exactly what I had hoped for - the news office was so excited by the speed at which the site could be built they decided to go with Drupal. The rapid development of a prototype or draft site can be built using Drupal made the CMS issue a fait accompli strategy.

The sIFR Drama
My first draft of the site did not use any of the mark-up, styles, or sIFR that the designer had provided. I instead created my own custom theme, relying heavily on blocks and views. I had assumed that if the site looked very close to the original design and that the CMS was in place, everyone would be happy. This was a huge error on my part. The designer had been working with the client for nearly six months at this point, and everyone had become wed to the "Whitney" font used heavily throughout the site. So despite a devious experiment on my part proving that the client couldn't tell which page used sIFR and which did not, I was asked to go back and add Whitney into the site.

Thus began draft number two. I installed the sIFR module Jeff Robbins and began to add in the style I had originally left out. The module itself is super easy to use. Sadly I didn't find sIFR2 so lovely. Regardless how much I fiddled with font-size, letter-spaceing, padding, margins, height, and width, I could not get consistently sized sIFR text replacement. I was informed by the designer that if I moved to sIFR3, which was still in beta at the time, all my problems would go away. In short, at the end of this draft, everyone was pretty frustrated - most of all me.

Thus began draft number three. This time I did what I should have done to begin with. (What is that saying about hindsight?) First I threw out the theme I had built. Next I grabbed the directory the designer had used to store all his stylesheets, flash, javascript, and images to run his 28 templates, and stuck it at the root of my drupal install.

Next I copied the mark-up from one of designer's templates, and named it page.tpl.php. Then piece by piece, I replaced the static content with nodes, views, and blocks - themeing as I went - ensuring that Drupal spit out the exact same mark-up as the original template. So after a very long journey through the land of sIFR, the site emerged as the designer originally intended.