In our CMS test I will have 6 type of users.

1. Super Administrator:

Responsible for all the aspects of the site, create/delete/edit/publish/unpublish content, change themes and create or edit other users

2. Site Administrator:

Responsible for create/delete/edit/publish/unpublish any content from the site, change themes, create or edit other users but is not able to change the layout of the site.

3. Author:

Creates/edits/publish/unpublish own content.

4. Editor:

Creates/edits own content but can't publish the content, they notify the Site Administrator to do so.

5. Subscriber:

Receives notifications when site content changes and is able to comment on content if content is enabled to receive content.

6. Visitor:

Access to all content that is published but is not able to edit any part of the site

WordPress and Drupal do a good job in allowing you to create different kind of users and this is where we start to see some separation between the two systems and this might be one of the main reasons why you may choose one after the other but lets see them in detail:

WordPress:

WordPress comes with 5 predefined roles (or user types) and one user, WordPress has a page that explain the roles in great detail but lets see their "Summary of Roles"

• Administrator - Somebody who has access to all the administration features
• Editor - Somebody who can publish posts, manage posts as well as manage other people's posts, etc.
• Author - Somebody who can publish and manage their own posts
• Contributor - Somebody who can write and manage their posts but not publish posts
• Subscriber - Somebody who can read comments/comment/receive news letters, etc.

This is great specially when you are starting and you want to create your content and define users rather quickly. In the default installation since I was the one installing the software I was automatically added as a site Administrator.

I went ahead and created the different users that we need and with WordPress was a breeze since the roles were already defined as an option.

There was one major issue with the default set up and that is the Administrator role could not be edited in a way that the role was not able to edit the layout of the site. So I still wanted the site administrator to have full control of the site content and users but not to have control of the layout. I am sure I could go into the database and alter this setting by creating a new role and applying new rules but for this experiment I am not going to go that far. I went ahead and did a quick search in Google for a plugin or similar that would allow me to create custom roles and there were about 21,500,000 results on my search (wordpress+custom+roles), so it seems to be some sort of demand for the feature.

Drupal:

Drupal has 2 predefined roles and one user each of the roles are explained within the role's page:

• Anonymous user: this role is used for users that don't have a user account or that are not authenticated.
• Authenticated user: this role is automatically granted to all logged in users.

Here is where we start to see a small gap between WordPress and Drupal. Drupal allows you to create custom roles where you can define and alter the different access levels for the users. Drupal starts to show some "muscle" here by giving you different categories for User Management, such as Access rules, Permissions and User settings.

Creating roles has a lot of advantages because you can customize exactly what each user is allowed to see and do, but also you are responsible for what you allow the user to do. It is a good idea to create test accounts that will allow you to see what the new role will be able to access.

