CSS specification
- All CSS try to use external calls
- The homepage with longer code and the homepage of important sections can be directly embedded with CSS to avoid too long calling time, which makes the page appear messy because the CSS style is not called in time.
Technical rules
1. Database naming convention
- Table naming convention: The table name cannot exceed 30 characters, the first letter of a word is capitalized, and there is no connection symbol between multiple words.
- Field naming convention: try to use quoted words for fields, capitalize the first letter of words, and separate words with "_". The naming rule is "table category name_word", such as: User_Info, News_Content
- View naming convention: adopt the rule View_tableA_tableB_tableC, where View means "view". If this view is generated from several tables, use the connection character "_" to connect the names of several tables. If there are too many tables, the tables can be simplified appropriately.
- Stored procedure naming convention: P_surface_stored procedure (abbreviation), such as: P_User_Deleted.
2. Folder naming standard
Public folder:
| Types of | rule |
|---|---|
| Public pictures | /images |
| Style sheet | /styles |
| script | /scripts |
| download | /ftps |
| Website related materials and documents | /doc |
| Website documentation | /readme.txt |
| Website Help Document | /helps.htm |
| Website maintenance records | /mylogs.txt |
Other column names can be abbreviated with pinyin letters or English words. The meaning of all folders is in the readme.txt folder.
3. The naming convention of objects and variables.
Each variable name must first
Some little experience
- Content that can be represented by static web pages should be implemented dynamically without using program code as much as possible.
- In the design stage, it is necessary to fully communicate with the user and fully and accurately understand the user's needs. Neither can it distort the meaning of users, nor can it blindly cater to users' improper needs, nor can they boast about technologies that they are not sure of or even impossible to achieve. Needs analysis is a process of communication, exchange, guidance, education, struggle, and compromise. The results of the demand analysis should be archived in text.
- Technical parameters must be understood accurately. For example, the user's software platform is the linux series, so you must be clear about what development you want to use.
- When necessary, allow users to sign and seal the determined requirements.
Reference: https://blog.csdn.net/zhangking/article/details/13085