nutshell.nu

I completely agree. In many aspects, such as those Jen Lampton is pointing out in the slideshow below, WordPress simply is better than Drupal. Same goes with Joomla as well.

Jen starts by comparing numbers, showing that WordPress has more installations, more modules, more themes and a much larger community. Then she goes on with telling you why its better, what Drupals problems are and rounds off with what the Drupal community needs to focus on.

In my First Impressions of Drupal 7 alpha 6 post, two weeks ago, I wrote that I was planning to update Nutshell to the new alpha. Unfortunately I haven't done that yet. This is mainly due to that I am involved in several large website projects and simple haven't had the time for it.

I routinly go through the Drupal logs here on Nutshell, mainly checking for any potential error messages for Drupal 7. Today when I had a look I noticed a big spike in the Mollom statistics. Yesterday there where 30 atempts to comment spam. Naturally I had to look further into it since I am just running small blog and that single spike doubled the total number of spam atempts since I enabled the Mollom module a month and a half ago.

The Drupal community is at the moment mainly focused on fixing the beta blockers for Drupal 7. The list on the Drupal core improvements page currently only list this ONE issue needed to be fixed for the upgrade path. It also lists THREE security issues. When those four issues have turned green the first Drupal 7 Beta will be released. We are very close now.

Drupal is doing a fantastic job with separating content, structure and design for websites. However, when it comes to developing a Drupal website, especially adding new features to an existing website, you will undoubtable run into issues that will require a lot of extra work.

Normal practice is to have a development server where you develop new features. Then you make a test implementation on a staging server. Finally, when everything have been thoroughly tested, you implement it on the production server.

One thing that fuels the power of Drupal is all the small focused modules that exists. These modules are absolutely lovely to work with. Not only do they almost always solve the task they are developed for perfectly, but also because they add very little, if any, complexity to your projects.

This time I have taken a look at contributed modules that improves your control over input and presentation of content. Many of these modules are also great for better SEO of your website.

There are some people in the world that has that rare skill of really being able to reach out and get you to simply understand that there are a bigger picture you need to pay attention to. Hans Rosling is such a guy. The way he takes boring statistics and turns it into something that makes you pay attention is amazing.

He gives you a view or how the world is transforming in a way you never going to get by just watching you normal newscast.

Often when I browse the web and stumble on a website that looks to be built using Drupal I usually take a look at the source code for it. Way to often I am then facing a wall of links to CSS files and JavaScripts. This is not only true for small sites, I have seen it on big popular websites as well.

Then I am thinking - How in £#&% can they miss the Performance settings that Drupal comes with as standard?

This morning when I, as usual, got online to check Nutshell I was greeted with with an ugly holding page saying "Your website is NOT YET AVAILABLE". Between I went to bed last night and this morning the hosting company had made a serious $%&#-up and started to redirect all our websites to their default holding pages.

E-mail, ftp and other services seemed all to work just fine, only the websites where affected.

Before Drupal 7, managing media files often turned into a nightmare, both to implement and then use on the production website. There are countless of modules, especially for Drupal 6, trying to solve the problem. Many of these modules are good for what they where intended to do, but they often lack features or are not flexibility enough to be deployed on different websites. Often you are forced to use more than one solution, ending up with a different user interfaces depending on the media file and so on.