[Reading notes] The way of the Web front-end development cultivation

Original address: http://www.cnblogs.com/bnbqian/p/3735565.html reprint please indicate the source

The book that we are going to read today is the way of Web front-end development

The 1th chapter starts from the reconstruction of the website 1.1 bad realization, headache maintenance

Once, the page code is very messy.

1.2 WEB standards, structure, style and behavior separation

Separated.

1.3 Front-end status

People are uneven.

Summary:

This chapter is equivalent to an introduction.

The 2nd chapter of the Team cooperation summary:

Teamwork and communication This is always a good topic to count words.

3rd. The semantics of high-quality HTML3.1 tags

Tags are semantically, except for div and span.

3.2 Why should I make a semantic label

Make the HTML structure more clear.

3.3 Semantic good criteria for judging

Take off the CSS and look behind your coat.

3.4 Example

• Use less div and span
• P and Div Precedence selection P
• No plain style labels

Summary

The important method of high-quality HTML is to use semantic tags appropriately.

4th. High-quality CSS4.1 weird patterns and DTDs

DTD (Data Type Definition), IE will parse in weird mode if the DTD type is not declared.

4.2 How to organize CSS

• Base.css + common.css + page.css
• Universal + Project + Flexible

4.3 Recommended base.css

This is good, it is recommended

4.4 Modular CSS4.4.1 How to divide modules

This chapter is about

4.4.2 Namespace for CSS

Name class in the same way that classes and attributes are referenced.

4.4.3 Multi-use combination, less inheritance

To put it bluntly is to hang multiple class

4.4.4 Margin Issue

Do not mix with MT MB

4.5 Low weight principle

Do not abuse child selectors

4.6 CSS Sprite

No, it's not a problem.

FAQ for 4.7 CSS 4.7.1 Multi-line and one-line

Single

4.7.2 ID or class

From a CSS point of view, it is recommended to use a multi-class