Quick Note: I don't know when, the logo (tags) becomes an element (Elements), which are the same meaning, different statements. No matter what you call them, the right name is now "element", maybe this is like this, I don't know if I have told me.

In any case, each element must be closed correctly. If you use HTML4.01, you can do not consider the individual element icons
,

Finally, XHTML needs you to write all the code with your lowercase, HTML is not case sensitive, but XHTML distinguishes, it follows the XML syntax rules.

The above is all changes in the identification! You already know! Check deep breath, drink beer, relax. Because it is just the first step.

Second section

Now, we start learning the correct HTML / XHTMLL and verify them in the Validator's Validator. If you write correct, you will see a successful information of a blue bottom yellow word. Try like this color / font combination, it will be your best friend.

Why is the verification? What is the relationship? Because Poorly-Written (casual, unscrupulous) identity will bring complete unpredictability. The page "Life and Death" is completely dependent on the browser's error handling method, although most browsers can support the poorly-write identity, but this is incorrect habit. Hi, what is the non-standard? The primary reasons are browser wars. In 1995, Microsoft can compete from Netscape to obtain a market because IE is the same as Netscape's processing.

Another point is: Verify the code to help you find the wrong code, make sure your page has a more consistent manifestation. The calibration code is the first thing I debug layout, I believe you too.

OK, when you first check your first site, you are likely to endure the 150th incredible error message that feedback back. Unfortunately, although the verification helps information, it is not perfect, it is only maintained by some volunteers. Good news is that the error is associated, if you find less a tab and fix it, it is likely that the next 24 errors are not. In short, it seems that the verification results are very bad, but it is often not.

Now, you have passed the check, your code is also in line with the norm. At this point, you insist on a strict guideline, but why should you first do this still understand a comprehensive understanding.

Third quarter

The next step is to use a good format (Well-Formed) to refactor the document you have established, stripped those with more and more new DOCTYPEs as "disapproval", using the properties of the performance layer used, put them in a separate In the file. This is the controversial "performance and structural phase separation", which is why CSS is attached to people.

This way, your text is content. The content is complete, but there is no tips for any content structure (such as space, section, title, list, etc.), you get just a messy text, it is not easy to use. The structural layer is additional, plus individual elements in the document to convey additional structural information, to break the messy text, make it more logical, organized. However, those elements do not control the default appearance of the text. For example, you often find that the title of the first page is larger than the original font, which is not a structure.

It was the "performance layer". The performance is a formatted tip, which tells the first page of the title is red, the slope, the font size is 150% of the original font. The performance layer is an additional layer of the document structure layer. CSS belongs to the performance layer, which can convert documents into amazing forms through a simple mark on documentation - can access CSS Zen Garden to see instances. So, what is the best way to separate the performance from the structure? We will explain the traditional code that includes HTML elements or properties for providing performance. It is when it is cut off those BGCOLORS and