It is true that we don't use Smarty "which any ole' coder can implement". We elected to use XSL so that "any ole' designer can implement" the look and feel for our client's program. I'm the first to say that both systems work and Smarty is a great technology. We just went a different way with implementation and we feel it suits the needs of our clients better.
We feel our clients are capable of designing more robust designs, considering all of us are in business on the internet. We like to provide our clients full visual control, so we've developed our XSL templating system. Our clients really like it.
Here's a great example of how unique our clients look and feel can be using the XSL:
http://www.mafias.com/
Basically, You just open the generic XSL template we provide in your editor, (like DreamWeaver) and you have the power to design everything for yourself. By doing this, we provide our clients true freedom of design.
Anyone who knows HTML will be able to use or even create simple XSL templates that he can use on his MPA3 pages. When one decides to change the design all they need to do is create a XHTML page and then copy our XSL template and everything will just work. No need to compile templates or know PHP.
Using XML/XSLT makes multi-language support in MPA3 REALLY easy. If you do the things right you can just send the XML files for translation, then upload them and that is all. You will have your MPA3 and your join pages in ANY language.
Considering the big world out there with new consumer countries, easily enabling our clients to serve their pages in any language is a pretty nice benefit.
