Using XSLT with Content Management Systems
CMS systems which use XML and XSLT are very flexible, and much easier to implement than a traditional CMS system.
A comparison of the methodolgies should highlight the differences between them. For this comparison, we
will assume that a vendor is implementing an established CMS for a new client.
Storing the data
A XML based CMS uses a single table to store the content in an XML format. This differs from a traditional CMS
where there is a different table for each different type of content.
Comparing the data storage needs
|XML Based|| - no re-development (every implementation is identical)|
|Traditional CMS|| - re-develop the database to match the CMS requirements|
Editing the content
No matter what type of CMS is implemented, there must always be forms and form handlers to edit the CMS data.
With a traditional CMS you must also develop the database side of things for each implementation.
Comparing the development of an editing system
|XML Based|| - develop a form to display each type of content|
- develop a form handler to convert the text from each form into XML
|Traditional CMS|| - develop a form to display each type of content|
- develop a form handler for each form
- write code to read each type of content from the database
- write code to store each type of content in the database
Displaying the data
Use XSLT to transform that XML content into whatever HTML is defined in the XSLT stylesheet. (Note: If you have
chosen to use XSLT for the site, then there is no additional work to display the CMS based content.)
Comparing the development required to display the content
|XML Based|| - write XSLT template rules to format the XML as HTML. (req even if no CMS used)|
- every placeholder automatically finds the matching template rule (zero development)
|Traditional CMS|| - development required to read the CMS data from database|
- development required to format the database content as HTML.
- each placeholder must be correctly coded