RawXml for /xsltFilter.xf

This website produced with XsltFilter. The Page.Response buffer output is shown below.

Return to normal view of page  

<? xml-stylesheet type="text/xsl" href="woric.xsl" ?>
<DisplayPage >
<title > XsltFilter </title>
<Content  Heading="What is XsltFilter"> XsltFilter is an ASP.NET module that performs server side Xsl Transformations without you writing any code. This type of ASP.NET module is called a Filter - hence the name XsltFilter. </Content>
<Content  Heading="Huh? What does XsltFilter actually do?"> It generates the Html which is sent to the browser. This allows the website developer to concentrate on building the site, rather than worrying about design issues or Html code. As an added benefit, the site automatically gets a consistent look and feel. </Content>
<Content  Heading="But someone has to write the Html"> In a perfect world a designer would design the site, a developer would write the code and the two would seamlessly merge to create a website. In the real world, a designer creates the site in static Html and a web developer creates a "dynamic" version of the website.<br/>
<br/>
If you are using XsltFilter, then someone must still turn the Html into a Xsl stylesheet which works with the developers Xml. Whilst this is not the perfect world scenario, its a little closer than previous ways of making websites. Usually its the web developer who maintains the Xsl stylesheet, but WSYIWYG tools for Xsl are available and some designers can write Xsl. </Content>
<Content  Heading="Can anyone use XsltFilter"> Yes - it is free and available with full soure code from <a href="http://xsltfilter.tigris.org"/>xsltfitler.tigris.org/</a>. All I ask is that you give me some feedback. [Seriously, anything from "I dont get it" to "you have a bug in your code" is helpful and appreciated.] <br/>
<br/>
<br/>
See the <a href="?_stylesheet=RawXml.xsl"/>Raw Xml/</a> for this page. </Content>
</DisplayPage>