Holy instant website, Batman.
Drupal is something I've been meaning to play with for a while, but it took Sam Tresler's Barcamp presentation on Instant Drupal to get me started. He turned a static site into a dynamic Drupal one as we all watched; I decided to take notes and follow along. An hour and fifteen minutes after the presentation started, I'm sitting here staring at a new website for the Olin SWE Chapter on my laptop (as of this posting, the site is not live as I need to get it over to an Olin webserver... but Simone and Kate, if you're reading this, I finally got off my butt and moved.)
I'm officially sold on this thing. I'm still planning on having a CMS Tryout Weekend for OCP (the Open Content Project, Olin's open source/content group) - probably right at the end of term, since we have some events (Linux installfest, roll-your-own-distro party, Python GUI eval party) coming up first. But I'm very impressed by Drupal because it seems very easy to teach non-coders how to admin it - incredibly vital because it means the groups you set up Drupal websites for can become self-sufficient quickly and not have to call you for tech support forever.
Here are my notes on the session, which should walk you through setting up your own Drupal site (downloading included) in an hour. Thanks, Sam!
Here's Drupal's homepage. It's technically a CMS, but Sam prefers to think of it as a web development framework.
Download and install
Download the latest version of Drupal and unzip it into your htdocs folder (inside your xampp installation - my path was C:xampphtdocs.)
Set up your database
- Go to http://localhost/phpmyadmin to see your local phpmyadmin page, thanks to xampp.
- On the main phpadmin page, there is a section labeled "create new database." Type the name you want to use in and make yourself a mysql database.
- Make sure your new database - we'll call it mydrupal in this example - is selected in the drop-down box on the very left hand side of phpmyadmin. On the main screen you should see a list of tabs, one of which is labeled "SQL". Click it; you'll see a text box labeled "Run SQL query/queries on database mydrupal."
- Inside your htdocs/drupal folder there's a file called INSTALL.mysql.txt. Open it up and copy the line that begins "GRANT SELECT, INSERT, UPDATE, DELETE, CREATE..." into the "Run SQL query" textbox in phpmyadmin, changing appropriate variables. In our case, we're going to replace databasename, username, and password to mydrupal - but you can set them to whatever you want as long as you remember them.
- A few tabs down from "SQL" in phpmyadmin is a tab called "Import." Go there, click the Browse button, and point it towards htdocs/drupal/database/database.4.1.mysql (this will work for most cases - check the end of htdocs/drupal/INSTALL.mysql.txt to make sure you've got the right one) then hit the Go button and watch lots of tables be automatically created.
- Open htdocsdrupalsitesdefaultsettings.php and set $db_url and $db_prefix lines to the database you created (replace 'username', 'password', and 'databasename' with what you set; unless you explicitly set a mysql prefix during database creation, leave the $db_prefix untouched.) In our case we're going to change them all to mydrupal because that's what we used two steps ago.
And you've got Drupal.
- http://localhost/drupal should work now. From here on out, the interface is fairly self-explanatory and can mostly be guessed at, but here is some stuff you will want to do.
- Create an admin account; there's a link on your drupal install's main page to do this. You'll probably get an error message that says it couldn't email your password to you; ignore it.
- Go to administer > settings and fill in the forms with your organization's information. You may want to turn on "clean URLs" to get rid of extraneous php syntax in your urls, but you don't need to.
- Cache settings: Also in administer > settings. For development, keep it disabled. When you go live, you may want to enable it so that the webpage won't dynamically generate every time it doesn't need to.
- Save before you test your new settings; Drupal settings don't take effect unless you save.
- The default Drupal settings are pretty good. If you don't understand something, you probably don't need to touch it.
Modules: make stuff functional.
- Go to administer > modules and check the boxes for whatever modules you'd like on your site.
- If you want more modules, download Drupal modules you like and drag them into your htdocsdrupalmodules file and they'll show up on your administer > modules page.
Putting the C in CMS: adding content.
On your left navigation bar is a link labeled "add content." Click it and you'll see the available content modules you just enabled. Click the name of the one you'd like to create - the suggested first one to try is a Page - and you'll get a bunch of self-explanatory textboxes to click and go. After you add your first bit of content, look at your Drupal site again, and it should look a heck of a lot like a fully running CMS... because it is.
Themes: make stuff pretty
- Download themes you like (or ones you've made) into your htdocs/drupal/themes folder and they'll show up in your administer > themes section; just pick one and go.
- You can enable more than one theme (so users can choose which one to look at) but can only have one default (the one that first shows up).
- Themes use normal php and css, so if you know either of those, you can easily modify the default themes to use your own logo and such.
And you're done. For more information on Drupal, check out their homepage (I think that's the tenth time I've linked there in this post); there may be a local Drupal group near you that meets up if you're looking for live people to ask questions of. Beyond that, Google is your friend, as people have posted about their favorite modules and such in thousands of places.
I'll be playing more with this in the coming weeks setting up Drupal for a few groups that I'm involved with, so if you have any tricks or shortcuts to share (or want to drag me into your Drupal group - I'm an engineering student in Boston interested in journalism and education) leave a comment with your contact info or email me and I'll write you back. Comments and revisions to this walkthrough are also totally welcome; if someone wants to slap it on a wiki, go ahead, mod it, share it, change it, and otherwise consider it yours.