Teaching Drupal CMS

Yesterday I took on teaching my friend Matthew about Drupal. We're helping with a project that, while there will only be a few users, seemed like a good fit for the platform. Normally my rule is that if you'll have a small team adding content then you should defer to a smaller CMS like WordPress, but this project will have a few more features just beyond what I think it reasonable for only WP plug-ins. It's not a tech project so I hesitate to think about custom development options.

I can't help but use the opportunity to log how I go about explaining the Drupal platform. First of all I'll mention that I've started with the Drupal v6.4 release. The v6 core has matured well, and many key building block modules have been ported to the new version. I went ahead and did the installation process, set up clean-urls, named the site, created a developer role with pertinent permissions, renamed the 'story' content type to 'post', created a taxonomy (category for v5 users) and configured some basic admin settings.

Admittedly, I softened the blow of dealing with Drupal. If you're setting up the platform for the first time then refer to your install and read-me docs, then return here for steps to discovery.

So step one, the first 'assignment'

1. Create a content type
2. Create a new taxonomy, assign it to a content type. 
3. Create a few pieces of content
4. Change the theme
5. Look at the module page
6. Set-up the primary links menu
7. Turn on and place a few blocks

Actually, I only stated step 1-5 explicitly. He did 6 and 7, so I added them to the list because he was right. I think this list give you a good idea about the structure and tools available in the Drupal system. The only pieces missing are the various admin functions of Drupal. There is LOTS of power in: error reporting, stat tracking, comment settings, url aliases, input formats, not to mention actions. Plus of course the power that comes with multiple user accounts. But I argue that to get started, you need to learn the structure-- take the user system for granted-- and bypass the plethora of admin settings.
I recommend before you install any modules learn: basic content types, creating content,
taxonomy, blocks, menus, user management, roles, permissions, core modules, and then move on to all the other admin stuff. Once you've bothered with things like tweaking your "post settings", changing the date and time, and choosing which content types display post information in your global theme configuration... then you can drop a new theme in and start installing modules.

I DON'T know about the project you have in mind as you read this, but might I recommend you go peak at: cck, views, imagefield, imagecache, (imageapi), pathauto, and token to start you on your Drupal journey. I said peak, not install. Be sure to read up and compare options before you roll forward. And one last piece of advice...

...Install modules one at a time. Test them out, set up the configuration, use them, and only then move on.