Validation

While trying to solve a validation issue in one of my web sites I came across the following forum posting. It was stated so well that I decided to re-post it here. I want to encourage my readers to understand that when a page doesn’t pass validation, it doesn’t mean that the page is “broken”. Please read on…

Validation is a tool. It is not a goal. It is for catching syntax errors. It is for you to determine whether to worry about the error or not.

The animations module is in working draft status.

Quote:

Status of this document

This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.

Publication as a Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.

Emphasis added.

It would be foolish for vendors to implement a module that is likely incomplete and certain to be modified in ways that would affect that implementation. That is why we have the -[vendor]- prefix. It’s a temporary implementation until the dust settles.

If your client is insisting on a validation button, you’ll have to explain why that’s not possible. Using css3 is a progressive enhancement; in this case from both sides. Older browsers won’t support css3 animations, and css3 won’t validate the proprietary prefix that allows for working draft properties that are not a part of the specification yet.

Gary Tuner, (Moderator on http://csscreator.com)
Source: http://csscreator.com/topic/w3c-validator-and-css3

COM1000 Beginning HTML Overview

HTML (Hypertext Markup Language, CSS (Cascading Style Sheets), and JS (Javascript) are the three primary languages that are used to create web pages. Every time you consume content on the web, those languages were used to create what you are seeing, hearing, reading, or watching.  If you’ve wanted to learn about basic web coding, now’s your chance.

Nashville State Community College has a a 13 week course on basic web coding this semester. It is being offered through the Visual Communications department. No coding experience is required. Classes begin on January 19, 2016,  so if you’re not a current student of NSCC you need to apply to the school and be admitted before you can enroll in the class.

Details:

Course Name: COM1000 Beginning HTML
Day/time: Thursday 6-9 PM
Location: Nashville State Community College, Main Campus (White Bridge Rd), Clement Building (C-108)

For more information contact:

Dale Rogers, M.Ed.
Assistant Professor, Web & Multimedia Design
Nashville State Community College
dale.rogers@nscc.edu
ofc: 615-353-3504

Overview

Anyone who creates content to be consumed on the World-Wide Web will at some point be face to face with the technologies that govern how that content is presented. Nashville State’s COM1000 Beginning HTML course covers that process.

We consume web content through an application called a “user-agent”. A user agent is some tool (an agent) that allows you (the user) to see, hear, read, watch, listen, or somehow consume content. Most typically, the user-agent is a web browser. The Web browser is the key to everything. As designers, podcasters, bloggers, marketers, trainers, salespeople, writers, illustrator, videographers, filmmakers, etc, we want to engage with our audience through the web browser. Therefore, we need to know a little something about how to get the browser to display our content as we intended it.

The three main languages that the browser uses to accomplish that are:

  1. HTML (Hypertext Markup Language)
  2. CSS (Cascading Style Sheets)
  3. JS (Javascript)

HTML allows us to put a structured object (an element), say a heading, paragraph, video, or an image, on a page. HTML contains tags that tell the browser what it can do with that element.

Every element has properties. When we want to determine the type of font, size, color, or location of a heading… when we want to determine the dimensions of a video, how it will be placed on the page, we use CSS to control an elements properties.

If we want to control an element’s properties based on some criteria, for example, when a button or link gets clicked, or a link is hovered, then we need to use scripting. That’s where Javascript comes in. It allows us to manipulate an object’s properties dynamically.

In COM1000 you will be introduced to the underlying languages that affect how content is displayed on a web page according to current best practices. It will give you the solid foundations for further exploration.

The course is part of Nashville State Community College’s Web Design concentration in the Visual Communications Associate in Applied Science degree. While the course is part of a degree, anyone from the community can enroll as a non-degree seeking student.

wwwroot

In the unit A project the author has you create a folder named wwwroot. Why?

When you get a web host account, you’ll find that there a number of folders that you have to work with. One folder will be the designated folder where all of your publicly accessible web files will be located. Different hosts call that folder different things. I’ve seen:

  1. public_html
  2. public
  3. wwwroot

I’m sure there are other folder names in use by other web hosts.

Vodnik asks you to create a folder called wwwroot to put your web files into. So does that mean that ALL your files go there. Not necessarily. You will find that a lot of files go into creating a project. The wwwroot folder in this case will be the upper-most folder for web files for this project. Unless the project plan, wireframes, and storyboard(s) are documents that you want the public to see, you keep them out of the web site folder. This is mostly a good file management practice. If the file is not needed for the web site, then it really doesn’t need to be under the web site’s root folder.

Will having a non web site file under the root folder break the site? No.