From the time I was exposed to WEB standards in my sophomore year to my first job after graduation as "Page Reconstruction Engineer", from the time I came into contact with standards to the moderator of the Blue Ideal Standards Area for more than four years, WEB standards have become an important part of my life. A main theme. Why do I still mention this when "front-end development" is so popular? I think it is necessary to make a summary at the beginning of my new career.
Now that we are enlightened about web standards, it will not be that simple. We hope to look at web standards from an architectural level and look at them holistically. We hope to talk about this topic from the standpoint of many page engineers and business owners.
If the revolution is to be successful, the ideology must be unified. It is necessary for me to equip each web engineer's combat unit with a "political commissar" to supervise and remind web engineers at all times to conscientiously implement the central ideas and normative provisions of W3C without slacking off. I only have one thought in my mind, W3C standards are good!
This is the theme of my article "unify thinking and follow standards". No matter how tempted you are, non-standardized applications can help you increase your salary and get promoted, and the table layout can quickly complete your needs. You have to endure it. Stay and resist the temptation. Because temptations are temporary, truth is eternal.
Unified thinking, what is the idea of WEB standards?
First, it is the W3C series of specifications, html4.0, xhtml1.0, css2.1, ECMAScript, DOM, XML, etc. As a page engineer, you must learn to read the standards, recognize and understand the standards. To check whether your code is consistent with the standard, you need to understand the advantages and intentions of the W3C standard. If you use language distance, Mandarin allows Chinese people to communicate with each other, and English allows people around the world to communicate. The W3C standard is to allow pages to run on different terminals, so that users using various terminals can browse your pages, which means that it can be used by more popular users across platforms.
2. Separation of structure, performance, and behavior. Structure is the writing of strictly semantic HTML documents, CSS is the visual processing of HTML pages, and behavior is the dynamic change of the page, content modification, and function completion triggered by user behavior. etc. Separation is not a simple separation of files, but a strict division of labor. Don't use tables for layout, that's a CSS matter, and don't use hx to adjust font size, that's also a CSS matter. Structure = content + semantic interpretation content. Performance = how well the content on the page is presented. Behavior = user triggers to change content and HTML and CSS.
Web standards are a revolution. This is what I realized when I was at Tencent. Revolution is to overthrow the old and backward system and establish a new and advanced system.
Backward page engineer system, page code for artists, page code that can only be browsed by IE, page code that can be directly exported with graphics tools without writing code, page code that consumes a lot of traffic, and page code that is as slow as a snail , programmers get dizzy when they see the page code, and they have to be moved every time it is revised. The page code that is generated repeatedly is a kind of page code that makes page engineers and migrant workers the same.
Of course we must revolutionize it, replace it, and create a new page engineer system and page quality. The page code completed by independent page engineers, the page code that spans platforms, can be accessed and browsed by any device that can parse the page, and the handwritten page code , neat, well-structured, page code with the lowest traffic consumption, page code that programmers like, page code with super-fast access speed, revised and reusable page code, so that page engineers can raise their heads and proudly call themselves engineers , what is written is also the page code of computer code.
Revolutions will always produce resistance and regression. No matter how lazy, self-satisfied, or those who betray the standards for a small profit, the standards will gradually be criticized in front of them. No matter how low-level, mentally retarded programmers, there is no visual assistance. When we fill in the data there and talk about the excellent table layout, when the boss and project manager who has no vision demand urgent online use and graphics tools directly generate pages, our revolution encounters obstacles and resistance, and our confidence is also shaken. What should we do at this time? If we give up the revolution, we will fail and our ideals will be shattered. The future is bright, but the road is tortuous. We can only say that persistence is victory. Since China’s democratic revolution can succeed, why can’t our page revolution succeed? .
Summary: The revolution has not yet succeeded, and comrades still need to work hard. Unify your thoughts, eliminate distracting thoughts, and follow standards.