CMS/Smarty/QuickForm/XML
Keywords: CMS, content mangagement system, php, XML, Smarty, Pear, Quickform, UTF8, i18n
I have developed a few PHP-based CMSes for various clients. In most cases part of the requirements was that an off-the-shelf CMS would not be flexible enough. Input data usually came from an SQL DB, though in one case the data was both read and written from a very complex XML file (the same file was used for the print version of the data: a prestigious scientific journal). In all cases support for multiple Asian languages - not just Japanese - was a requirement so UTF8 was used.
Smarty was used as the template engine. I have found this easy to use, powerful and easy to extend. Designer resistance seemed common, but no better alternative was ever suggested.
Pear::QuickForm was used to quickly build edit forms on one system. On non-trivial forms this introduced as much complexity as it saved, so I am not convinced of its usefulness. However when I recently tried it again on a slightly simpler project I found a mistake in the examples that come with the documentation. Once that mistake was avoided it went more smoothly.
|
