What are the precautions for web pages made with div css I studied asp

Compatibility is the biggest problem.

It is rare to encounter such a problem with Table, but div+css will have a lot of style inconsistencies such as IE6, IE7, IE8, Firefox, etc.

Using a table is not very demanding for CSS, but if you use a div, the requirements for CSS are very high.

Made with div+css**, compatibility with most browsers is a basic requirement, if your web page is serialized on more mainstream browsers, overlapping, etc., it will definitely affect your popularity.

Dynamic web pages created by ASP are no different from other server languages and do not affect the style of the foreground. Don't worry.

This doesn't have much to do with asp. div+css is just the layout of the page, look at other people's **css and then modify, just practice more.

The main thing is:

1. Standardize the scientific naming, so that it is convenient to maintain in the future and convenient for others to read;

2. Compatible processing, so that different versions of mainstream browsers can be browsed normally;

CSS is the front-end page effect display, independent of the program!

I have a detailed DIV+CSS e-book, as well as HTML summary PPT, a lot of practice materials, if needed, send a letter, I will send you.

@提高效减小**@提高访问速度@让布局整洁漂亮@扩展更改时简单@对一些不同版本浏览器带来强兼容.

Benefits of using div+css for web page bai design:

Jiangxi Xinhua.

Fly Ori gives.

Test the oranges.

DIV (Identification) + CSS (Cascading Style Sheet) is one of the common terms in the standard (or "web standard"), usually to illustrate the difference from the HTML web design language (Table) positioning, because in the XHTML design standard, the positioning technology is no longer used, but the way of div + CSS is used to achieve various positioning. The SEO impact of using DIV + CSS Design** is obvious, due to the simplicity of the structure and compliance with standards.

Maybe the width is not enough? You copy and paste the source ** and see.

This is obviously a problem with the layout, see if the height is collapsing.

First of all, the great advantage of CSS is that it is concise, for a large website, it can save a lot of bandwidth, and as we all know, search engines like to clean (the real meaning is that it increases the proportion of effective keywords in the total number of web pages), so the use of CSS div web standards to make ** has a certain advantage of search engine friendliness. Secondly, the ** made by CSS+div makes the ** revision relatively simple, and many problems only need to change the CSS without changing the program, thus reducing the cost of the ** revision. Problems with CSS DIV** design Although CSS+DIV has certain advantages, the problems existing in the construction of CSS+DIV** at this stage are also relatively obvious, mainly in the following aspects:

First, the high reliance on CSS makes web design more complex. Relative to the ** layout (table), although CSS+div is not unattainable, but at least it is much more complex than **positioning, even for ** design masters are easy to have problems, let alone beginners, which to a certain extent affects the popularization of the XHTML design language. Second, the CSS file exception will affect the normal browsing of the entire **.

The design elements of CSS are usually placed in several external files, and this one or several files may be quite complex, or even relatively large, if the CSS file call is abnormal, then the whole ** will become miserable. Third, browser compatibility issues with CSS** design are more prominent. The web design based on the web design has almost no browser compatibility issues in later versions, but the CSS+div design of the ** page that displays normally in Internet Explorer may not be recognizable in Firefox (which is why it is recommended for online marketers to use Firefox).

CSS+div needs to be further supported by various browser vendors. Fourth, CSS+DIV is SEO based on the level of expertise in web design rather than CSS+DIV itself. CSS+div web design does not guarantee the optimization of the web page to the search engine, and even does not guarantee that it must have a more concise design than HTML, not to mention that the search engine's inclusion and sorting of the web page is obviously not measured by whether it adopts ** and CSS positioning, which is why many traditional **layout production** are ranked high in the search results, and many web pages made using CSS and Web standards are still ranked low.

Recommending div+css is not in conflict with abusing divs.

You first have to understand what it means to abuse div:

Abuse is due to the fact that many people do not learn well or do not use their brains.

After reading the tutorial and the book, I can't turn my head when I move things from the book.

The quality of the current books and tutorials is also poor, and they are also cobbled together, which misleads many people.

Examples of abuse:

Make a search form or navigation bar, according to the design effect, you can directly use CSS on the form of this form or the ul of navigation to achieve it, and the abuser wants to go to the outside of the form and add a div to cover the form.

The content area of the web page should be represented by various tags such as H and P according to the semantics and paragraphs as much as possible, and CSS should be used on these tags, while the abusers use div to contain these contents throughout the text.

In fact, abuse is nothing more than two main points:

Random nested divs or other markup, redundant tags written due to poor grasp of CSS and HTML.

There is no need for semantic tags, everything is included with div and span.

It is not wrong to use the recommendation, to avoid the above points, you must first be proficient in HTML and CSS;

Text paragraph 1 in the content area of the web page

Text paragraph 2 in the content area of the web page

And then I was in. user-zone, to write styles to control the indentation, width, font size, color and other things of p, h, a and other things under this div.

According to what I said above without abuse, it seems that CSS should be written directly on top of p to control its own style, and div is redundant and should be del away.

Text paragraph 1 in the content area of the web page

Text paragraph 2 in the content area of the web page

When you write a style directly on P, the customer doesn't type P into it, and it controls the fart.

At this time, add a div outside, although P's css is invalid, but at least you can control the text line height, links, font size, etc., so that the whole page is not too ugly.

Whether this seemingly redundant div is abused depends on how you understand it, the ghost knows what the customer will copy from word without clearing the word format tag, at least you still have half of the control over multiple divs.

In the past, it was all layouts, and although such layouts were easy to implement, they would also make the layout and style tightly combined, making it more difficult to maintain. Because, if you want to change the style of the page, you have to modify the structure of the HTML, which is a lot of work and prone to errors. Nowadays, the structure is complex, and many layers need to be nested when using tables, which will make people confused.

However, with div+css, the layout styles are completely separated. Using CSS is like manipulating a puppet with a thin wire. As long as your div layout is properly designed, most styling changes don't need to change the structure of the HTML.

You can easily swap the positions of two divs, but the layout is not.

Using div+css, it is easy to manipulate the DOM structure. Now the interaction is getting better and better, and a lot of js special effects are used. However, moving a ** cell will destroy the entire ** structure, not to mention any special effects.

Use ** when it's time to use it. Inherently ** data,If you use div,Of course, it's abuse.

Because div+css plays a great role in the layout and layout of **, it is mainly easy to include search engines. Of course, it's not good to go overboard, and excessive abuse of div will cause **unconcise, unfriendly to search engines, and affect the quality of **. Learning div+css mainly depends on persistence, reading more books on this subject, and referring to other people's examples.

The second is to go to some learning ** to see. Learning anything doesn't happen overnight, and I hope you succeed in the future.