One more benefit for Drupal users is that you can customize the different emails that the user is going to recieve when new accounts are created, forgot password, no approval required, awaiting approval, blocked email and deleted email. For many of us this might not seem like a huge benefit but if your CMS is going to have your (or your client's) personality, it is great to see that you can customize these type of details.

If the administrator creates a new account you have an option to notify to the user of their new account, WordPress doesn't have this option.

We can see how both systems have their own way of handling user management and it is evident that when it comes down to a robust CMS where you need detailed user management Drupal gives you the flexibility you need. WordPress is the "out-of-the-box" solution that allows you to create predefined users, in a blogging environment this is perfect but for a more complex setup you will need to rely on plugins or hack the software directly.

to be continued (templates)

Creating content in Drupal

Creating content in Drupal is very straight forward and I really like how they explain each default section. Immediately you can tell Drupal is not worried about winning the Blog wars since they do not even have a blog option as part of their default system. Although you can use the "story" as a blog post ("and informal blog-like entries may all be created with a story entry. By default, a story entry is automatically featured on the site's initial home page, and provides the ability to post comments.") and they also have a Blog module but is not one of their default settings.

Here is the default view for a Page in Drupal, straight forward that allows you to enter the Title and Body of the page. One draw back on this default interface (at least in my point of view) is the simplicity of the page, we do want simplicity but right of the back you cant upload pictures or have a pretty interface that you can use to edit test, which a lot of people have been accustomed to. Again, that is my point of view as if I were to give this application to a client as it is they probably would feel the same way.

On this page you can also allow the page to be part of the main menu or leave as is and you can enter HTML (something that can be changed and more about that in a different post)

You also get to create the revisions for that specific page and view/revert in the future if you desire to do so.

It is important to note that as these settings are optional and you can turn them on or off depending of your specific needs for the content. You also get a preview of the page with all the edit section at the bottom of the preview and then you can save to make your page live.

Creating content in Wordpress

WordPress is a content-creation machine, as soon as you login to the dashboard you can do a quick-post which is similar layout to what you find in Drupal but immediately you are able to also upload media such as images, video, sound or media in general. Right away you can tell why WordPress is so "loved" in the blogging community.

But again, I need to create a page and that is one of the options in the main navigation bar. Create pages is 2 clicks away (1. Pages and 2. Add New)

Some of the features in WordPress is that you have the usual interface when creating content even with spell check. Which it was not available by default in Drupal. Also you are able to switch from Visual and HTML for the users who want to take advantage of that functionallity.

Another nice feature is that WordPress will save Drafts as you are editing your Pages, which allows you to keep the content you are working with in case something goes wrong with your computer, lose internet connection or are in the run.

You also are able to upload media in this section and create custom fields. Custom fields are used for more advanced site layouts that need this extra information to make your layout unique. Here is some information about custom fields. Can we create custom fields in Drupal? Absolutely but we are just covering the default behaviors in WordPress at the moment.

One more thing that WordPress does well, is providing feedback and information that to some might be overwhelming but that it is informative for the user such as word count and when the last draft was saved.

You can preview your changes which will be launched in a new page with your theme in a very realistic manner. Drupal does something very similar but all the editing tools live under the items you are reviewing.

Continue to WordPress VS Drupal User Management

On the other side I also had to create a file in WordPress directory. Here are the steps on more detail

WordPress Installation

1. Download Wordpress
2. Upload to server with FTP program
3. Duplicate/Rename wp-config.php file (you can also let WP do this for you)
4. Update settings in the file such as Database/Login credentials
5. Add new Authentication Unique Keys*
6. Enter Blog Title and your email
7. Receive your Username and Random password.

*It was nice that WordPress has a site dedicated in creating those unique keys and no way around it, once you hit the site you get the set of key numbers you need and continue working.

Drupal Installation

1. Download Drupal
2. Upload to server with FTP program
3. Create 2 files and set permissions to them (settings.php & /files)
4. Enter database information on online form
5. Submit Username and Password for admin and set some other basic settings such as site name

Here you have it, the installation in a few number of steps for more advanced users. Granted, for some one that has never installed any package maybe you will have to browse around and find answers to basic questions but in the end you should be able to acomplish the same task in this few steps.

Continue to WordPress VS Drupal Creating Content

To start let me give you some of my professional information so that you know who I am and where my review is coming from.

12+ years in Web Development
WordPress user since 2003
Drupal noob since April 2009 (about 5 days at the time of this writing)

Programming Languages and Frameworks that I either use or I have experimented with: ASP, PHP, AS(1-3), Flex, Objective-J, JQuery, JQueryUI, CodeIgniter, Kohana (fork of CI), Zend Framework, AMFPHP, HTML, XML, JavaScript, CSS, and more...
Online packages that I have worked with: Wordpress, b2b, MovableType, Habary, Mambo, Joomla, SugarCRM
I would also like to note that I have created my custom CMS for clients, couple have been done with pure PHP and some with the aid of a framework such as CI, or Kohana. Also I have been fortunate into creating CMS that would have Flash front end and PHP/Framework backend.
Writer: 0 experience, just my blog .

(Disclaimer: I am not here to defend the packages themselves)

Now with that aside, I want to take a minute and put WordPress VS Drupal in a small duel where I will register my findings and give some feedback in different aspects of both pieces of software such as installation, upgrading, templates, 3rd party elements integration and whatever else comes along.

Continue to WordPress VS Drupal Installation

Here is a sample as a reference:

#!/bin/bash
# Convert all mov files into flv
counter=0
mov=flvMovie
currmov=$mov$counter
ext=.flv
for file in *.mov; do
let counter=counter+1
currmov=$mov$counter$ext
ffmpeg -i $file -ar 22050 -f flv -ab 56 -aspect 4:3 -b 200 -r 12 -s 320x240 -ac 1 $currmov
done

Next time you start a new task ask yourself, Is this really going to help me accomplish my original goal?

Enjoy!