About the front-end code organization some rude views

For small and medium-sized projects, the lightweight organizational structure is still relatively good;

HTML: Semantic Precedence principle

CSS: Recommended base.css, Common.css, page.css;

Organization style effective management of the entire project CSS, as far as possible to partition the module, there is a certain concept of the namespace, such as:. Timelist-lastitem;

Multi-use combination less inheritance (not even);

Low weight principle (use class as much as possible);

Sprite Technology reduction request;

Commonly used three kinds of hack methods: IE conditional annotation method, selector prefix method, style attribute prefix method;

Trigger Haslayout;

JS: There is a namespace concept that can encapsulate a global object;

The program has a uniform entrance

Layered concept, Base common page

JS Library Selection: JQ basic ability to cope with 98% of development tasks

Some common compatibility issues, focusing on the event node BOM Dom aspect, this, closures and the like ...

Build tools don't use much, try gulp.

　　　　

About the front-end code organization some rude views