Faint: "Use web2.0 to create standard-compliant pages"
|
Today someone talked to me about a website development project. When it came to the specific requirements, he said to me, "Use web2.0 to create standard pages." I fainted on the spot, thinking that if you don't understand, don't pretend. But in the end I decided to have an interview anyway. However, his words caused me to rethink the website reconstruction. Web2.0 is a historical concept, a stage, and an Internet model, but it is definitely not a technology; the web standard is a collection of standards. Its core is the complete separation of content, structure, presentation and behavior (I also added the content myself), which is very convenient for future revisions and maintenance. As for how much improvement it has made on browsing speed, I don't agree. When it comes to reconstruction, we must start with the content, because any improvement is for better display of content. So what is content? Content should be the real information that the page actually wants to convey, including data, documents or pictures. In essence, content refers to the most original data and is the basis of the page. Next, we have to talk about the main point of the page - structure, because the content without structure is almost unusable. A structure with good semantics will make the content more logical and easy to use. So the content and structure are an inseparable whole. Perhaps this is also the reason why the standard does not clearly point out the separation of content. When it comes to structure, many people's minds pop up the concept of "using div css for layout". I don't care whether this consciousness is right or wrong, because I always like to clarify the concept of a thing first: the structure is currently divided into two parts, one is the semantic structure, and the other is the code structure. The semantic structure is generated by the semantics of the tag itself (Note: I have never fully understood what semantics are, but now I can be clear about one thing: semantics contains the concept of some structure, but it is not equal to structure, and semantics has nothing to do with style). The code structure is program-oriented and requires human participation. Next, I would like to share my opinion on the above consciousness. First of all, I think the word "layout" should not appear. Maybe this is all caused by IE. In addition, a wrong concept must be corrected. The standard advocates the use of xhtml css instead of div css. This should be blamed on those friends who promote the standard. We should not confuse learners in order to achieve quick results. Just a joke. Since we are talking about div and table, I would like to talk about the difference between the two: div is semantic and code-structure oriented, it represents a part, and is used to define a division in a document. It displays the XML-based node structure through division, and generates structured rows through division. The specific application of nodes and rows has already appeared in the upcoming xhtml2.0, which uses section to represent nodes and line to represent rows. The focus of table should be on generating data columns and displaying tabular data, and it should never be used to divide structures. But at this point some friends may want to ask a question: If the tabular data displayed is a single column with multiple rows, can't it be achieved using ul/ol? If you really have such doubts, then I have to say that you don't understand the concept of tabular data. Tabular data refers to data whose expansion trend is columns. So when you expect the expansion trend to generate columns, even if it has only one column, you should use a table instead of a list, because the focus of ul/ol is on generating data. The key to the correct grasp and application of the two depends on one's foresight of the future page structure. I won't go on any further as it seems a bit off topic, let's get back to the structure, based on the renderings given by the design, we should consider all factors before we start, and strive to use a common structure to achieve the same effect, rather than constantly defining those small div units, so as to strive to achieve the most ideal state in design: the front desk can know with their eyes closed what kind of xhtml structure code is output by the back desk. For this purpose, we must fix xhtml. The specific implementation method is to use the H series to divide the large structure of the page, and use div to modularize local areas. When modularizing parts, since the meaningful dedicated elements in XHTML may not be enough, and it cannot create its own elements like XML, it is necessary to give them additional meaning by adding IDs or classes. To put it simply, the difference between the two is that id finds the structure/content first and then defines the style for it; class defines a style first and then applies it to multiple structures/contents. Specifically speaking, in the structure of XHTML, the scientific method is to use id as much as possible in large structures, especially peripheral elements, and use class as much as possible within the structure to make it universal, but it is best not to let class contain id. The relationship between the two is a bit like the parent-child relationship, but it should never be understood as a father-son or grandfather-grandson relationship. I don't want to say much about performance and behavior, just a simple description: the pure XHTML structure without added styles has UE, but no UI, which makes it impossible for CSS to surpass the core position of XHTML. Of course, I am not saying that performance is not important, because personally, a barbecue without seasoning or a movie without art is not attractive to me. As for javascript, as you get more familiar with and understand ajax, you will increasingly appreciate its special effects. However, from a behavioral level, its use is more often combined with CSS, which gives you another task when learning CSS. Original link: http://blog.5u96.cn/article.asp?id=30 |
<<: JavaScript to implement slider verification code
>>: Solve the problem of margin merging
Recommend
Analysis of MySQL crash recovery based on Redo Log and Undo Log
Table of contents MySQL crash recovery process 1....
Detailed explanation of semiotics in Html/CSS
Based on theories such as Saussure's philosop...
Why I recommend Nginx as a backend server proxy (reason analysis)
1. Introduction Our real servers should not be di...
Mysql 5.7.18 Using MySQL proxies_priv to implement similar user group management
Use MySQL proxies_priv (simulated role) to implem...
Causes and solutions for slow MySQL query speed and poor performance
1. What affects database query speed? 1.1 Four fa...
CSS3 realizes particle animation effect when matching kings
When coding, you will find that many things have ...
A brief discussion on mobile terminal adaptation
Preface The writing of front-end code can never e...
Tutorial on downloading, installing and deploying Tomcat to IDEA (with two hot deployment setting methods for IDEA)
Table of contents Tomcat Download Tutorial Tomcat...
MySQL group query optimization method
MySQL handles GROUP BY and DISTINCT queries simil...
Detailed steps for creating a Vue scaffolding project
vue scaffolding -> vue.cli Quickly create a la...
Use thead, tfoot, and tbody to create a table
Some people use these three tags in a perverted wa...
Axios cancels repeated requests
Table of contents Preface 1. How to cancel a requ...
Sample code for implementing multi-application deployment using tomcat+nginx
Table of contents Multi-application deployment 1-...
A brief discussion on spaces and blank lines in HTML code
All consecutive spaces or blank lines (newlines) ...
Detailed steps to install JDK and Tomcat in Linux environment
Table of contents 1. Install JDK Manual Installat...