What processes and tools do senior front-end engineers have when developing traditional pages?

there is usually a fixed process when developing a SPA like Vue, such as scaffolding to generate npm dependencies, then install dependencies, personalize Webpack configuration, jslint configuration, and then start writing components and so on.

what are the processes for developing traditional pages (non-SPA)?

what we learned in school and online video is to manually introduce css,js, and then write html, directly in the editor and then open the browser to run the test. is this process out of date? (because sometimes the header and footer parts of a web page are common, without a back-end template engine, we all have to manually copy and paste this part. If you want to modify the html, of header or footer, you also need to modify one file after another. I"m sure there are more scientific and reasonable development processes and more convenient tools, such as Baidu"s FIS3, etc., but I"m still reading the documentation to learn) , ask senior front-end engineers to share your development process and tools, or there are relevant practical tutorials can also be recommended to us. Thank you!


obsolescence is obsolete, but the most basic things need to be understood. After experiencing the "inconvenience", you can better understand the ideas, principles, and convenience of existing tools.

I'm not a front-end senior engineer, and I don't usually use many of the advanced build tools that everyone uses, but I can give you a suggestion. If you first use the most primitive method of development, you will find some inconvenience, and then you will use webpack or other tools, or some UI framework, to experience the difference, and you will have your own feelings.


it is a good choice to use FIS3 when developing traditional projects. Api documents are relatively friendly, and many built-in functions can be used directly.
after you have some knowledge of fis, you can recommend to learn gulp, a tool based on task flow ideas. This tool requires you to configure a lot of things yourself to achieve development goals. You can deepen every step of the tool
finally, if you want to develop a webapp like spa in the future, you can contact webpack again


first of all, webpack can also develop multiple pages.
secondly, if you think webpack is too cumbersome, you can use gulp to develop it. Your so-called public header and common tail all have corresponding plug-ins to help you deal with them. All you need is and its simple configuration.

gulp can be configured in complex ways to achieve the same effect as webpack, but webpack is a better choice at that time.

  • How to use mpvue-simple?

    recently, the company is going to write WeChat Mini Programs, which is all written in the grammar of the original sound Mini Program. I recently heard that mpvue, is very popular, and decided to learn. I can want to write the original WeChat Mini Program...

Menu