ProjectSpecification
- Uniform code formatting rules, otherwise git history will be very messy
- Git branches and tag naming rules
- The front-end route determines the url rules, where to use / [id] and which to use /? id= {id}
- Is there a need for seo, and is there a need for both H5/Mini programs/App or just one of them
- Css naming convention
- Determine the domain, path and whether httponly is required for cookie
- Do not use a version number like / v1 for baseUrl, and the docker parameter is the same.
- Direct use of new Date or moment ()-like methods that depend on the client environment in the project is prohibited.
- The intranet ip of each member of the team is set to static and written to the document.
- More than 15-bit (or ±2mm / 53) number is converted to string and then returned to the front end.
- Cdn picture naming rules