Normative purpose
In order to improve the efficiency of team collaboration, facilitate back-end personnel to add functions and front-end post-optimization maintenance, and output high-quality documents, this document is specially formulated. If there is something wrong or inappropriate in this document, please submit it in time, and it can be changed after discussion and decision.
Basic Guidelines
Comply with web standards, semantic HTML, separation of structure, performance and behavior, and excellent compatibility. In terms of page performance, the code is required to be concise, clear and orderly, to reduce the server load as much as possible and ensure the fastest parsing speed.
File specification
1. All html, css, js, and image files are archived in the agreed directory;
2. Name the html file: English name, suffix .htm. At the same time, place the corresponding interface draft in the same directory. If the interface draft is named in Chinese, please rename it with the same name as the html file to facilitate finding the corresponding page when adding functions to the backend;
3. CSS file naming: English naming, suffix .css. Common base.css, others are named according to module or page content
4. Js file naming: English naming, suffix .js. Common.js is shared, and other names are based on actual module requirements.