Subject Line:
Should contain the Course Code (i.e. WEBD2201) the CRN that you are enquiring or communicating about (e.g. 12345) and some indication what the email is about. An acceptable subject line could be (if you were enquiring about your 32345 CRN, note that your CRN will be different):
WEBD2201 - CRN 32345 - Clarification of Lab 5 Requirements
Email Body:
The body of the email should include a greeting (e.g. Hello ❬ PLACE YOUR LAB INSTRUCTOR'S NAME HERE ❭ ), followed by your enquiry or whatever information needs to be communicated to the faculty member(s). You are to consider these exchanges to be formal communication and students are to take the time to create emails that look and sound professional. Therefore, you are discouraged from using abbreviations (e.g. U, R, lol, BTW, IDK, AFAIK, etc.) that you might use while emailing friends and family members or while texting. For a succinct explanation of formal versus informal email communication and when to use each check out Formal Vs. Casual Emails: How To Keep The Professionalism In Your Correspondences. These are good rules to follow when attempting to find and subsequently keep employment. You should consider your lab and lecture faculty as your supervisors in this course.
Signature Block:
Finally, there should be a signature block that, at least, includes your first and last name AND your student number. Example:
For your consideration,
Bill Smith
100123456
Where to send your emails:
- Notices of absense for one class, should be sent to the specific instructor whose lab or lecture is going to be missed.
- Notices of absense for a period that spans multiple labs and/or lectures, can be sent to both instructors by adding both of the email address' in the To: or Cc: field(s).
- Questions or concerns about labs, lab due dates, or lab requirements, should be directed to your lab instructor.
- Questions or concerns about term tests, test dates, clarification of concepts and/or course content, should be directed to your lecture instructor.
Course Server: http:// opentech. durhamcollege. org/pufferd/webd2201
All assignments will be uploaded and viewed or run from Opentech, the course server. This system runs Linux, a free UNIX-like operating system, and the Apache web server. It also runs the other server-side software required for the course: the PHP script interpreter and the PostgreSQL database engine. This server is separate from the main college Information Technology Services such as Campus Pipeline, the Novell servers, the ITIC faculty pages and the main college Web site. The main help desk cannot help you with problems with this server!
W3School
Arguably, one of the best online resources for web development technologies (not just PHP). It will be referenced several times throughout the semester. The instructor recommends bookmarking it in your Favorites and that you take advantage of the tutorials and utilize the "Try It Now" concept demos.
Web pages that suck
Don't repeat other peoples' mistakes. I hope your pages never make it to the "Daily Sucker"
The Web Standards Organisation
Some more arguments about using proper Internet standards.
PHP tutorial on PHP.NET
Tutorial on the main PHP site
Get started with PHP
Another tutorial, this one on the commercial phpbuilder.com site.
This course gives students practical experience with creating a website. Topics to be covered and utilized are:
- HTML/XHTML as the building blocks of the World Wide Web
- Laying out pages and presenting data on webpages using HTML tables
- Laying out and modifying page content using CSS
- Overview of and introduction to basic server-side scripting using PHP
- HTML form design, creation and processing including data validation/persistence using PHP
- Overview of database fundamentals and utilization (including SQL statements) on the web
- Configuring a computer to run as a web-server for website development and testing.
- Basic file I/O processing
When the requirements for ALL the labs state to include HTML comments with your name, the filename, the date the file was created, and a description, the following is AN EXAMPLE of what you should include:
‹!-- Name: Darren Puffer File: index.html Date: May 14, 2019 Description: This file acts as the home page for my WEBD2201 website --› XHTML 1.0 Transitional doctype tag (For use on Labs 1-3)
The XHTML 1.0 Transitional DTD includes everything in the strict DTD plus deprecated elements and attributes (most of which concern visual presentation). For documents that use this DTD, use this document type declaration. Place the following at the top of all your course produce html files: ‹!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"›
XHTML 1.0 Strict doctype tag (For use on labs 4-10)
The XHTML 1.0 Strict DTD excludes all the deprecated HTML 4.01 elements and attributes (most of which concern visual presentation). For documents that use this DTD, use this document type declaration. Place the following at the top of all your course produce html files: ‹!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"›
Don't email your HTML files through DC Connect!
The Campus Pipeline email system will change the content of your HTML files when you email them to yourself. They add a big comment at the start of the file, then add a letter 'x' to the front of HTML tags like meta, script and so on. They do this to prevent malicious Javascript and other nastiness from being sent to your browser. Unfortunately, it also means that your pages will NOT validate any more. To get around this, upload your files to the opentech server directly with WinSCP.
Some extra links
The XHTML 1.0 Strict DTD excludes all the deprecated HTML 4.01 elements and attributes (most of which concern visual presentation). For documents that use this DTD, use this document type declaration. Place the following at the top of all your course produce html files: