Let me first say that a newbie shouldn't worry a lot about adding modules and themes at first. Work on the basics of your siteA logically grouped set of content - also web site. first, then worry about add-ons.

Themes are largely a matter of taste. For example, I have no idea why anyone would use a "fixed width" themeFor web sites, this refers to the "look and feel" of the site. It is also used to describe the code to produce that look., but lots of people do. One nice thing about themes are they are pretty much independent of your content (later on you can look at the many submissions that are dependent on content).

Contributed modules are ways to add or extend functionality of your siteA logically grouped set of content - also web site.. The only moduleAn add-on, or extension, to Drupal to provide additional functionality; written in PHP. I, personally, consider necessary is the Nodewords (a.k.a Meta Tags) moduleAn add-on, or extension, to Drupal to provide additional functionality; written in PHP.; in my opinion, it should be promoted to "core" status. This one allows you to add the "content," "keywords," and "robots" meta tags to your pages. This is useful if you're interested in your search engine rankings. You will also find that many contributed modules also require the Views moduleAn add-on, or extension, to Drupal to provide additional functionality; written in PHP.; I go ahead and make that a standard one for my sites.

I am sorry, but when I realized I needed to move my resume here, I had to change the basic Bluemarine themeFor web sites, this refers to the "look and feel" of the site. It is also used to describe the code to produce that look. a little. What you see here (other than the logo picture) are very small changes to the style sheet.

Remember the KISS Principle

Resist the temptation to add every moduleAn add-on, or extension, to Drupal to provide additional functionality; written in PHP. that looks like it might be useful someday! If you don't NEED it today, don't install it. Why? There are several reasons for my suggestion: 1) Not all modules play well with others - most do - research the forums and support requests. 2) I'd be willing to bet that you won't need all of them, and removing them can be problematic, especially the access control modules (worry about security later in your project). 3) Not all modules will make it into the next release of Drupal

Drupal

An open-source content management system that is used on this site and is taking over the world., and some will be delayed after the release - research their history, research their bug reports - be sure you want to invest in that moduleAn add-on, or extension, to Drupal to provide additional functionality; written in PHP.. 4) After your understand Drupal

Drupal

An open-source content management system that is used on this site and is taking over the world. a little better, you may realize you don't really need that moduleAn add-on, or extension, to Drupal to provide additional functionality; written in PHP..

Do keep a list of things that you might want or that your current siteA logically grouped set of content - also web site. is not doing yet. Prioritize it. But don't be completely hung up on following the priority list strictly. Some times item #2 will be much easier to do after you've done item #7. (Okay, technically that means you mis-prioritized item #7, but who's counting?)

Installation

Installing a moduleAn add-on, or extension, to Drupal to provide additional functionality; written in PHP. or themeFor web sites, this refers to the "look and feel" of the site. It is also used to describe the code to produce that look. is pretty much the same until you get to enabling them. Now keep in mind that I use a Windows based PC (development) and LinuxA Unix variant that has become very popular. It has itself spawned numerous variants, although not all of those enjoy open-source status. servers (on my live sites).

1. Go to the Drupal

   Drupal

   An open-source content management system that is used on this site and is taking over the world. siteA logically grouped set of content - also web site. and click on the "Downloads" tab. Then select either "Modules" or "Themes" depending on what you're after.
2. Locate the moduleAn add-on, or extension, to Drupal to provide additional functionality; written in PHP. or themeFor web sites, this refers to the "look and feel" of the site. It is also used to describe the code to produce that look. you want.
3. I always click on "Find out more" and read the stuff again. This gives you the chance to see if there is support for your release of Drupal

   Drupal

   An open-source content management system that is used on this site and is taking over the world.. You can also look at pending bugs and feature requests - it might change your mind.
4. Download the proper release. (I put them in a Drupal

   Drupal

   An open-source content management system that is used on this site and is taking over the world. folder in "My Downloads.")
5. Unzip the downloaded file (I use WinZip). It may tell you that there is only one file in the zipped file; click "yes" or "OK."
6. Extract the code to to your Drupal/sites/sitename/modules or themes folder. If you are not running multiple sites, this would be Drupal/sites/all.
7. That's it! Now you need to enable it.