Establish your own operating standards

Standard

When we are all in the web standards, we often hear the voice: "Too slow to make such a page I need to spend several times more than before." "Does the adoption of the standard really make your production slow?" My answer is "not necessarily, it all depends on what kind of perspective you look at, and there is no way to find a quick action." "The first thing we want to make sure is that the new way of doing this is to pull us from the" WYSIWYG "software into the" Code editor. " We now need to have an understanding of each XHTML tag, and have a sense of their characteristics! And we just had to hide behind the software.

We are now standing at the intersection, is the time we choose! To the standard? Or to tradition? The choice of things needs to analyze the development of things, and advanced. Standard is to advocate code standards and clear, advocating style of separation of data. From this point of analysis: The code is clear and standardized, is to facilitate the sharing of information within the site, that is, the code clear and standard Web site more easily by the collection engine search, and can be ported to other display devices. The separation of data and style shows that the Division of Web page production becomes more and more clear. Art as long as the focus and aesthetic aspects can be! The producer only needs to know how to implement the artwork, and the programmer simply outputs the code with the data. We can give up the traditional mode in light of these two points! What's more, we can save money to buy Dreamweaver! But we always encounter difficulties--development speed!

To be aware, our previous development rates benefited from our familiarity with Dreamweaver, our understanding of table layouts, and our disregard for details. We can take out the previous works and the design diagram comparison is not a lot of places "size and length" is not the same as the first design? Of course, cracking down on traditional weaknesses doesn't make me abandon tradition, and we need to come up with ways that can be faster, more accurate, and easier to manage than traditional methods. And today I'm here to express my point of view!

When I began to learn the standards of the beginning I was thinking about how to make my workload less! It is a virtue to reduce unnecessary duplication of labor. I found that we make Web pages in the Web code we have a lot of the same! For example, the header file, sometimes our layout seems to look at only the more than 10 layout, and we used the label is only more than 10 commonly used, when we understand the layout of the XHTML we have a clearer understanding of the choreography. Well, look how I did it: (Reminder: Even if we are code editors, we need a good code editing tool.) I'm using a editplus.

1, the collation of a standard XHTML file. This file has dtd,head,body and so on, in the head we have to fill in each of the information are included in it, this is my every survival page template!

2, in the editplus of some commonly used labels are made in advance in the editplus of the Clip Gallery!

3, in the EditPlus some commonly used CSS also in advance to put in the Clip Gallery.

4, the analysis of several commonly used Web page layout, and then made into XHTML code, stored in the Clip Gallery.

5, the production of their own CSS common ID and class name set, preferably a comprehensive point.

6, in the CSS needs to be commonly used in a number of CSS commands to make a collection, such as: "Page Center", "horizontal navigation", "form style" and so on, in the CSS in the body and the div ID or class CSS command to put in a clip in the library.

There will be more work to be done to reduce duplication in practice, which requires us to think about how to solve the problem. At the same time we can write the code as much as possible, so that the code can still be used without modification when we migrate to another place!