Write 'friendly' 'Javascript' code as much as possible_Basic knowledge

When the robot of Search Engine searches, for the type, the friendliness of "text" such as text/html is the highest (except text/xml at this stage), while the friendliness of text/javascript is not ideal. If the robot still If you want to judge DHTML code, the complexity is also high, and it is not worth it

Therefore, when programming DHTML, if you want to improve the friendliness of the code. The better method is to "simplify the DHTML code into code without HTML as much as possible". How to understand this sentence?

e.g: A javascript menu. Method 1. Use conventional programming methods: var navi_menu = neverDHTMLmenu(); /* addItem method * @ pid * @ id * @ text * @ href */ navi_menu.addItem("0","1","home","http ://www.never-online.net"); navi_menu.addItem("0","2","blog","http://blog.never-online.net"); navi_menu.addItem("0","3","music","http://www.never-online.net/music"); navi_menu.init("navigator_Container");

2. Use a programming method that is more friendly to Search Engine

Copy code The code is as follows: onload = function() { var config = { container: document.getElementById("navigator_Container "); // and more configuration code } var navi_menu = new neverCssDHTMLMenu(config); navi_menu.init();

home blog music

Comparing method one and method two, the method encapsulates some HTML into neverDHTMLmenu(), but in this way There is no real benefit, although we can still put CSS into this class. Method 2 can be seen to have many benefits. For example, the view can be separated from the program, and client-side MVC can be implemented. Put another way, it can improve development efficiency.

Some friends may ask, besides menu, what other programs can be separated according to the above method? As mentioned above, this method can be used for those that generally interact with the page more, will generate a lot of HTML, and will affect the Search Engine's robot. Of course, these are just discussions about the friendliness of the Search Engine. , so any code must be determined by the actual situation.

Some friends may also ask, why does this improve development efficiency? For example, after the artist makes the template, (assuming that the artist knows how to write some relevant HTML), then according to the xhtml standard, (as shown in the example above) Suppose I want to change the original home to Default page, then the artist has to Communicate with the programmer and say that the wording of this menu needs to be changed, which will take more communication time during development. Therefore, this time must be included in the development progress. If you want to change the template, you still need to communicate. Or if the original HTML generated using js is a menu made from a table, and it needs to be revised, then the program will have to be rewritten. Not conducive to maintenance...

It is recommended that you try this method. The main meaning is that JS is responsible for business implementation, while the view is still handled by HTML.