Summary of Web front-end development experience

With the advent of the Internet in the Web 2.0 era, a variety of similar desktop software Web applications have emerged, the site of the front-end of this has undergone tremendous changes. Web page is no longer just bearer single text and pictures, a variety of rich media to make the content of the page more vivid, the Web page of the interactive form of software to provide users with a better experience, these are based on the front-end technology to achieve, gifted college summed up the Web front-end development experience, with everyone to share.

First, from the Web standards, "Web standards" is a series of standards, including HTML4.0, XHTML1.1, CSS2.1, XML1.0, RSS2.0, ECMAScript1.1, DOM1.0, and so on, mainly for XHTML1.1 and A summary of some of CSS2.1 's experiences. What are the benefits of using web standards development?

1, save the operating costs.

How is the Web Standard production method done? Using Web-based standards, we can perform a form of separation, we use XHTML to express, with CSS to control (page element rendering) Form. Good page, XHTML code is basically the user to see the data, but also other cosmetic things, all by our CSS to control. This way our (XHTML) page volume is greatly reduced, so that your cost on the bandwidth will be reduced, this how to reduce, you can imagine, Yahoo home small 1k,100w personal access, then how much bandwidth savings? And the bandwidth can be used more fully. And our CSS control, all the page elements of the style, now want to change the overall style of the site, you only need to spend a few minutes to modify a CSS file, you can easily get it done. The cost of maintenance also came down, saving a lot of money?

2, more user-friendly, and have the opportunity to get more users

Now for the user-friendly. First of all, I want to divide our users into classes.

First Category: Ordinary users (everyone who visits our site), category II: Search engines;

Web-based standard development page, the structure is clear, the page volume is small, browser compatibility is good. When ordinary users visit, the page opens quickly, and regardless of the user's use of that browser, can normally access (display) the page, and the structure of the page is clear, to find the data can be easily browsed.

And for the search engine, a good use of web standards development of the page, have done SEO optimization, it is very friendly to access, it is easy to understand where your page is the title (H1~h6 tag), where is the paragraph (P tag), where the paragraph to emphasize the content (strong tag), etc., It can be easily analyzed. and a good SEO site, we all know that the search engine included more opportunities, this also means that your site will be more ordinary users to visit, to your site to bring more users.

One can save us a lot of money and improve our work efficiency. At the same time can improve the page browsing speed, user-friendly, and even can not spend money to promote, can bring you more users of technology. You say you're not going to use it? This is also the reason why our website is recommended to use Web Standard open Web site.

Finished with web standards, followed by XHTML and CSS techniques.

A reasonable layout. How do you start with a reasonable layout? We mentioned a few points of knowledge-"clear structure, SEO optimization, small page size, XHTML code is basically the user to see the data." These things are the result of a reasonable layout. And I personally think that everything we do with web standards starts with this knowledge, so I'm going to talk about it first.

Block-level elements. Block-level elements generate an element box, which, by default, fills the contents of its parent element and cannot have additional elements next to it. In other words, he generated a "delimited" character before and after the element box. The HTML element we are most familiar with is P and div.

In-line elements. The inline element generates an element box within a line of text without interrupting the line of text. The best example of inline elements is the a element in XHTML. Strong and Em also belong to the inline element. These elements do not generate a "delimiter" before or after it itself, so it can appear in the contents of another element without breaking its display.

Finally, the experience of Web front-end development is mainly the XHTML label full semantics, as little as possible nested, the page basically only shows the user need to see the data (we use CSS directly control the user needs to see the display of the data of the style), the page face search engine friendly (no CSS support, The page is also clear, hierarchical, and easy to view data.

Web front end development experience summary