Xaraya

From Wikipedia, the free encyclopedia

Xaraya

Initial release	November 6, 2005 (2005-11-06)
Latest release	1.1.4 / January 3, 2008
Written in	PHP
OS	Cross-platform
Development status	Active
Genre	Content Management System, Web Application Framework
License	GNU General Public License
Website	www.xaraya.com

Xaraya is a Content Management System and is Free Software published under the GNU General Public License. Xaraya is written in the programming language PHP, and is based on the previously unpublished 0.8 branch of PostNuke (circa mid-2002).^[1]

Xaraya shares basic ideas with PostNuke in the area of modularity and security, but it has been completely rewritten with a focus on separation between design and content in order to achieve a more modular and flexible product. This added flexibility allows Xaraya to be used in many different ways, including blog portals, online communities, e-commerce and brochure sites.

1 Templating system
2 Dynamic Data
3 See also
4 References
5 External links

[edit] Templating system

Xaraya has a templating system developed specially for it, known as Block Layout. This makes it possible to customise most features of a website developed using Xaraya.

Block Layout supports the complete separation of code and layout. The output templates are written in XML, with 'xar' namespace tags providing variable access, looping constructs, conditional constructs and inclusion of sub-templates. The output from the standard themes are XHTML and RSS, though any other type of output can be generated.

Block Layout allows the developer to create adhoc "blocks" which can be constructed into full pages to create a versatile array of unique websites.

Xaraya can be operated with different databases, including MySQL, Postgres and SQLite.

[edit] Dynamic Data

A noteworthy core module of the Xaraya CMS is 'dynamic data'. This provides the functionality to define data objects using metadata (stored in the database). The data objects can be used to extend existing data objects in most modules, or to provide all the database access required in a module. The dynamic data objects can map onto individual physical tables, a single shared table, text files or any other underlying storage mechanism by extending classes.