I need to take a quick step back in my process and make a brief note about Drupal Terminology. Almost every other Drupal instruction set I have read include a significant amount of time devoted to terminology. From a general perspective I don't like doing this because I would rather use terms people understand. But, the world of Drupal has it own language regardless of what would be easy for beginners. In the grand scheme I think it is good. The language and terms used by Drupal are very exact and as a result, once understood, it is very helpful.
Here goes. I may add to this as I run into terms that are critical to a new section of lessons. All descriptions are given as they apply to Drupal. I have tried to organize them as they need to be understood from most basic general to more in depth and Drupal specific.
Drupal: A web based Content Management System. Translitteration of the word Drop in Dutch (Druppel). Originally a misspelling of the Dutch word Dorp, which means community.
Content Management System (CMS): A system where data can be stored in a standardize format on a server. The data can be viewed, created or edited through a styled or themed user interface. In the case of Drupal it is also expandable to allow for numerous types of data or methods of alteration.
Core: Refers to the basic Drupal package downloaded from drupal.org. Core includes the basic application code as well as included expansion modules and themes. Everything included in core is highly tested and tends to be very stable.
Module: An extension to Drupal used to add functionality not included in the basic CMS. Examples of core modules include blogs, forums, polls. Users can add functionality to Drupal by creating new modules. The number of user contributed modules is enormous. I will discuss individual modules later in the book.
Theme: The appearance that the user of Drupal sees when accessing or editing content. Several basic themes are included in Drupal core. However, to give a website a unique look a feel a new theme (or sub-theme) will be required. The Zen Theme is designed to be easily changeable and upgradeable.
Node: The broad Drupal term to describe a piece of content. This content could be text, images, audio files or even a page of other nodes. Nodes can be created, edited and reorganized and manipulated by users or modules. Comments are an exception to this rule, they are not nodes.
Taxonomy: Drupal organization. Taxonomy allows tagging and structure to be added to Nodes so they can be easily sorted and organized. Taxonomy is broken into two parts or levels first vocabulary then terms. For a simple example, on my site I have a vocabulary "post_type" and terms like "Woodworking", "Cooking", "Family" and "Drupal". I can then organize my content using these terms so when you click on the woodworking page you only get woodworking.
Path: what appears in the URL location when you are looking at content. Using the Clean URL features changes these from something rather convoluted like "www.yourdomain.com/?q=node/4105" to something pretty like "www.yourdomain.com/how_to_do_this".
For now I think this will do. It is not comprehesive I just want to make sure I don't use a term that is completely foreign.