I’m building a simple 10-page site using an MVC-like architecture. Is it worth learning the Smarty templating engine?
I’m building a simple 10-page site using an MVC-like architecture. Is it worth learning
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m building a simple 10-page site using an MVC-like architecture. Is it worth learning the Smarty templating engine?
Template engines add overhead.
You should only use a template engine if you need to have others create/edit templates and you do not want them to be able to use PHP.
If you are the sole maintainer, defiantly go with plain PHP. If your team can be trusted (they are all devs), stick with plain PHP. If you have designers that don’t know PHP or, more importantly, letting them use PHP is dangerous, then use Smarty or another template engine.
That being said, you are wondering if you should learn Smarty. You’ll need to learn Smarty if creating templates with Smarty. You don’t really need to learn Smarty if you are just implementing the Smarty template engine.