course-outline


 * Instructor – Greg J. Smith** greg.smith1@sheridanc.on.ca
 * Technologist – Dafydd Hughes** dafydd.hughes@sheridanc.on.ca
 * IT Support –** **Mark Galaszkeiwicz ** mark.galaszkiewicz@sheridanc.on.ca

Students will draw on their CSS and information architecture skills to create basic and medium complexity websites with Drupal. A series of seminar presentations will run throughout the semester and will provide the group with the opportunity to research and learn about many of the key modules used widely across the Drupal community. Students engaging the labs, major assignments, selected readings and participating in class discussions will develop:
 * Goals and Learning Objectives**


 * Familiarity with managing and administrating a Drupal site
 * An understanding of how to 'theme' a site
 * Skills in applying information architecture fundamentals to construct sophisticated publishing workflows
 * The skills to asses, organize and initiate a 'real world' web project

//Students who apply themselves in this course can expect to have entry-level content manager and/or junior drupal developer// //skills by the end of the semester.//

Each week will feature a lecture on design principles and present various case study sites related to Drupal development. There will be a small selection of assigned readings that serve as the basis for conversations about web publishing and the course will also feature guest speakers from within the Drupal or broader design community. At least one hour of every class will be dedicated to lab exercises and as the semester progresses 'free work' time will be devoted towards working on the major assignment.
 * Required Materials**

Although there is no required text for the course, [|Information Architecture: Blueprints for the Web// (2nd Edition)] and //The// //[|CSS PocketGuide]// are highly recommended.

Students will work in pairs and select one of a range of prominent/sophisticated Drupal sites and assess the functionality of these precedents. This will be delivered as a simple three page report that requires each group to critically engage existing web content.
 * Assessment and Grading Policies**
 * Type || Description || Format || Due || Weight ||
 * Assignment || Case Study || Group (pairs) || Feb 2 || 10% ||
 * Assignment || CV Assignment || Individual || Feb 16 || 20% ||
 * Presentation || Seminar Presentation || Groups (4-5 members) || Mar 1-22 || 15% ||
 * Class Participation || Class & Wiki Participation || - || Ongoing || 15% ||
 * Assignment || Website || Individual || Mar 29 || 40% ||
 * Requirements and Criteria**
 * Case Study - group assignment**

Given one of the primary innovations of Drupal is its modular expandability this assignment will charge groups (of 3-4 students) to select a given module, research its functionality and write up a wiki reference page for the class. This research will be demonstrated to the group via a 15 minute presentation to the class (demonstrating the module where possible). This assignment will put students in charge of part of the course programming and promote the vital 'information gathering' associated with engaging open source platforms. Groups will be evaluated on the effectiveness of their presentation and the quality of their research.
 * Seminar Presentation - group assignment**

The first major Drupal assignment will have each student employ a step-by-step walkthrough to use Drupal's content type construction methedology to build an input system for their own CV. Students will then be required to style and organize the resulting page using CSS. While this assignment will be evaluated in terms of CSS and web typography, students will pick up fundamental content creation skills that will be invaluable as the semester progreses.
 * CV Design Exercise - individual assignment**

The major assignment will have students develop a fully functional, medium-complexity Drupal website from the ground up. This will be worked on in the lab sessions from reading week through the end of the semester and culminate in a review of the work produced on the final day of class. The site will be evaluated based off the quality of information architecture, design and usability.
 * Website - individual assignment**

Communication and collaboration are essential skills when working with open source software. Participation marks will be awarded to students who are active on the wiki, ask questions and contribute to the class discussion, and offer assistance and support to their peers during the lab sessions and during the build up to the two major assignments. Persistent absence will result in a poor participation mark. A 'participation rubric' will be provided within the first few weeks of class.
 * Class & Wiki Participation**

Each week will feature a lecture on design principles and present various case study sites related to Drupal development. There will be a small selection of assigned readings that serve as the basis for conversations about web publishing and the course will also feature guest speakers from within the Drupal or broader design community. At least one hour of every class will be dedicated to lab exercises and as the semester progresses this time will be devoted towards working on the major design assignments.
 * Teaching Methods**

Only student Utormail accounts should be used for course communication and all emails from students must include the course code in the subject line and should be signed with the full student name and student number. The course wiki resides at http://cct460-w12.wikispaces.com students are expected to refer to it regularly for reference material, related links and tutorial information.
 * Procedures and Rules**
 * E-Culture Policy**

**Any technical questions should be asked in the discussion section of the course wiki rather then via private email sent** ** to the instructor –** that way the answer is available for the entire group.

For the case study assignment, e-submissions will not be accepted under any circumstances. Material is to be handed in class. All web work will be 'handed in' via email notification.
 * Learning Technology**

You are expected to complete assignments on time. There will be a penalty for lateness of 10% deducted per day and work that is not handed in one week after the due date will not be accepted. **Extensions will not be granted unless there are (documented) extenuating personal or medical circumstances (see the below terms – if you are not familiar with them that does not excuse you from these protocols).**
 * Late Assignments, Extensions**

//If you require more time to complete term work you should contact your instructor immediately, and no later than the due date. Original supporting documentation (e.g. U of T medical certificate, accident report) and a request for Special Consideration Form are to be brought to Rose Antonio, Academic Advisor in CC3018 no later than one week after the due date. Your documentation must specify exactly the length of the period during which you were unable to carry out your academic work. Students must adhere to UTM policy and declare their absence on ROSI, in order to receive academic accommodation for any course work.//