Web page standardization is not something anyone can use.

Standard | Web page

"The standardization of Web pages is not for anyone to be able to use" the title is very easy to misunderstand, will think that the author would like to say that the technology is only in the hands of a few people. However, this is not the meaning of this, I hope reader can read the article and then judge.

A recent project customer feedback is: Page page always error, mainly content page error, add some information will be messy, the whole page will be out of chaos. Usually my first reaction is that the code they add is not clean, which means there are a lot of HTML tags in the data, and there are many tags that don't have a number. When this data is added, the site's original code and subsequent code will be between the problem, and in the local code error may produce global layout error. The basic principle is that the unsealed label is understandable and supported by IE in non-standard cases. And when users replicate the content of non-standard web sites, they sometimes take these non-standard unsigned tags, and it is these non-standard tags are added to the standardized web site will be the standardization of the site play a mess.

Web site after the standardization of the website is fragile, is unable to deal with sudden errors. A standardized code is added to a non-standard web site so the code will show no difference at all. But after a non-standard code is added to a standardized web site, it is very easy to make mistakes. No wonder people say the more perfect things are easier to break. Some people will say, why not tell the customer clearly. Let them be aware of the information they are adding. If our customers are able to have a knowledge of web technology is good, we do not need to be so troublesome. But the customer will not listen to this, the client would think I spend money, you want to let me use comfortable. Can't make me so troublesome a job. Also ah people spend money, but also to let people so troublesome operation. Isn't this a game of family?

Does that mean we need to give up Web page standardization? My proposition is: Web page standardization is only suitable for some user groups. This part does not necessarily mean a small portion, but refers to some of the application groups, the specific size of the proportion is not necessarily. Web page standardization for large portals, suitable for professional-level shopping malls or online trading sites, suitable for government sites. Large portals The professional management of all information is published in the most concise manner. can guarantee the correctness of the Web page. The larger the more the more professional website can be used. And government websites, mostly information, and this information is their own information, not from others to crawl, of course, some government agencies will directly copy the Word document directly published, these will not be too big error, because the Word document code, although a bit redundant, but still be complete, not too much bad. And now some editors already have the ability to clean up the junk code in Word. So there's no need to worry about publishing information that could go wrong.

Most of them do not apply to their own independent information sources of the site, these sites to get information on other people's websites as the main content, so their code is not clean is normal. And the error becomes inevitable. So to deal with such customers, need to do before the correlation analysis, this will let us in the later work to reduce trouble!