onenaught.com

Just as web developers want to use standards on the client side, standards such as XSLT on the server side may be an efficient way to create good quality markup and other web output.

It can help avoid the hard coded or hard to edit HTML strings that are often seen in server side templates and scripts.

As an open standard, XSLT is reasonably universal, and skills can be easily transferable.

Some people don’t like it or have had bad experiences with it in the past.

But it can be a very powerful tool in the developer’s toolbox. Perhaps it is worth giving it another look?

This article looks at why XSLT could be useful as part of the View in an Model-View-Controller pattern, its benefits and potential drawbacks.

Read the full post titled, “Why Use XSLT in Server Side Web Frameworks For Output Generation?”

A couple of XSLT profilers have recently been announced.

One by Microsoft, and one by PHP for the up-coming PHP 5.3.

The PHP one is interesting as it can be invoked from within your PHP code thus profiling actual run time XSLTs.

Read the full post titled, “XSLT Profilers”

XSLT tips for cleaner code not only helps with maintenance and readability, but some of these also help improve performance. The first in a series of XSLT posts, this one concentrates mostly on cleaner coding. Tips cover areas such as xsl match templates versus named templates, xsl:for-each versus match templates, optimising use of variable declarations, using in-built XPATH functions for performance and easier to read code, and more.

Read the full post titled, “XSLT Tips for Cleaner Code and Better Performance”