<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>XSLT2.0 on ilikeorangutans</title><link>https://kuelzer.ca/tags/xslt2.0/</link><description>Recent content in XSLT2.0 on ilikeorangutans</description><generator>Hugo</generator><language>en</language><copyright>© 2026 Jakob Külzer</copyright><lastBuildDate>Sun, 12 Apr 2026 14:27:24 -0400</lastBuildDate><atom:link href="https://kuelzer.ca/tags/xslt2.0/index.xml" rel="self" type="application/rss+xml"/><item><title>Building a CMS with XML, XSLT, Ant, and ImageMagik</title><link>https://kuelzer.ca/posts/2010/01/03/building-a-cms-with-xml-xslt-ant-and-imagemagik/</link><pubDate>Sun, 03 Jan 2010 11:37:30 -0400</pubDate><guid>https://kuelzer.ca/posts/2010/01/03/building-a-cms-with-xml-xslt-ant-and-imagemagik/</guid><description>&lt;p&gt;Not so long ago a freelance client approached me with some updates for their website. The site has been growing organically since 2000 and therefore was a big mess. Several attempts to port the site to a CMS driven system failed largely because those CMS systems are usually to complex for our needs (Typo3) or not flexible enough (Joomla, WordPress). So as I was faced with updates to all the updates including image updates which in turn needed thumbnails to be generated. The same day I stumbled randomly over the &lt;a href="http://www.w3.org/TR/xslt20/"&gt;xsl:result-document&lt;/a&gt; function in XSLT 2.0 which allows you to transform a single XML file into several output files. That sparked an idea with me: why not use that to build a CMS system using XML technologies? I&amp;rsquo;ve toyed around with &lt;a href="http://cocoon.apache.org/"&gt;Cocoon&lt;/a&gt; a couple of years ago but that was not what I was looking for. So I looked for other technologies&amp;hellip;&lt;/p&gt;</description></item></channel></rss>