This site uses Extensible Stylesheet Language (XSL) templates for server-side JSP-driven transformation of XML content and metadata into HTML for presentation as dynamically served web pages.

You may have also noticed the consistent use of XSL-driven HTML markup of recurring definitions, sometimes with inclusion of default links, like: Drancing, Drancing, Drancel, Drancel, Drancel-RGB. Aha .. no need to repeat fancy colour or font markup or remember or track links, just edit in one place, the XSL Stylesheets !

I have done some simple Unified Modelling Language (UML)^TM modelling of the XSL file hierarchy of this site with custom stereotypes. Currently the XSL model is "by hand" since I don't have reverse-engineering of XSL (yet). This game is worthwhile in small doses, but don't push it too far; what is needed is reverse-engineering of the relationships between templates. The following UML "class" diagram of XSL templates is out-of-date, however it shows the general idea:

(Select image to enlarge in new window)

Pseudo-engineering of XSL using a UML class diagram and custom stereotypes.

Tip: I recommend using fine-grained XSL files to group templates, however this can cause file loading problems when transformations are applied by custom classes, in which case one need to implement the javax.xml.transform.URIResolver interface and set it as the resolver in your javax.xml.transform.Transformer.