You might be wondering why we are using drupal when we speak so much about Python. I shall enunciate the reasons for the same in this post.

When we started off with the website we had the option of choosing among the various available CMSs namely, Plone, Drupal, Joomla and so on. There was also the option of going with Django, which we discarded because most of our site would be static and we thought it would be too much work to do for a static site. We chose Plone, the reasons being, its written in Python and we had seen quite a few websites that ran plone like plone.org and Connexions. It took us a couple of days to figure out stuff and get the basic site up and running using Plone. Thats when the problems started. Maintaining a plone site a great pain. Firstly, Plone is a beast! Its a package of 34MiB which comes with its own Python2.4 and Zope server. Installing Plone is not a difficult task I must say. But the problem starts only after the installation. Every time a new module has to be installed, the module tarball has to be downloaded and extracted to the Plone src folder, then the buildout.cfg has to be edited, which in itself is a great pain and then the buildout script has to be run. Then the zope server has to be restarted. All this just to make the module appear on the Plone administration set up page. The installation is complete only after the module is selected for installation on the set up page. The plone docs say that the module should get installed by just specifying the url to the module tarball if they are under pypy or plone itself. But this procedure doesn't work most of the times. The documentation for most of the modules is sometimes misleading and completely non-existent most of the times. Also most modules that might come close to being useful are usually in the alpha or the beta releases and hence are buggy and lack support. If some of you have visited this site before, then you would've experienced the messy and the cluttered interface. Also adding content on to the site was non-intuitive to say the least and a huge pain in the backside to say the most. Hence we decided to do something about it.

We decided to work on improving the plone site and if it was completely impossible to do it then ditch plone and take up alternatives. So Shantanu, PR and me started looking for alternatives. In the meanwhile I did try to tweak the plone site a little but I was more inclined on trying something better. We looked at Pinax and Django-cms. Pinax is too social-networking-site-ish and we felt that the django-cms installation procedure was too cumbersome. So we reviewed our options and considered drupal as well as wordpress this time. Since
I had some experience with drupal, I suggested that we go with drupal, since I had some experience with its working. I worked for a couple of hours to set up a basic site on my local machine, just as a demo and PR was quite impressed with it. Shantanu and Puneeth provided valuable input on the necessities of the website and its basic design. Once this was set we started out with the actual website. PR and Asokan gave their reviews with inputs about what they want from the site. Thus we went on to develop the website

Working with drupal is very simple and instinctive. Drupal provides an interface that is uncluttered and quite uncomplicated to navigate through. Also drupal has a whole suite of modules that provide scale the functionality of a website to great levels. Also it has an amazing set of beautiful, eye-catchy themes. And the best part is that configuring all these modules and themes is straight forward and doesn't involve complex stuff like editing configuration files remotely or running complex scripts. Its all done on the browser. Also drupal has amazing support in the form of simple, easy-to-understand documentation as well as an amazing community with people always ready to help on #drupal-support. All these factors led us to choose drupal.