Software engineering ideas in Web design

Today, the number of websites is growing, and the number of departments and personnel involved is also growing. Naturally, the scale of Web development groups is becoming more and more complex, and the resulting management difficulty is also growing. In the following article, I will discuss some related Web design concepts with you.
1. Is Web a software?
The earliest Web design was very simple. There were a lot of hyperlinks, and some places occasionally saw very advanced CGI (in the current environment ), the current Web has the need to closely connect with data, and many B/S structure applications have emerged in the current Web project, so there is no need to doubt, web has become an important branch of software.
2. Is Web design art or engineering?
Many people think that web design is an artistic type of work, and it is a place with a lot of storage space. Therefore, we often see many web design competitions, but do not ignore one problem, most Web design competitions only compare one or more pages, rather than a complete Web system. Is there any artistic sense in Apple's Web design?
The answer is yes. Why can't Apple influence the designer's art cell without limits? Even if we can put several classic design styles we have seen on it! But they didn't do this. I think the reason should be easily understood: the artistry of any Web design must be balanced with the engineering nature of the Web system.
Web is a software that has the ability to include a large amount of information on the user interface as the main interactive channel, so its artistic nature naturally reveals more obvious, I think that's why many people classify Web design into art and equate Web design with Web design.
3. Can Web designers be compared with the coder in programming?
This is a very interesting question. I used to remember that I have discussed the issue of Coder for high school students in the Indian software industry in the Delphi area. There are still many companies looking for web design on the market, how do they arrange their work after recruiting these designers? There should be many problems here.
The design capabilities of different web designers are naturally different. Sometimes the capabilities differ greatly, we cannot expect our company to have first-class designers (or the company may not be willing to pay for them), so I define general Web designers as Coder designers.
However, how can we reasonably arrange and make stable projects for people with poor abilities? In practical applications, we often use a set of uniform design methods (whether explicit or non-explicit), or more specifically, using methods such as templates, JS, and SSI outputs, for an development group that has defined related Web components, what developers need to do is not try to modify existing components (this will directly lead to changes to non-active demands), but based on the specific situation, design New components when necessary (of course, this kind of creative work is unlikely to be handed over to common Coder Web designers), and then the coder-level Web designers generate a large number of general pages, or use other software.