Application Resources

This application relies on a number of resource files, these are outlined below


The top-level XSLT file - imports other XSLT resources.

Controls responses to user and system events and imports remaining XSLT.

Responsible for dynamic control over all visual elements in the application - except the rendered page.


JavaScript for managing state and for non-standard features like text-highlighting.


Controls all style and layout aspects of the application.


The host HTML page - loads the Saxon-CE processor and contains the 'skeleton' on which to hang the dynamic elements of the application.


References all the top-level documents containing article elements - represented as top-level nodes in the Table of Contents.


All the top-level documents - each one containing an HTML 5 article element with a number of nested section elements.


Intended container for all media files (such as graphics) referenced from within articles or sections.


HTML and other resources required for the Saxon.NET API - currently rendered as static HTML only.


(Optional) Directory for static HTML generated by XSLT 2.0 - run from an Ant task.


Images used by the application - should be kept separate from images referenced by the documentation (unless they serve both purposes).


All files in this directory should be auto-generated on a Saxon build. The build uses a Java doclet to create one 'master' XML file which is then processed by XSLT to partition, sort and group the data.


Used by the application to show the tree-view of the JavaDoc members.


The aggregated and processed well-formed content of HTML pages that describe each Saxon Java package and are maintained alongside the code.


File used as a rough indexing measure to locate Saxon Java types and functions.


Each XML file represents a Java package with data about each contained type, plus authored HTML comments (converted to well-formed XML by tagsoup).


All the imported XSLT files - each one responsible for rendering a different document structure or serving a specialist function - such as search and link-checking.


Contains resources for creating static HTML rendered from the XML files in the doc directory - output goes to the html directory.