Regarding PHP templates, it is indeed easier said than done. There are probably more than 20 choices at random, and pear alone contains 5 different templates, which is really a headache.
Don’t just follow others’ opinions and say this is good and that is bad. Before choosing a template, it’s best to understand what the real purpose of the template is? Simply put, the core purpose of a template is a team work. There are two main ways of functioning:
1. Separating HTML and PHP makes the cooperation between web designers and PHP programmers more pleasant.
2. Separating display logic and transaction logic makes it easier and more flexible to change core transaction logic and expand applications, which means it makes cooperation between programmers more pleasant. (This point is often overlooked or misunderstood by people. They always think that taking PHP out of HTML is called separating display logic and transaction logic. If this is the case, why bother mixing PHP and HTML in the first place?)
Figure out this template What is the real purpose, it will be easier to make the right choice.
If you are the only PHP programmer but need to work together with other web designers, then choose a template that can separate HTML and PHP, phplib (now it seems to be integrated into Pear http:/ /pear.php.net/package/HTML_Template_PHPLIB) or
FastTemplate are such things, very simple and easy to use.
If your website interface is ugly and is mainly completed by programmers, but the functions are more complex and require powerful extension functions, and you need to separate various levels including display logic, then don’t use anything special, PHP itself This is the best template. It should be noted that in this case, you have to design your program very carefully, and always remember to separate not PHP and html but business logic and presentation logic. This is why I have always been very resistant to things like Smarty, because the syntax of Smarty is too complex and powerful, almost reinventing a scripting language (even PHP programmers have to relearn it). What's even more puzzling is that the more powerful this script is, the easier it is for people to mix business logic and presentation logic, destroying the original intention of the template.
If you want to separate HTML and PHP to get a better visual design, but also want the entire system to have very powerful expansion capabilities that can adapt to various interfaces of html, xml, and wml without having to learn complex syntax. It is a very challenging problem to provide high operating efficiency at the same time. The bad news is that there is currently no mature template that can really meet such requirements. The good news is that it is not difficult to complete such a template. If you try Zope or ColdFusion, you will find the shadow of this template,
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
