As a front-end project engineer, it is not just to publicly process those beautiful HTML5, css3, and JavaScript special effects. A small and important part of the work is to make the project progress toward code stability and code standards. Design, information structure, and background restrictions all constitute a stumbling block for us to design sophisticated, concise, and impeccable front-end code. The following three practical skills are provided for you, but you must use them skillfully, because each skill is applicable.
In fact, it is quite difficult for a front-end project engineer to influence the project process. This is not to say that our work has no value, but that we have to solve the problem. The effect can be achieved simply by mixing CSS and JavaScript code. This solution is very easy to integrate into the system. As a front-end project engineer, it is also very difficult to send requests, mostly because we lack the standard data to elaborate on the problem and fear some unfavorable decisions. Fortunately, there are other ways to "Defend" us against "harm ".
1. Classic: Search Engine Optimization
When the Internet is finally oriented to the public, it will become more and more difficult for your webpage to be noticed in the ever-expanding network. At about the same time, semantic web designers started to play a role after abusing HTML for many years. At first, two seemingly unrelated concepts can be found in an unlikely marriage.
However, semantics makes things much more difficult. Writing HTML actually becomes a skill that requires such language knowledge. In addition, it benefits CSS, testability, and machines, but it is a pity that these three arguments are very unconvincing. Especially when the implementation of these new HTML structures leads to some backend development issues (it always does this and suddenly feels that the default CMS code is not good enough ).
But on the other hand, Seo has become the first level for our HTML designers thanks to Google Seo. Correct use of titles, paragraphs, and tables... are all taken into account when determining the location of a web page in the search results. This opens up a new path for forcing people to notice our HTML pages. It is a lever to push our own HTML pages into the project, so that not only CSS and evaluatable can benefit from it, but we can finally publish some reasonably structured HTML code.
2. Update classic: responsive
Nowadays, many CMS system makers create very good HTML pages, at least from the perspective of search engine optimization. Most of them are still irrelevant to HTML5 pages, which undoubtedly makes the SEO quota lose some weight. This does not mean that we must follow the default HTML page of the popular CMS system. Our new standard is responsive webpage design.
Although many CMS systems have very good control over semantic rules, most of them still lack the rational structure. This is often a real challenge to deal with responsive needs. A very rational structured easy structure allows us to identify the elements around us. Without it, we must return to the nasty javascriptheike and CSS structures.
Position: absolute; and box: Flex; here are our solutions. They need a specific structure, but often the default CMS code is missing, which means that their own HTML code actually needs a way to make everything work, so that the display of a page on different forms will not be damaged at any time.
3. New things: Performance
But what about CSS and JavaScript? Well, performance has been popular for the past one or two years ". Providing a good mobile user experience is the key to a well-executed site. Sorry (Ha !) The current status of the smartphone does not agree to have too many fancy decorations.
The technology of responsive images and the rework of responsive la s alone have taken us too much time and are usually accompanied by some functional requirements such as logging. This is where performance plays a role, because all those fancy solutions often rely on complex JavaScript and CSS. This dependency does not have to follow the specifications of the smartphone, resulting in fever, delay, and battery depletion.
Performance is measured when we want to narrow down functional complexity. Many recent tools can help us accurately infer the overall performance impact of specific technologies applied to a Web page, this is a huge help for us to block the implementation of detailed functional requirements.
Remind me
Remember: although all the three shards above are valid, they are not holy. Suppose you yell at others everywhere, because of performance issues, they cannot have X or Y, or because they do not have a solid foundation to support your ideas, such as responsive requirements, they need to implement Z, in this way, you must not work in a project for too long.
Use the above number of arguments in an appropriate case, but in a case that prevents its development, you can use them as a benchmark, laziness in some details can actually improve the overall quality of front-end code. Believe me, everyone else has done this (designers, information architects, backend developers), so don't feel terrible. You just need not to be too obvious when doing so.
Performance is a brand new SEO
