This project is read-only.



  1. Configuration
  2. Writing templates
  3. Usage
  4. Integrating with ASP.NET MVC
  5. Web controls
  6. Data sources


Landscape design has its foundation on the following basic concepts


An XSL stylesheet which will be used to transform an XPath document.

When using it as a standalone, its transformation must produce a valid xml document with a root element at least

Otherwise, it can be used as the content of a wrapper


A Template which may wrap the result of the transformation of another template.

When the inner template is rendered, its transformation can produce some parameters that are passed to the transformation of the outer one, providing a quick method to disable some functionalities in the wrapper based on the transformation of the inner content.

Smart inclusion

By default, xslt processor resolve include paths based on the location of the template being processed. Landscape provides a quick way to define some include folders for xsl includes or imports, so templates do not rely on physical paths for inclusion.


An xsl stylesheet which can be transformed to a document fragment, or anything else when used with fantasy.

Template overriding

When working with multiple installations of the same website or application, it is a nice thing to reuse as much original presentation code as possible, for instance keeping the content part's template of the webpage untouched while acting on the outer levels for design customization.

To do so, Landscape implements a prioritized source folders lookup for templates, smart includes or widgets so that the source with the highest priority is searched first.

Last edited Nov 3, 2011 at 5:13 AM by Kunyo, version 19


No comments yet.