I hate to promote my own site (http://theexceptioncatcher.com) but I found that it made it a lot easier to separate the design of the site from the content. Most of my websites rarely ever change, so having a dynamic site is over kill. XSLT/XML helps to keep it as a static site, and I have the opportunity to change/fix the design at will.
Also, I've managed to setup a system to generate my resume via an XML/XSLT transform. I haven't published how I do that (or the public version [which is out of date]).
It's a tool and it can be very useful if you understand what you're doing. Additionally, there is Unix support for XSLT processing.
There are _so many_ template engines out there. Using XSLT to generate HTML is one of the most obtuse, obsolete ways you could possibly generate static pages.
The problem with a lot of those options is that the transformation happens on the server. I'm not really interested in doing that, with exception to googlebot. I want to keep everything static. It's hard to exploit a website that is all static.
That just means that you'd run them over your source locally and upload the static output to the web server. This is what most static blogging engines, like Jekyl, Pelican etc... do.
Also, I've managed to setup a system to generate my resume via an XML/XSLT transform. I haven't published how I do that (or the public version [which is out of date]).
It's a tool and it can be very useful if you understand what you're doing. Additionally, there is Unix support for XSLT processing.