A list of technologies that Web front-end development engineers must know

Want to build and have a first-class web product development team, in the team member's basic ability must work hard. For Web front-end product development, it is not enough to master the simple "Web Web1.0" in the era of the Internet. With my own team, I hereby list the skills involved with the Web front-end product engineer:

Through many practical projects, the individual believes that a complete front-end product development team, must have the following talent staffing, but also hope that you can add:

All team members achieve a-level standard in all skills
All members of the team must master the B-level standards in both skills and ensure that all B-level standards are over 50% per cent of the team.
All members of the team must master the C-level standard of a skill and ensure that all C-level standards are over 25% per cent of the team.

Specific Skill Description:

"Essential" userinterface

Photoshop/fireworks Design

A-in conjunction with the art of the sketch to form a specific webpage design
B-ability to quickly produce layered high quality psd and PNG
C-Quickly design the PSD, PNG content into HTML code such as DIV+CSS or table

Flash Design

A-basic animation effects
B-Complex interaction system design, understanding of Third-party swf design software
C-Complex interactive system design and strong ability to integrate all kinds of out-of-town resources (PNG, JPG, MP3, WAV, etc.). Proficient in part of third party auxiliary design software (AE, SWiSHmax, Swift3d, etc.)

Prerequisites Browser-side (Web application)

Xhtml/css

A-basic layout implementation
B-strictly cross-platform layout implementation to
C-Elegant HTML code, as far as possible to meet the standards and have SEO considerations. Basic consistency in any platform or browser. Do not ask to know the hacks of various CSS, but ask how to access the information to meet the problem should be resolved in the first time. A DOM structure that provides the best operation for JavaScript developers, allowing JS developers to think "everything is ready" rather than "stretched" at the time of development.

Javascript/ajax/dom

A-basic DOM operation, understanding Ajax, can realize data communication
B-Basic DOM operations, able to write efficient OOP code to reduce maintenance costs
C-based on requirements, different development, choose the appropriate framework, to achieve the highest code efficiency, the best user experience, the minimum code download, and can be in a separate or even more product lines to maximize the reuse of code

Flash developement

A-based on the timeline ActionScript operation, can achieve simple interaction
B-Master A, can realize data layer communication (with server and local sharedobject)
C-Proficient in as1-3, can be based on the needs of various RIA development. Whether it is required to support FlashPlayer8 or FLASHPLAYER9, it is possible to develop the most efficient and flexible (such as interface design for HTML layers, etc.).

"Required" Client-side (Desktop application)

Apollo

A-product-level encapsulation, basic technology understanding (how to package, how to add HTML and JavaScript, etc.)
B-While mastering a, can use the Apollo API to design and develop OS file I/O function independently.
C-Understanding the "3D concept system" while mastering basic skills. Here "3D" namely: Design (designing), Development (development), Deploy (product deployment). can use Apollo

Windows presentation Foundation, wpf/e (Silverlight)

(Pending, Welcome to add)

"Supplemental" Server-side (modified: This skill does not participate in the rating after consideration)

The

1, server-side simple technologies, scripts, and 2, MediaServer (RED5) interface are used as a criterion for the "Web Front-End Engineer Skills list" (server, Data Logic layer skills). But it seems that many friends are skeptical about the need for front-end engineers to master server-side skills. Indeed, it is not easy to grasp the above presentation skills, and the front-end engineers are really hard. But, on the other hand, the reason for the hard work, I do not know when you fight div+css day and night when you think about it. In my experience, the front end of the hard is the following aspects:
Repeated labor, a large number of div+css are repeated, even if you can copy and paste, but thousands of rows of div in the sea to find an entrance I am afraid it is very painful
needs to become more, Often you toss a couple of hours to finally solve the cross-platform problem, and under IE6, 7 and Firefox can show the same effect, even JavaScript interaction is almost done. Suddenly it says that the demand is going to change. This is undoubtedly a great pain.
It may appear that this has nothing to do with server-side skills, but I feel that having a good server-side sense will certainly help (and certainly not solve all the problems). After all, the information structure and database are closely related, and server is the only way to connect to the database (at least for most B/s applications). Mastering the basic skills of the server side is important for designing interfaces with logical layer developers. and the HTML presentation layer is decoupled from the data during development and is also related to various template technologies on the server side. For example, the Smarty template in PHP (I used to), the MODEL2 concept of JSP and so on. How the HTML structure is designed, how to make HTML reusable, and even the development of OOP in the HTML layer (the front-end development process I am now designing in the new product line) requires server-side support. At the very least, you have to tell the PHP programmer what you need. If you don't know anything about PHP at all, it's impossible to talk about it.
In addition, for entrepreneurial teams, there are often very limited staff. In order to minimize operating costs, all technicians are obligated to have an understanding of server-side technology. If you're going to call a PHP programmer to connect to a remote server in order to change the title of a Web page, it really increases the operating costs of the entire company.
Summary: I think, can not understand the technical details, but should know the principle, it is best to master one or two sets of design ideas (after all, the data logic is here to go, just look at the HTML and JavaScript, the person's insight or limited, this limitation of my own long time), That would be a valuable asset.

"Supplemental" mobile-side (no participation rating)

Seeing a lot of friends saying that front-end engineers have no future, I wonder if mastering the skills of mobile devices is also a necessity for future development? Here to say a few more, about the technical staff's future, at present in the country really have to use "bleak" to describe. Impetuous atmosphere let technical personnel often prematurely give up their own technical career, and intrigues the overall moral level also let simple technical staff pain (I side too much, well, do not say specific details, hehe).
As a technical personnel, developers, in the maintenance of purely professional mentality (this is the premise, so no, nothing to talk about), but also learn how to protect themselves, how to strengthen themselves, society will not sympathize with you, only you can protect yourself.
Flashlite (Pending, Welcome to add)
Java? (Pending, Welcome to add)