Which CMS has the most correct templating?

Question

CMS

In which CMS is the most correct templating done - flexible and convenient for the template developer? Please share your thoughts on what not to do.

Answer 1

In those where XSLT is used.

Answer 2

In cms made simple, IMHO, everything is implemented very competently and elegantly. Sharpened on Smarty, which is very convenient for me personally. And in general, the CMS is good, modules are easy and convenient to write, made for people, while not piling up, like Joomla, everything is simple, easy and elegant. Fully justifies its name.

Answer 3

When I was still working in all sorts of CMS, I liked MODx. The only thing that is not usual in it (you can get used to it and even make it a plus, not a minus) is that all templates are stored directly in the database. Of course, you can pervert and make storage in files, but this makes no sense. The rest of the templates there can be made from layout by any manager

Answer 4

IMHO - MODx.
Clear, convenient, simple. You insert the necessary calls in the places you need (chunks, snippets, TV parameters) and everything is displayed without unnecessary garbage. Plus, full control over what kind of code these calls generate. Also on Smarty.

Answer 5

templating is implemented not so much in the CMS as in the template engine, and here, apparently, we need to talk about them.
I will say for CMS Drupal - there is a basic PHPTemplate templating engine, as alternatives you can fasten PHPTAL, Smarty, PHP XTemplate. Somewhere on the net I came across the fastening of templating engines in Ruby. Google, look, choose.

Answer 6

Correct - really XSLT (UMI?)
Flexible - PHP and other means of embedding JAPON :) in templates (drupal, wordpress, sorry gentlemen, CMS On rails with erb templates)
Convenient - subjective

Answer 7

XSLT yes, UMI no. This is the most convenient templating in HostCMS (similar to layout + view from ZF, only in the view a “third level” is possible - just XSL). Those. for static pages, XSL does not apply at all, only for data structures.

Answer 8

In fact, this is a very controversial issue. Personally, from my point of view, the correct templating is the one where you can’t shove logic, i.e., for example, Smarty templates or even Django framework templates. As far as I know, almost all popular CMSs allow you to use custom template engines.

Answer 9

Look at ExpressionEngine or, for very simple sites, at their own development MojoMotor

Answer 10

XML + XSLT output is done in Symphony CMS Symphony CMS, not to be confused with a framework.
The CMS itself is very correct. Working with it is like designing a database, and then writing database queries, and then pulling on the design results. And filling the site with information is filling the database, the interface is generated automatically.
However, there is a drawback - it slows down. The only solution is caching, there are plugins for caching.
The second disadvantage is that XSLT is not intended for sorting and selecting from ready-made queries to the database (results are issued in the form of XML), although it still knows how to do it! Get clear answers right away. Well, this applies to programming in general - there are programmers who have problems writing complex database queries.