It's been almost two years since we started contacting the so-called web standardization. From the initial doubts and hesitation until now, went through every stage. This process is painful and happy, the pain is that no one in the process can help you answer questions, all the problems you have to solve (this is painful at the beginning), happy is when you successfully out of the wandering after the harvest of joy ... Web standardization for Web pages My understanding of this is that it should not be a trade-off between table and Div, nor should it be a div layout that conforms to standardization. The most critical is the degree to which this understanding is to be understood. If you still want to write div in the way of table, it is better to use table to layout, because the table layout visualization is very mature, will greatly save your development time. Using a div (which should be xhtml+css) to lay out, it's almost certain that you're going to have to write the code like a programmer (it's a must-have skill). Web standardization has a special validation tool on the Internet to verify that your Web page meets the standards. Personal opinion can only be used as a reference, not absolute. This reminds me of a sentence, "You do the site is for the user to see, or to the search engine to see", in this issue is also the same. Do not be overly advocating the so-called web standards, as long as you really understand the meaning of web standards and bring benefits I think enough. Say a few words I understand the Web Standard bar (if there is a similar, very honored) 1. What is the use of what this is mainly refers to the HTML tag, I have to re-learn the HTML for this once again, re-view the HTML of each tag function and meaning. This is very important, so to speak if you do not understand the meaning of each HTML tag, you write out the front-end code must be problematic. This is related to the previous mode of work, because you don't need to know the look and meaning of every HTML tag in the time table layout, you just need to click on the Set button in the visual mode. But now the problem is that visualizations that support web standardization have not yet been created. 2. To have their own ideas and style "thinking determines the fate" This is also true here, no matter what code you write, as long as the handwriting code of each person's writing will be different, this should be the style bar. Clear thinking, unique style. This should be what we are constantly pursuing. Now it's the problem, the ideas and styles that everyone has, and it's impossible to distinguish between those that are right and those that are not. I have seen some colleagues or peer-written div page, some feel very strange, it seems that this is the way table, but it is to change table to Div, of course, it is not so simple, but the idea is the same as the traditional, this phenomenon is more deadly, and only trouble will not be beneficial. Or the two words "understanding" mentioned above 3. Easy to extend this is the definition of the module mentioned in the program should be one to the moduleCSS is also the goal of the pursuit. It's actually just a shift in thinking, and it's very effective and easy to extend. To give a very simple example, to get a block B to ensure that the basic style is not changed or complete one, but now a lot of cases, as long as the moving position will be confused or all the confusion. My opinion is first to clarify that those are shared and that are private, and then consider the problem of easy expansion. 4. Commenting and naming these two points is very important and is also a very important criterion for distinguishing the quality of code. First of all, the code is written for the user to see, but also for themselves and other colleagues to see. The meaning of the note is not to say a word about naming it. Naming should be very important, first of all, from class name you can quickly know what the class is for, and not only you can read it, others will soon understand if they take over your project. Box_a,box_b,box_c Wait, if you simply look at such a name will you know what it is? The answer must not be known. This kind of naming is very common, first of all, let's talk about the drawbacks. First of all, you will be confused; second, if there is a change you will be very troublesome (cannot be changed); Third, it is not conducive to maintenance and management; This similar naming approach shows that you do not fully understand web standardization, which is still using traditional ideas to understand the standard ... In this own understanding and the need to strengthen the place 1. Understanding the meaning of HTML tags and making it easier to understand the document structure easily HTML5 in this respect (HTML) 2. reasonable annotation and naming (JS) 3. The layout of the standard DIV+CSS replaces the table layout, and cannot ignore the code structure (CSS) because of the implementation functionality
