Intermediary transaction http://www.aliyun.com/zixun/aggregation/6858.html ">seo diagnose Taobao guest cloud host technology Hall
1. Stick to writing in Notepad
My real contact with Div was only a year, so is also a beginner, the beginning of the same in the DW dragged and dragged drag and drop, do things when all in the Design view never look at and regardless of the page code what kind of, our teacher also teaches, then the concept of the Web page is a picture, animation stack. After graduating to work, I am glad to meet a good supervisor, in the initial learning CSS to give me a lot of help. Asked me to write it entirely in Notepad, so I borrowed a book from the Art next door, the specific name of foreign countries forget, red and white cover, there is a "CSS basic tutorial" feel good. The next Su Ying CSS help manual, write on one side, read books, look up the manual.
Maybe my method is not the best, but it suits me very well. If you start to rely too much on the software, CSS inside a lot of styles will be remembered for a long time, use naturally will not be handy, and so slowly memorize each style in the manual, in order to improve the efficiency of development, and then use (Dreamweaver shorthand, the same below) to write.
2. Develop good writing habits
Remember when a college teacher Delphi said, good programmers write the program like poetry, patchwork, very aesthetic. I want to say that we should be writing HTML and style should also be like this, for example, when writing HTML, my custom is the div tag in pairs, and then fill in the content. Otherwise it is easy to fall off the label, there are errors difficult to troubleshoot, someone will say, write a simple page can, but write a large page, usually dozens of sets together, easy to write a string, this situation will also have, this depends on the appropriate annotation, and shrink in to avoid. When you write CSS, there are a lot of recommended specifications on the web, such as menu menus, copyright with coryright, the bottom with footer and so on, in the writing order is generally: Display Properties-Their properties-text properties. Of course there are no rigid rules, but to follow some unwritten rules is not a bad thing, so that you write the code, easy for others to read.
3. Out of the misunderstanding
Myth One, the Web standard is all using div.
Many people used to use table layout before, after learning Div, you can no longer find table in his code, feeling that using table is a disgraceful thing. This is not the case, and the web2.0 standard does not explicitly refer to table or Div, as the table is also compliant with XML rules. Pages containing a table can still be validated by XHTML1.0. Moreover, Div may be omnipotent, but in some ways it is not the best. For example, we are making a form, table is definitely the best solution, div to achieve absolutely no table to the simplicity.
Misunderstanding two, must pass the verification. The standard just prompts us to update on the gratitude is not a simple code change. Many people use JS to deceive validator, through verification, so there is no pass the verification of the page, but through verification is not our ultimate goal. We want to write a Web page that is accessible on the Internet and easy for users to use.
Myth Three, the more hack use, the more the pattern of their own level higher. When we encounter incompatible problems, usually think of hack, but it is best to try all the other feasible methods, write simple and Standard code, only to use hack. Because Web browser support (forward compatible) should not be limited to the support of the past browsers, but also to the future of the browser support ( Backwards compatible), so we try to be standard, not obsolete.
4. Perseverance
This is not much to say, do everything you need, write style is. The style is the few, the label also that several, toss and turn is not less. The compatibility of the browser requires patience and perseverance.
Above just I in the study some experience, perhaps the master is disdain to see, hope to help beginners.