PHP website development plan (a must-read for new developers)_PHP tutorial

1. Development members

a) Project Manager
b) Page art
c) Page development
d)Server-side program development
e) System and data management
f)Testing and version control

2. Simple process for website team development

3. Development tools and environment

a) Server configuration
i. WEB server: FreeBSD6.1+Apache2.0+PHP5.0, SVN version control service (test machine only).
ii. Database server: WIN2003 server+SQL server 2000+MySQL5.0, CLUSTERED SERVER cluster service, mail server.
iii. 100M/1000M switch
b) Development tools
i. Front desk: Macromedia flash 8.0, Macromedia Dreamweaver 8.0, Adobe photoshop CS
ii. Backend: Zend Studio 5.2, SQL Server Enterprise Manager, PhpMyAdmin

4. Technical Rules

a) Browser compatibility strategy: Compatible with IE5.0 or above, and compatible with FireFOX2.0 or above browsers.
b) Search engine optimization: Focus on baidu, Google, and Yahoo search optimization and create a clear website map.
c) Character encoding rules: Chinese websites always adopt the GB2312 character standard.
d) File and folder naming: To be compatible with win32 and unix systems, lowercase letters are always used for naming.
e) Public file naming rules:
i. Default homepage: index.htm, index.html, index.php
ii. Main CSS file: style.css
iii. Main JS file: main.js
iv. Main program configuration file: config.php
f) Unified naming of public file directories
i. Picture directory: /images or /pic
ii. CSS style directory: /css
iii. JS script program directory:/js
iv. Template file directory: /tpl
v. Class or component directory: /class or /lib
g) Page script specifications: Uniformly use JavaScript
h) Class, function, and variable names in the code: use similar English word names, such as: DefaultClass or default_class
i) Code comment rules: All functions or procedures in the program must be accurately commented.
j) Database related rules
i. Data table and field naming rules: Name with all lowercase letters, and classify the naming prefix, such as: user table group, user_passport, user_info, user_service….
ii. Date type field: Unix timestamp is used uniformly, char(12)
iii. Primary key naming: All tables must have a primary key named after id.
k) Template component rules: Use compatible versions of Smarty and unified cache directories to facilitate permission control under Unix.
l) Database virtual layer: Use Adodb or Pdo uniformly, and SQL statements must be compatible with existing mainstream database rules.
m) Factory mode development rules: Develop or inherit component classes with comm.php as the center, and uniformly control file calling IO and class instantiation.
n) Object-oriented development rules: All functions must exist in the form of class ---> procedures.
o) SQL encapsulation rules: All SQL statements and database queries must exist in the process.
p) URL redirection rules: In order to optimize search engines, try to use Apache's mod_rewrite module to beautify the URL, such as: http://www.BkJia.com/action.php?id=123 converted to: http://www.BkJia .com/action/id/123 or http://www.BkJia.com/action/id_123.html

5. Website security and maintenance strategy

a) Server and database security:
i. Establish a complete virus defense mechanism, install a firewall, and close any unnecessary ports and services on the server.
ii. Manage user permissions in a unified manner, regularly track user and system events, and check system logs regularly.
b) Disaster recovery and backup mechanism:
i. Establish a database cluster and keep at least one server synchronized with data to ensure that the database system can automatically transfer to a normal server for stable operation when an accident occurs.
ii. Back up files and data regularly and save data and files through various methods.
c) Program security policy:
i. SQL injection prevention: Resolutely filter out unforeseen illegal characters, and strictly check SQL statements for database queries and updates.
ii. Do not use third-party source code from unknown sources, and do not easily copy unknown code to the server.