First of all, this is a very unsystematic idea. After a period of formalized development process training and a period of accumulation, I started to complain.
Separation :
after separation
Structural development process:
For those responsible for page production, the structure is of course given to the backend and JS/DOM script developers, who implement the improved functions in the planning document. However, it is based on the structural document produced by the later production staff and cannot destroy the later structure.
Structure recognizer:
Structure is a language for machines to read. Naturally, it recognizes that it is a machine, so its greatest significance is to transfer data. The most interesting thing here is to extract data. Who will extract the data? I believe that most of the machines that extract data now are search engine robot crawlers, which means that the test and service targets of our structure are mainly search robots. Then SEO is the best standard to test our structure.
Establishing a set of standardized structures helps machines to easily understand our documents. Creating semantic documents also allows machines to easily extract the required data. Microformats are naturally a lazy way of extracting data. A set of semantic specifications is established based on the existing semantics. It can also be seen that the structure of XHTML is indeed unsatisfactory in this regard, and the move towards XML is mainly due to this reason.
Expression process
Compared with structure, CSS is oriented to the visual layer, which is recognizable by people. It is built on the UI layer and is naturally developed after receiving UI requirements.
Recognized by:
People, people are their identifiers, which means that CSS is for people and needs to provide information that can be seen or heard, mainly visible. In order to better let people see the information you deliver, it is necessary to cross browser types and versions, and it is necessary to cross devices. So as a CSS developer, your requirement is cross-platform. As for affinity, it is the more humane side. When facing people with physical disabilities, your requirements for recognizability are better and you have to do more.
Behavior process behavior, the popular rich client now, although it involves css and html, more of it is javascript, dom and xmlhttp. After the behavior needs to be clear, ideally all it needs is an interface, and the common ID is his interface. The process I came into contact with was to give it to the script developer after the html production was completed. But I think that after the requirements are clear, the script developer can develop an interface such as ID, and then wait until the page is completed and reference the js file.
Recognized by:
People, human behavior, that is, an interaction, is born on the basis of a good experience, the match between human behavior and expectations for behavior, and the results and expectations.
PM
The roles I once wanted to be but don't like now, they don't realize this at all. After talking about the interaction, they let the UI be designed, the pages be produced, and the programmers add functions... Their target needs are This page only requires that it can be used under IE5. I want to publish.
Version iteration The cycle of version iteration is very short. Changes in requirements and ambiguity are normal. So what is the significance of extending the life cycle and reducing costs? Development is still repeated, and new versions are constantly being released. The web is fast and slow, and it is impossible to give you enough time to consider whether your requirements are complete. Is it still necessary to apply web standards for development? Efficiency comes first!
Does production have to come after UI?
Can’t producers participate in product planning? Some UI designs are completely art based on pictures, without considering it as a web UI at all. The UI is CSS-oriented, and the structure is the responsibility of the producer. These are two completely independent elements, and both have such absolute importance. Why should the producer follow the UI and create documents according to the UI structure?
After I finished writing it, I felt that it was not interesting and I mostly complained about it!