What is the industrial practice on how to separate html and php code in a web project? Using echos to generate html is considered bad but what is the standard way to achieve the sought separation? Using template engines like twig?
Take the 2-minute tour
×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.
closed as too broad by gnat, GlenH7, World Engineer♦ Apr 8 at 0:14There are either too many possible answers, or good answers would be too long for this format. Please add details to narrow the answer set or to isolate an issue that can be answered in a few paragraphs.If this question can be reworded to fit the rules in the help center, please edit the question. |
|||||||||
|
|||||||||
|
The general practice is to put HTML in a template. A template contains minimum programming code: it's mostly HTML, with calls to variables and basic loops and conditional statements. The reason for that is that putting too much programming code in templates would:
A template engine, such as Smarty, is then used to transform the template into real content. |
|||
|
|
|
There are several aproaches, the one hand, using templates from the server side like Smarty, Twig, etc. I don't recommend this approach because you're coupling your presentation code to the technology used in the server (like php, python, ruby, java, ...). The other approach is to use client side templates/frameworks for the view (like ember, angularjs, backbone, ...). I recommend this approach due to the separation of concerns between view (html,css,js ...) and server code or controllers (php/symphony, python/django, ruby/rails, java/spring ...). So between your server code and your client code, the uniq glue you've to put is the model object in Json format (or whatever format you need). This way, you can develop code in the view that is reusable by any kind of server code, and thus, you can develop your application logic with different server technologies. |
|||
|
|
