User:Vtaylor/CIS89A Learning Web Design/3. summary

From WikiEducator
Jump to: navigation, search

2019.10 based on 19m


3. Summary - Links


Links are an essential feature of the web. Learn to use all the formats they can take and all the places they can take your visitors.

More great coding project submissions and thoughtful feedback. More good discussions with many new resources provided. These contribute to making this course so interesting and useful.

  • What to do - Module activity descriptions are provided on a separate web page. Some students are just posting to the discussions without reference to the discussion description. There are specific learning objectives associated with each of the activities.
  • Discussions and question assignments - Remember. This is a transferable credit course. College level writing is required. If your response lacks specifics or adequate explanation, points may be deducted.
  • Late work - By now, everyone has had an opportunity to become familiar with the course structure and has established a routine for completing the coursework. Reminder: All module Assignment activities are due on the module due date. Late work submission deductions may apply. If you know you can't make the deadline ahead of time and you have a good explanation, we can talk about a plan and an extension.


Voyager, file transfer

  • http://voyager.deanza.edu/~vtaylor/m18index.html - Within the Glitch index.html file the link to the css file is rel="Stylesheet" href="/style.css" type="text/css". If you did not modify the link or naming in Glitch and copied the source from Glitch, this may not work in Voyager. You may have to remove the "/" so you would have href="style.css". Or, as some students suggest, use the Unix filepath naming "./" to explicitly say that the .css file is in the same directory as the .html file. If you have a problem try href="./style.css". Either of these will work. See LWD p.27 and Chapter 6. Adding Links.


Coding projects

  • New module, new project - Keep it simple. Create a new project for each coding assignment. Glitch provides you will all the basic elements and tags - html, head, title, meta, body. It shows you how comments are formatted. You need all these. Do not delete them! You may need to modify them for your own work. Points will be deducted if they are not in your code correctly.
  • Requirements - Reminder these are coding assignments! You can use any content you like. Be sure to include all the required tags and features. There are some really good looking projects being submitted. Some are missing most of the requirements. You are taking this course to learn web development. That means practicing using a broad range of functions. If you don't include these in your project, you probably won't have learned some important features of web development.
  • Grading - Keep your projects simple. Confine your work to be graded to the html file you submit and one linked style sheet. That's all that will be reviewed and considered for grading.
  • Look it up - You don't have to remember all of this! You should be learning where to look up the current version of this information (and how to use it, if you need that too).
  • Discussion AND assignment - Yes, you "submit" the link to your coding project twice. 1. as a post in the discussion for sharing with the class AND 2. as the assignment for grading and feedback. Spend time looking through the work submitted by other students. You will learn a lot!
  • Basics - All projects must use css for styling. Include comments in all your css and html and html code. Replace the default Glitch title with your own. Watch the structure of your html page elements - all code including comments must be with either the head or body elements and only one of each of these are in the html element. Make sure tags that require a close have one. Yes, there will be points deducted for missing these.
  • html code formatting - Nothing says rookie coder more than basic code formatting mistakes. Spaces in your html code may be incorrect. Some places spaces don't matter. If an attribute or property value has an equal sign (=) then there should not be any spaces either side of the "=". See LWD p.63 for details.
    I use Firefox as my browser. When I look at your source code, Firefox automatically highlights these errors (along with others). This is just one example of basic code formatting that you need to know.


Coming up...

Module 4. Images & Media

A picture is worth a thousand words - It is easy and inexpensive to add pictures to web pages. One of the great benefits of the web and the internet has been the virtually unlimited availability of content, specifically images, audio and video.