forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r527010 [5/26] - in /forrest/trunk/site-author/content: ./ skins/ xdocs/ xdocs/docs_0_70/ xdocs/docs_0_70/howto/ xdocs/docs_0_70/howto/bugzilla-patch/ xdocs/docs_0_70/howto/cvs-ssh/ xdocs/docs_0_70/howto/multi/ xdocs/docs_0_80/ xdocs/docs_0...
Date Tue, 10 Apr 2007 03:48:57 GMT
Modified: forrest/trunk/site-author/content/xdocs/docs_0_70/howto/howto-pdf-tab.xml
URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/docs_0_70/howto/howto-pdf-tab.xml?view=diff&rev=527010&r1=527009&r2=527010
==============================================================================
--- forrest/trunk/site-author/content/xdocs/docs_0_70/howto/howto-pdf-tab.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_70/howto/howto-pdf-tab.xml Mon Apr  9 20:48:52 2007
@@ -16,67 +16,61 @@
   limitations under the License.
 -->
 <!DOCTYPE howto PUBLIC "-//APACHE//DTD How-to V1.2//EN" "http://forrest.apache.org/dtd/howto-v12.dtd">
-
 <howto>
- <header>
-  <title>How to create a PDF document for each tab</title>
-  <abstract>This How-To describes the generation of a PDF document for each
-    group of documents that is defined by a tab. 
-  </abstract>
-  <last-modified-content-date date="2005-07-19"/>
- </header>
-
+  <header>
+    <title>How to create a PDF document for each tab</title>
+    <abstract>
+      This How-To describes the generation of a PDF document for each group of
+      documents that is defined by a tab.
+    </abstract>
+    <last-modified-content-date date="2005-07-19"/>
+  </header>
   <audience title="Intended Audience">
     <p>
-      Users who need to generate one printable document aggregated from a
-      group of documents.
+      Users who need to generate one printable document aggregated from a group
+      of documents.
     </p>
   </audience>
-  
   <purpose title="Purpose">
     <p>
-      By default Forrest generates a pdf file for each separate document of
-      your project.
-      As well you can create a pdf of the whole site. But sometimes it may
-      be necessary to generate a pdf file out of selected tab, i.e. only for
+      By default Forrest generates a pdf file for each separate document of your
+      project. As well you can create a pdf of the whole site. But sometimes it
+      may be necessary to generate a pdf file out of selected tab, i.e. only for
       certain parts of the site.
     </p>
   </purpose>
-
   <prerequisites title="Prerequisites">
     <ul>
       <li>Understand how to create project-specific sitemaps by following the
       <link href="site:v0.70//your-project">Using Forrest</link> document.</li>
     </ul>
   </prerequisites>
-
   <steps title="Steps">
-    <p>The procedure outlined below will define a project
-      <code>sitemap.xmap</code> and create a new
-      <code>pdf-tab.xmap</code>.
-    </p>
-  <section id="sitemap">
-    <title>Create your project's main sitemap.xmap</title>
-    <p>
-      If you do not have already a sitemap then create a new empty one in your
-      <code>src/documentation</code> directory (or wherever
-      ${project.sitemap-dir} points to).
-    </p>
-  </section>
-
-  <section id="aggregator">
-    <title>Create another sitemap: pdf-tab.xmap</title>
     <p>
-    Like before create an empty sitemap and name it pdf-tab.xmap.
+      The procedure outlined below will define a project
+      <code>sitemap.xmap</code> and create a new <code>pdf-tab.xmap</code>.
     </p>
-  </section>
-
+    <section id="sitemap">
+      <title>Create your project's main sitemap.xmap</title>
+      <p>
+        If you do not have already a sitemap then create a new empty one in your
+        <code>src/documentation</code> directory (or wherever
+        ${project.sitemap-dir} points to).
+      </p>
+    </section>
+    <section id="aggregator">
+      <title>Create another sitemap: pdf-tab.xmap</title>
+      <p>
+        Like before create an empty sitemap and name it pdf-tab.xmap.
+      </p>
+    </section>
     <section id="mount">
-    <title>Edit project sitemap.xmap to mount pdf-tab.xmap</title>
-    <p>
-      Your sitemap should look something like this.
-    </p>
-    <source><![CDATA[
+      <title>Edit project sitemap.xmap to mount pdf-tab.xmap</title>
+      <p>
+        Your sitemap should look something like this.
+      </p>
+      <source>
+<![CDATA[
 <map:sitemap xmlns:map="http://apache.org/cocoon/sitemap/1.0">
   <map:pipelines>
     <map:pipeline internal-only="false">
@@ -91,16 +85,17 @@
     </map:pipeline>
   </map:pipelines>
 </map:sitemap>]]>
-    </source>
-  </section>
-
-  <section id="edit-aggregator">
-    <title>Edit the file <code>pdf-tab.xmap</code></title>
-    <p>
-      The <code><![CDATA[<map:match pattern="*.xml">]]></code> element
-      should look like the following:
-    </p>
-    <source><![CDATA[
+      </source>
+    </section>
+    <section id="edit-aggregator">
+      <title>Edit the file <code>pdf-tab.xmap</code></title>
+      <p>
+        The <code>
+<![CDATA[<map:match pattern="*.xml">]]>
+        </code> element should look like the following:
+      </p>
+      <source>
+<![CDATA[
 <map:sitemap xmlns:map="http://apache.org/cocoon/sitemap/1.0">
   <map:pipelines>
     <map:pipeline internal-only="false">
@@ -123,25 +118,28 @@
    </map:pipeline>
   </map:pipelines>
 </map:sitemap>]]>
-    </source>
-  </section>
-  <section id="edit-site">
-    <title>Edit your site.xml</title>
-     <note>
-        Do not use directories with "." in it. Replace them by "_"
-        e.g 1.2/ will not work in the aggregation. e.g. 1_2/ just works fine.
-    </note>
-    <p>
-      Add the following entry to your site.xml in the
-      <code><![CDATA[<about>]]></code> element
-    </p>
-    <source><![CDATA[... 
+      </source>
+    </section>
+    <section id="edit-site">
+      <title>Edit your site.xml</title>
+      <note>
+        Do not use directories with "." in it. Replace them by "_" e.g 1.2/ will
+        not work in the aggregation. e.g. 1_2/ just works fine.
+      </note>
+      <p>
+        Add the following entry to your site.xml in the <code>
+<![CDATA[<about>]]>
+        </code> element
+      </p>
+      <source>
+<![CDATA[... 
 <whole_foosite href="pdf-tab.html" label="sub site" />]]>
-    </source>
-    <p>
-      Your site.xml should look like this ...
-    </p>
-    <source><![CDATA[... 
+      </source>
+      <p>
+        Your site.xml should look like this ...
+      </p>
+      <source>
+<![CDATA[... 
 <about label="About">
   <index label="Index" href="index.html" description="Welcome to MyProj"/>
   <changes label="Changes" href="changes.html"
@@ -150,48 +148,57 @@
   <whole_foosite href="pdf-tab.html" label="pdf-tab" />
 </about>
 ...]]>
-    </source>
-    <p>
-      This allows you to link to it via a
-      <code><![CDATA[<link href="site:whole_foosite">]]></code>
-      reference. 
-    </p>
-	  <p>Add to every element that should be included in the pdf-tab.pdf
-      the attribute <code>wholesite="true"</code></p>
-	  <source><![CDATA[
+      </source>
+      <p>
+        This allows you to link to it via a <code>
+<![CDATA[<link href="site:whole_foosite">]]>
+        </code> reference.
+      </p>
+      <p>
+        Add to every element that should be included in the pdf-tab.pdf the
+        attribute <code>wholesite="true"</code>
+      </p>
+      <source>
+<![CDATA[
 <sample-wiki label="Wiki page" href="wiki-sample.html"
   description="wiki-sample" wholesite="true"/>]]>
-	  </source>
-	  <note>This attribute will be inherited by all children of the element. 
-	 Do not use it in the parent element that contains the 
-	 <code><![CDATA[<whole_foosite href="pdf-tab.html" label="pdf-tab" />]]></code> 
-	 as the child (will cause a <code>stack overflow</code> if you do)!!!
-	</note>
-  </section>
-  <section id="explain">
-    <title>Explanation of the operation</title>
-    <p>
-      Line 4 of our example
-      <br/>
-      <code><![CDATA[<map:parameter name="include" value="//*[@wholesite='true']"/>]]></code>
-      looks at your site.xml and will match every element containing the
-      <code>wholesite="true"</code> attribute. For example, to use the "samples"
-      tab ...
-    </p>
-    <source><![CDATA[
+      </source>
+      <note>
+        This attribute will be inherited by all children of the element. Do not
+        use it in the parent element that contains the <code>
+<![CDATA[<whole_foosite href="pdf-tab.html" label="pdf-tab" />]]>
+        </code> as the child (will cause a <code>stack overflow</code> if you
+        do)!!!
+      </note>
+    </section>
+    <section id="explain">
+      <title>Explanation of the operation</title>
+      <p>
+        Line 4 of our example
+        <br/>
+        <code>
+<![CDATA[<map:parameter name="include" value="//*[@wholesite='true']"/>]]>
+        </code> looks at your site.xml and will match every element containing
+        the <code>wholesite="true"</code> attribute. For example, to use the
+        "samples" tab ...
+      </p>
+      <source>
+<![CDATA[
 ...
 <samples label="Samples" href="samples/" tab="samples" wholesite="true">
 ...
 </samples>
 ...]]>
-    </source>
-    <p>
-      It matches <strong>all</strong> of the elements that contain
-      <code>wholesite="true"</code>
-      (in our example <code><![CDATA[<samples>]]></code>
-      and its "children") for the content of the pdf file to be generated.
-    </p>
-    <source><![CDATA[ 
+      </source>
+      <p>
+        It matches <strong>all</strong> of the elements that contain
+        <code>wholesite="true"</code> (in our example <code>
+<![CDATA[<samples>]]>
+        </code> and its "children") for the content of the pdf file to be
+        generated.
+      </p>
+      <source>
+<![CDATA[ 
 <samples label="Samples" href="samples/" tab="samples" wholesite="true">
  <sample2 label="Static content" href="sample2.html"      
    description="More Samples" wholesite='false'/>
@@ -199,31 +206,32 @@
    description="wiki-sample" />
  <sample-ihtml label="ihtml page" href="ihtml-sample.html"      
    description="Test iHTML page" />
-</samples> ]]>    	
-    </source>
-    <p>
-      This example shows that you can as well exclude site(s) from the aggregation 
-      by using the <code>wholesite="false"</code> attribute. This attribute will be as well inherited 
-      by all children of the element.
-    </p>
-    <p>
-      Line 8 defines the title of the pdf file by taking the content
-      of the project-name variable in
-      <code>skinconf.xml</code> and adding some funny text:
-      <br/>
-      <code><![CDATA[<map:parameter name="title" value="{conf:project-name}: Still My Foo Site"/>]]></code>
-    </p>
-  </section>
+</samples> ]]>
+      </source>
+      <p>
+        This example shows that you can as well exclude site(s) from the
+        aggregation by using the <code>wholesite="false"</code> attribute. This
+        attribute will be as well inherited by all children of the element.
+      </p>
+      <p>
+        Line 8 defines the title of the pdf file by taking the content of the
+        project-name variable in <code>skinconf.xml</code> and adding some funny
+        text:
+        <br/>
+        <code>
+<![CDATA[<map:parameter name="title" value="{conf:project-name}: Still My Foo Site"/>]]>
+        </code>
+      </p>
+    </section>
   </steps>
-
   <feedback title="Feedback and further development of this How-To">
     <p>
       Please provide feedback about this document via the
       <link href="site:mail-lists">mailing lists</link>.
     </p>
     <p>
-      In the future, this ability will probably be incorporated into the
-      main Forrest process.
+      In the future, this ability will probably be incorporated into the main
+      Forrest process.
     </p>
   </feedback>
 </howto>

Modified: forrest/trunk/site-author/content/xdocs/docs_0_70/howto/howto-view-contracts.xml
URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/docs_0_70/howto/howto-view-contracts.xml?view=diff&rev=527010&r1=527009&r2=527010
==============================================================================
--- forrest/trunk/site-author/content/xdocs/docs_0_70/howto/howto-view-contracts.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_70/howto/howto-view-contracts.xml Mon Apr  9 20:48:52 2007
@@ -16,38 +16,33 @@
   limitations under the License.
 -->
 <!DOCTYPE howto PUBLIC "-//APACHE//DTD How-to V2.0//EN" "http://forrest.apache.org/dtd/howto-v20.dtd">
-
 <howto>
- <header>
-  <title>How to write a forrest:contract?</title>
-  <abstract>
-    This How-To will explain how we wrote the contracts for views and hope afterwards you will be able to do the same.
-  </abstract>
-  <last-modified-content-date date="2005-06-06"/>
- </header>
-
+  <header>
+    <title>How to write a forrest:contract?</title>
+    <abstract>
+      This How-To will explain how we wrote the contracts for views and hope
+      afterwards you will be able to do the same.
+    </abstract>
+    <last-modified-content-date date="2005-06-06"/>
+  </header>
   <audience title="Intended Audience">
-
-<warning>
-"Views" are new functionality which is still in development phase. That is why it is in the
-"whiteboard" section of the Forrest distribution.
-This HowTo is a good start but still needs proof-reading.
-</warning>
-
+    <warning>
+      "Views" are new functionality which is still in development phase. That is
+      why it is in the "whiteboard" section of the Forrest distribution. This
+      HowTo is a good start but still needs proof-reading.
+    </warning>
     <p>
-      Devs and skin developer that wants to get started with forrest:contract development. 
-      To really understand this how-to you need basic and sometimes advanced understanding of 
-      the "old fashion" skin development process.
+      Devs and skin developer that wants to get started with forrest:contract
+      development. To really understand this how-to you need basic and sometimes
+      advanced understanding of the "old fashion" skin development process.
     </p>
   </audience>
-  
   <purpose title="Purpose">
     <p>
-      This setup guide will explain how to create a forrest:contract from scratch and 
-      how this forrest:contract work with the core parts of forrest.
+      This setup guide will explain how to create a forrest:contract from
+      scratch and how this forrest:contract work with the core parts of forrest.
     </p>
   </purpose>
-
   <prerequisites title="Prerequisites">
     <ul>
       <li>
@@ -61,22 +56,26 @@
       </li>
     </ul>
   </prerequisites>
-
-
   <steps title="Steps">
-    <note>The following content is from many mails around the topic, this how-to tries to be the 
-      consolidation of this thread. It is mainly based on the [RT] Why using views - 
-      in comparison with "old fashion" skins - usecase i18n</note>
+    <note>
+      The following content is from many mails around the topic, this how-to
+      tries to be the consolidation of this thread. It is mainly based on the
+      [RT] Why using views - in comparison with "old fashion" skins - usecase
+      i18n
+    </note>
     <p>
-      By working on the i18n integration for "pelt" we crossed again the whys for using views. ;-)
-      The maintainment problem was to change the captions of the skin features (contracts) to enable
-      support for i18n. The case is that the <code>site2xhtml.xsl</code> has a lot of repeating code. 
+      By working on the i18n integration for "pelt" we crossed again the whys
+      for using views. ;-) The maintainment problem was to change the captions
+      of the skin features (contracts) to enable support for i18n. The case is
+      that the <code>site2xhtml.xsl</code> has a lot of repeating code.
     </p>
     <p>
-      For example the "last-publish"-contract could be found 2 times in the code.  
-      This is not the only contract that was (is) double in the code. The problem with that is that 
-      we needed to search the code for each caption and senseless repeat the following 
-      maintainment step of adding the <![CDATA[<i18n:text/>]]>-tags.
+      For example the "last-publish"-contract could be found 2 times in the
+      code. This is not the only contract that was (is) double in the code. The
+      problem with that is that we needed to search the code for each caption
+      and senseless repeat the following maintainment step of adding the
+<![CDATA[<i18n:text/>]]>
+      -tags.
     </p>
     <source>
 <![CDATA[
@@ -89,17 +88,18 @@
     </source>
     <section id="enhanceMaintainment">
       <title>Enhance the maintainment</title>
-      <p>Now we can enhance the maintainment for the future and we give this code snippets 
-        contracts names (based on their functionality). This naming enables us to keep
-the contract separate from the position code itself. In xsl you would
-simply do:
+      <p>
+        Now we can enhance the maintainment for the future and we give this code
+        snippets contracts names (based on their functionality). This naming
+        enables us to keep the contract separate from the position code itself.
+        In xsl you would simply do:
       </p>
       <ol>
         <li>replace the script by <![CDATA[<xsl:call-template name="siteinfo-last-published"/>]]></li>
         <li>and add:</li>
       </ol>
-      
-      <source><![CDATA[<xsl:template name="siteinfo-last-published">
+      <source>
+<![CDATA[<xsl:template name="siteinfo-last-published">
  <script type="text/javascript">
   document.write("<i18n:text >Last Published:</i18n:text>&#160;" + document.lastModified);
  </script>
@@ -107,23 +107,25 @@
       </source>
       <p>
         This allows us in a next maintainment just change the code of
-        <![CDATA[<xsl:template name="siteinfo-last-published"/>]]> and apply it in any position where
-        it is placed.  
+<![CDATA[<xsl:template name="siteinfo-last-published"/>]]>
+        and apply it in any position where it is placed.
       </p>
       <note>
-        Now this refactoring of the site2xhtml.xsl is exactly what we doing in creating contracts for views.
+        Now this refactoring of the site2xhtml.xsl is exactly what we doing in
+        creating contracts for views.
       </note>
     </section>
     <section id="blankContract">
       <title>Explaining the blank forrest:contract</title>
       <p>
         To start a new forrest:contract you can copy the 'blank.ft' from
-        <code>org.apache.forrest.plugin.output.viewHelper.xhtml/resources/templates</code>. 
-        The exact file system path can be looked up at <code>http://localhost:8888/ls.contracts.html</code>.
+        <code>org.apache.forrest.plugin.output.viewHelper.xhtml/resources/templates</code>.
+        The exact file system path can be looked up at
+        <code>http://localhost:8888/ls.contracts.html</code>.
       </p>
       <p>
-        The 'blank.ft' is a simple xml file with the following code which you can use to base new contracts 
-        on:
+        The 'blank.ft' is a simple xml file with the following code which you
+        can use to base new contracts on:
       </p>
       <source>
 <![CDATA[<forrest:contract 
@@ -148,61 +150,82 @@
 ]]>
       </source>
       <p>
-        The most important is the name of the contract <code><![CDATA[<forrest:contract name="blank"/>]]></code>. 
-        This name is the same as the file name of the contract (without file extension) <code>blank.ft</code>. 
+        The most important is the name of the contract <code>
+<![CDATA[<forrest:contract name="blank"/>]]>
+        </code>. This name is the same as the file name of the contract (without
+        file extension) <code>blank.ft</code>.
       </p>
-      <note>This is a <strong>naming convention</strong> that you have
-        to always met. All @name has to be file name of the contract without file extension!
+      <note>
+        This is a <strong>naming convention</strong> that you have to always
+        met. All @name has to be file name of the contract without file
+        extension!
       </note>
       <p>
-        The <code><![CDATA[<description/>]]></code> tag needs to be filled in with some information
-        that is explaining the contract to the webdesigner. The better explained the more efficient
-        for the webdesigner to pick the right contract.
+        The <code>
+<![CDATA[<description/>]]>
+        </code> tag needs to be filled in with some information that is
+        explaining the contract to the webdesigner. The better explained the
+        more efficient for the webdesigner to pick the right contract.
       </p>
-      <source><![CDATA[<description>
+      <source>
+<![CDATA[<description>
   siteinfo-last-published-howto will output the last published date of the site with the help of jscript.
 </description>]]>
       </source>
       <p>
-        In the <code><![CDATA[<usage/>]]></code> tag we have to explain how the designer can use 
-        the contract in his view.
+        In the <code>
+<![CDATA[<usage/>]]>
+        </code> tag we have to explain how the designer can use the contract in
+        his view.
       </p>
-      <source><![CDATA[<usage>]]>&lt;![CDATA[<![CDATA[<forrest:contract name="siteinfo-last-published-howto"/>]]>]]&gt;<![CDATA[</usage>]]>
+      <source>
+<![CDATA[<usage>]]>&lt;![CDATA[<![CDATA[<forrest:contract name="siteinfo-last-published-howto"/>]]>]]&gt;<![CDATA[</usage>]]>
       </source>
       <p>
-        <code><![CDATA[<forrest:template name="blank" body="false" head="false">]]> </code> 
-        That leads to the template attribute @body="true" and
-				@head="false". In xhtml a contract can add content to the <![CDATA[<body/>]]> or/and
-				<![CDATA[<head/>]]> part of <![CDATA[<html/>]]>. This values have to be change when adding an actual template.
-        Besides this a xsl-template has to indicate this in the naming. A template that add content to the 
-        html body has to end with "<code>-body</code>"!!!
+        <code>
+<![CDATA[<forrest:template name="blank" body="false" head="false">]]>
+        </code> That leads to the template attribute @body="true" and
+        @head="false". In xhtml a contract can add content to the
+<![CDATA[<body/>]]>
+        or/and
+<![CDATA[<head/>]]>
+        part of
+<![CDATA[<html/>]]>
+        . This values have to be change when adding an actual template. Besides
+        this a xsl-template has to indicate this in the naming. A template that
+        add content to the html body has to end with "<code>-body</code>"!!!
       </p>
       <note>
-        It is possible to use contracts in different in/output-formats. 
-        We are focusing for now on format="xhtml" as ouput and the inputFormat="xsl".
+        It is possible to use contracts in different in/output-formats. We are
+        focusing for now on format="xhtml" as ouput and the inputFormat="xsl".
       </note>
       <p>
-        A <![CDATA[<forrest:template />]]> has the son <![CDATA[<xsl:stylesheet/>]]> where we can create 
-        templates for the html-head and html-body. For adding content into the body of the final 
-        document change @body="true" and add:
+        A
+<![CDATA[<forrest:template />]]>
+        has the son
+<![CDATA[<xsl:stylesheet/>]]>
+        where we can create templates for the html-head and html-body. For
+        adding content into the body of the final document change @body="true"
+        and add:
       </p>
       <source>
 <![CDATA[<xsl:stylesheet version="1.1" 
  xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
  <!--Add here the needed templates-->
  <xsl:template name="blank-body"/>
-</xsl:stylesheet>]]>        
+</xsl:stylesheet>]]>
       </source>
     </section>
     <section id="newContract">
       <title>Create a new contract</title>
       <fixme author="thorsten">
-        We need to explain basic naming convention for contracts. Like
-        "naming do not say about layout position but functionality of the contract.".
+        We need to explain basic naming convention for contracts. Like "naming
+        do not say about layout position but functionality of the contract.".
       </fixme>
-      <p> 
-				Now lets pick up the example we started with and create a "siteinfo-last-published-howto" contract.
-        Save the blank.ft to <code>{project.home}/src/documentation/resources/templates/siteinfo-last-published-howto.ft</code>.
+      <p>
+        Now lets pick up the example we started with and create a
+        "siteinfo-last-published-howto" contract. Save the blank.ft to
+        <code>{project.home}/src/documentation/resources/templates/siteinfo-last-published-howto.ft</code>.
       </p>
       <p>
         Now the maintainment optimized code (xpath="/html/body/*") was:
@@ -212,10 +235,12 @@
  <script type="text/javascript">
   document.write("<i18n:text >Last Published:</i18n:text>&#160;" + document.lastModified);
  </script>
-</xsl:template>]]></source>
-			<p>
-        In this code we have to do the following steps to use it in our contract:
-			</p>
+</xsl:template>]]>
+      </source>
+      <p>
+        In this code we have to do the following steps to use it in our
+        contract:
+      </p>
       <ul>
         <li>Search and replace "siteinfo-last-published" with "siteinfo-last-publish-howto-body"</li>
         <li>Add a "debug string - " to the template</li>
@@ -229,8 +254,11 @@
  <script type="text/javascript">
   document.write("<i18n:text >Last Published:</i18n:text>&#160;" + document.lastModified);
  </script>
-</xsl:template>]]></source>
-			<p>Now we have to do some last steps in the siteinfo-last-publish-howto.ft</p>
+</xsl:template>]]>
+      </source>
+      <p>
+        Now we have to do some last steps in the siteinfo-last-publish-howto.ft
+      </p>
       <ul>
         <li>Search and replace "blank" with "siteinfo-last-publish-howto"</li>
         <li>Add description and usage of the contract</li>
@@ -240,7 +268,8 @@
       <p>
         As the result your code should look like this:
       </p>
-      <source><![CDATA[<forrest:contract xmlns:forrest="http://apache.org/forrest/templates/1.0"
+      <source>
+<![CDATA[<forrest:contract xmlns:forrest="http://apache.org/forrest/templates/1.0"
   name="siteinfo-last-published-howto" type="nugget">
   <description>
     siteinfo-last-published-howto will output the last published date of the site with the help of jscript.
@@ -265,23 +294,25 @@
     <section id="viewContract">
       <title>Activating the contract</title>
       <p>
-        To see whether the new contract works we need to add it to our view.
-        The contract usage contains the contract-tag <code><![CDATA[<forrest:contract name="siteinfo-last-published-howto"/>]]></code>
-        Please see <a href="site:howto/view/DSL">Getting started with forrest:view DSL</a> for more details.
-      </p>
- 			<fixme author="thorsten">
-        Let us now look into advanced features of views. 
-        I will write a how-to for advanced contracts soon. :)
+        To see whether the new contract works we need to add it to our view. The
+        contract usage contains the contract-tag <code>
+<![CDATA[<forrest:contract name="siteinfo-last-published-howto"/>]]>
+        </code> Please see <a href="site:howto/view/DSL">Getting started with
+        forrest:view DSL</a> for more details.
+      </p>
+      <fixme author="thorsten">
+        Let us now look into advanced features of views. I will write a how-to
+        for advanced contracts soon. :)
       </fixme>
     </section>
   </steps>
   <extension title="Further Reading">
     <p>
-      Congratulations you are now able to work with view contracts. 
-      From here we recommend to read the following How-To's:
+      Congratulations you are now able to work with view contracts. From here we
+      recommend to read the following How-To's:
     </p>
     <ul>
-      <li><a href="site:howto/view/DSL">Getting started with forrest:view DSL</a> </li>
+      <li><a href="site:howto/view/DSL">Getting started with forrest:view DSL</a></li>
     </ul>
   </extension>
   <feedback title="Feedback">

Modified: forrest/trunk/site-author/content/xdocs/docs_0_70/howto/howto-view-dsl.xml
URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/docs_0_70/howto/howto-view-dsl.xml?view=diff&rev=527010&r1=527009&r2=527010
==============================================================================
--- forrest/trunk/site-author/content/xdocs/docs_0_70/howto/howto-view-dsl.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_70/howto/howto-view-dsl.xml Mon Apr  9 20:48:52 2007
@@ -16,37 +16,33 @@
   limitations under the License.
 -->
 <!DOCTYPE howto PUBLIC "-//APACHE//DTD How-to V2.0//EN" "http://forrest.apache.org/dtd/howto-v20.dtd">
-
 <howto>
- <header>
-  <title>How to use the forrest:view config-DSL</title>
-  <abstract>
-    This How-To describes the usage of the forrest:view config Domain Specific Language 
-    to create a beautiful website in no time.
-  </abstract>
-  <last-modified-content-date date="2005-06-06"/>
- </header>
-
+  <header>
+    <title>How to use the forrest:view config-DSL</title>
+    <abstract>
+      This How-To describes the usage of the forrest:view config Domain Specific
+      Language to create a beautiful website in no time.
+    </abstract>
+    <last-modified-content-date date="2005-06-06"/>
+  </header>
   <audience title="Intended Audience">
-
-<warning>
-"Views" are a new functionality which is still in development phase. That is why it is in the
-"whiteboard" section of the Forrest distribution.
-This HowTo is far from being finished. 
-</warning>
-
+    <warning>
+      "Views" are a new functionality which is still in development phase. That
+      is why it is in the "whiteboard" section of the Forrest distribution. This
+      HowTo is far from being finished.
+    </warning>
     <p>
-      This part of the views is dedicated to web designers and users with some knowlegde of css.
+      This part of the views is dedicated to web designers and users with some
+      knowlegde of css.
     </p>
   </audience>
-  
   <purpose title="Purpose">
     <p>
-      This how-to will show you how to write a <strong> forrest:view</strong>  from the ground up. 
-      We will focus on html as the output format and show how to add your own css implementation to the view.
+      This how-to will show you how to write a <strong> forrest:view</strong>
+      from the ground up. We will focus on html as the output format and show
+      how to add your own css implementation to the view.
     </p>
   </purpose>
-
   <prerequisites title="Prerequisites">
     <ul>
       <li>
@@ -60,89 +56,106 @@
       </li>
     </ul>
   </prerequisites>
-
   <steps title="Steps">
     <note>
-      When developing with views we assume you are using 'forrest run' and the following workflow:<br/>
+      When developing with views we assume you are using 'forrest run' and the
+      following workflow:
+      <br/>
       change files -> refresh browser
     </note>
     <p>
-      We developed <strong> forrest:view</strong>  to let the user decide where to place elements
-    	in, e.g., html pages.
-      We started this work with the <code>skinconf.xml</code> where you could configure certain elements and
-      their positions. These elements were known by established names and it was up to the skin-designer to support 
-      this configuration and the elements.
+      We developed <strong> forrest:view</strong> to let the user decide where
+      to place elements in, e.g., html pages. We started this work with the
+      <code>skinconf.xml</code> where you could configure certain elements and
+      their positions. These elements were known by established names and it was
+      up to the skin-designer to support this configuration and the elements.
     </p>
     <p>
-     We started by grouping the elements (from skinconf) and using css contracts that 
-     we added as @attributes, e.g. <code><![CDATA[<div id="content-main"/>]]> </code>. That made it 
-     possible to use the same elements in different skins. For the full list  of these contracts refer to the
+      We started by grouping the elements (from skinconf) and using css
+      contracts that we added as @attributes, e.g. <code>
+<![CDATA[<div id="content-main"/>]]>
+      </code>. That made it possible to use the same elements in different
+      skins. For the full list of these contracts refer to the
       <a href="http://svn.apache.org/repos/asf/forrest/trunk/main/webapp/skins/leather-dev/contracts.initial.txt">
-        initial contract list
-      </a>.
+      initial contract list </a>.
     </p>
     <p>
-     Around these contracts we developed a configuration Domain Specific Language and called it<strong> forrest:view</strong> .
-    <strong> forrest:view</strong> allows us to define the order in which <strong>forrest:contract</strong>s appear, and also to group
-     them using <strong>forrest:hook</strong>s.
+      Around these contracts we developed a configuration Domain Specific
+      Language and called it<strong> forrest:view</strong> . <strong>
+      forrest:view</strong> allows us to define the order in which
+      <strong>forrest:contract</strong>s appear, and also to group them using
+      <strong>forrest:hook</strong>s.
     </p>
     <p>
-     <strong>forrest:hook</strong>s are containers that are only used for layout reasons. They <strong>do not</strong> add 
-     any content nor functionality to the output. They add <strong>only</strong> layout information to 
-     the output. Actually a <code><![CDATA[<forrest:hook name="layoutId"/>]]></code> will be transformed
-     to <code><![CDATA[<div id="layoutId"/>]]> </code>
+      <strong>forrest:hook</strong>s are containers that are only used for
+      layout reasons. They <strong>do not</strong> add any content nor
+      functionality to the output. They add <strong>only</strong> layout
+      information to the output. Actually a <code>
+<![CDATA[<forrest:hook name="layoutId"/>]]>
+      </code> will be transformed to <code>
+<![CDATA[<div id="layoutId"/>]]>
+      </code>
     </p>
     <p>
-     <strong>forrest:contract</strong>s add functionality or extra content that a skin can use to display the requested
-     document (content-main). Sometimes a contract delivers <strong>format-specific markup</strong>, other times it delivers
-     a <strong>format-independent string</strong>.
+      <strong>forrest:contract</strong>s add functionality or extra content that
+      a skin can use to display the requested document (content-main). Sometimes
+      a contract delivers <strong>format-specific markup</strong>, other times
+      it delivers a <strong>format-independent string</strong>.
     </p>
     <section id="emptyView">
       <title>Empty view file</title>
-      <source><![CDATA[<forrest:views xmlns:forrest="http://apache.org/forrest/templates/1.0" >
+      <source>
+<![CDATA[<forrest:views xmlns:forrest="http://apache.org/forrest/templates/1.0" >
   <forrest:view type="xhtml">    
   </forrest:view>  
 </forrest:views>]]>
       </source>
       <p>
-       <strong> forrest:view</strong>  is designed to be available for any format that can use<strong>
-       	forrest:view</strong>  as a configuration file.
-	The only format we have implemented is xhtml for now. This is also true for the delivered contracts.
+        <strong> forrest:view</strong> is designed to be available for any
+        format that can use<strong> forrest:view</strong> as a configuration
+        file. The only format we have implemented is xhtml for now. This is also
+        true for the delivered contracts.
       </p>
       <p>
         Now lets start to skin our site. :)
       </p>
     </section>
-
     <section id="firstView">
-			<title>Creating your first view</title>
-			<p>
-				In this section we will create a new view. We will override the default view of the view plugin
-        for the index page of the <a href="site:howto/view/install">newSeed</a>.
-        To do this we will create a file called <code>index.fv</code> and save it in our xdocs directory. 
-				This will <strong>only</strong> make the index.html page look different from the rest of the project.
-			</p>
-      <p>
-        Remember: pointing your browser to <code>http://localhost:8888/ls.contracts.html</code> will
-        show a page with all contracts that you can use in your project.
-      </p>
-      <p>
-        Let's use the blank view from the earlier step and add the content-main contract. In 
-        ls.contracts.html we find the information about how to use the contract in our view. Our 
-        <code>index.fv</code> should look like:
+      <title>Creating your first view</title>
+      <p>
+        In this section we will create a new view. We will override the default
+        view of the view plugin for the index page of the
+        <a href="site:howto/view/install">newSeed</a>. To do this we will create
+        a file called <code>index.fv</code> and save it in our xdocs directory.
+        This will <strong>only</strong> make the index.html page look different
+        from the rest of the project.
+      </p>
+      <p>
+        Remember: pointing your browser to
+        <code>http://localhost:8888/ls.contracts.html</code> will show a page
+        with all contracts that you can use in your project.
       </p>
-      <source><![CDATA[<forrest:views xmlns:forrest="http://apache.org/forrest/templates/1.0" >
+      <p>
+        Let's use the blank view from the earlier step and add the content-main
+        contract. In ls.contracts.html we find the information about how to use
+        the contract in our view. Our <code>index.fv</code> should look like:
+      </p>
+      <source>
+<![CDATA[<forrest:views xmlns:forrest="http://apache.org/forrest/templates/1.0" >
   <forrest:view type="xhtml">    
     <forrest:contract name="content-main"/>
   </forrest:view>  
 </forrest:views>]]>
       </source>
       <p>
-        Let's try our new view by pointing to <code>http://localhost:8888/index.html</code>. 
-        We will see only the main content. :) Now let's add the section navigation to our view.
-        The contract usage in the view can be looked up in ls.contracts.html. Our view now looks like:
+        Let's try our new view by pointing to
+        <code>http://localhost:8888/index.html</code>. We will see only the main
+        content. :) Now let's add the section navigation to our view. The
+        contract usage in the view can be looked up in ls.contracts.html. Our
+        view now looks like:
       </p>
-      <source><![CDATA[<forrest:views xmlns:forrest="http://apache.org/forrest/templates/1.0" >
+      <source>
+<![CDATA[<forrest:views xmlns:forrest="http://apache.org/forrest/templates/1.0" >
   <forrest:view type="xhtml">    
     <forrest:contract name="content-main"/>
     <forrest:contract name="nav-section"/>
@@ -150,18 +163,20 @@
 </forrest:views>]]>
       </source>
       <p>
-        We now see the main content and the section navigation in the order 
-        we placed them in the view, but we want them next to each other 
-        (left: nav-section; right: content-main).
+        We now see the main content and the section navigation in the order we
+        placed them in the view, but we want them next to each other (left:
+        nav-section; right: content-main).
       </p>
     </section>
     <section id="hookView">
       <title>Hooks in views</title>
       <p>
-        We will now use for the first time a <code><![CDATA[<forrest:hook name="layoutId"/>]]></code>.
-        Hooks are the styling side of views. We can imitate an arbitrary html skeleton 
-        with their help. Before we explain how to use your own css in views we will use the default css.
-        In the default.css we can find 
+        We will now use for the first time a <code>
+<![CDATA[<forrest:hook name="layoutId"/>]]>
+        </code>. Hooks are the styling side of views. We can imitate an
+        arbitrary html skeleton with their help. Before we explain how to use
+        your own css in views we will use the default css. In the default.css we
+        can find
       </p>
       <source>/* menu */
 #leftbar {
@@ -172,21 +187,24 @@
 }
       </source>
       <p>
-        With this information we can see the purpose of <code><![CDATA[<forrest:hook name="leftbar"/>]]></code> 
-        and add contracts into that container. 
+        With this information we can see the purpose of <code>
+<![CDATA[<forrest:hook name="leftbar"/>]]>
+        </code> and add contracts into that container.
       </p>
       <p>
         If we want to put the nav-section contract into the left side position
         of the site we need to place the contract into that hook like so:
-      </p> 
-      <source><![CDATA[<forrest:hook name="leftbar">
+      </p>
+      <source>
+<![CDATA[<forrest:hook name="leftbar">
   <forrest:contract name="nav-section"/>
 </forrest:hook>]]>
-			</source>
+      </source>
       <p>
         Our view will then look like:
       </p>
-      <source><![CDATA[<forrest:views xmlns:forrest="http://apache.org/forrest/templates/1.0" >
+      <source>
+<![CDATA[<forrest:views xmlns:forrest="http://apache.org/forrest/templates/1.0" >
   <forrest:view type="xhtml">
     <forrest:hook name="leftbar">
       <forrest:contract name="nav-section"/>
@@ -199,15 +217,19 @@
     <section id="cssView">
       <title>CSS in views</title>
       <p>
-        We now know how to place contracts and hooks in our view, but until this stage we have only
-      	used the default.css. 
-        CSS support within views is as easy as placing contracts/hooks. To override the default.css
-        stylesheet we use another tag within our view <code><![CDATA[<forrest:css url="default.css"/>]]></code>.
+        We now know how to place contracts and hooks in our view, but until this
+        stage we have only used the default.css. CSS support within views is as
+        easy as placing contracts/hooks. To override the default.css stylesheet
+        we use another tag within our view <code>
+<![CDATA[<forrest:css url="default.css"/>]]>
+        </code>.
       </p>
       <p>
-      	Now we will create a new file as <code><![CDATA[{properties:skins-dir}{path}/{name}.css]]></code>. In our case
-        we will save a file called howTo.css in newSeed/src/documentation/skins/css/howTo.css containing only 
-        the following css:
+        Now we will create a new file as <code>
+<![CDATA[{properties:skins-dir}{path}/{name}.css]]>
+        </code>. In our case we will save a file called howTo.css in
+        newSeed/src/documentation/skins/css/howTo.css containing only the
+        following css:
       </p>
       <source>/* menu */
 #leftbar {
@@ -218,15 +240,22 @@
 }
       </source>
       <p>
-        We just changed the border-style to 'solid', the background to '#CCCCFF' and the color to '#000000'. 
-        Now we have to add a new tag to tell that we want to override the default.css. We are doing this 
-        by adding the tag <code><![CDATA[<forrest:css url="howTo.css"/>]]></code> to our view.
-      </p>  
+        We just changed the border-style to 'solid', the background to '#CCCCFF'
+        and the color to '#000000'. Now we have to add a new tag to tell that we
+        want to override the default.css. We are doing this by adding the tag
+        <code>
+<![CDATA[<forrest:css url="howTo.css"/>]]>
+        </code> to our view.
+      </p>
       <note>
-        <code><![CDATA[<forrest:css url="howTo.css"/>]]></code> has to be the direct son of 
-        <code><![CDATA[<forrest:view type="xhtml">]]></code>!!!
+        <code>
+<![CDATA[<forrest:css url="howTo.css"/>]]>
+        </code> has to be the direct son of <code>
+<![CDATA[<forrest:view type="xhtml">]]>
+        </code>!!!
       </note>
-      <source><![CDATA[<forrest:views xmlns:forrest="http://apache.org/forrest/templates/1.0" >
+      <source>
+<![CDATA[<forrest:views xmlns:forrest="http://apache.org/forrest/templates/1.0" >
   <forrest:view type="xhtml">
   	<forrest:css url="howTo.css"/>
     <forrest:hook name="leftbar">
@@ -237,11 +266,11 @@
 </forrest:views>]]>
       </source>
       <p>
-        Now you see a white page where the menu is sourrounded by a solid border with the defined background.
-         For a second example let's change the content-main by adding another hook 
-         <code><![CDATA[<forrest:hook name="content"/>]]></code>.   We need to add the new layout
-      	container
-         to our howTo.css:
+        Now you see a white page where the menu is sourrounded by a solid border
+        with the defined background. For a second example let's change the
+        content-main by adding another hook <code>
+<![CDATA[<forrest:hook name="content"/>]]>
+        </code>. We need to add the new layout container to our howTo.css:
       </p>
       <source>
 /* The actual content */
@@ -252,9 +281,11 @@
 }
       </source>
       <p>
-        Then we have to add the 'content-main' contract to the 'content' hook.  The resulting view looks like:
+        Then we have to add the 'content-main' contract to the 'content' hook.
+        The resulting view looks like:
       </p>
-      <source><![CDATA[<forrest:views xmlns:forrest="http://apache.org/forrest/templates/1.0" >
+      <source>
+<![CDATA[<forrest:views xmlns:forrest="http://apache.org/forrest/templates/1.0" >
   <forrest:view type="xhtml">
   	<forrest:css url="howTo.css"/>
     <forrest:hook name="leftbar">
@@ -267,22 +298,23 @@
 </forrest:views>]]>
       </source>
       <p>
-        We are now able to place contracts and layout containers and add custom css to the view.
+        We are now able to place contracts and layout containers and add custom
+        css to the view.
       </p>
       <fixme author="thorsten">
-        Let us now look into advanced features of views. 
-        I will write a how-to for advanced contracts soon. :)
+        Let us now look into advanced features of views. I will write a how-to
+        for advanced contracts soon. :)
       </fixme>
-      <!--<fixme author="thorsten">This section is next to be writen/finished</fixme>--> 
+<!--<fixme author="thorsten">This section is next to be writen/finished</fixme>-->
     </section>
   </steps>
   <extension title="Further Reading">
     <p>
-      Congratulations, you are now able to work with the view DSL. 
-      From here we recommend reading the following How-To's:
+      Congratulations, you are now able to work with the view DSL. From here we
+      recommend reading the following How-To's:
     </p>
     <ul>
-      <li><a href="site:howto/view/contracts">Create your own contract implementation</a> </li>
+      <li><a href="site:howto/view/contracts">Create your own contract implementation</a></li>
     </ul>
   </extension>
   <feedback title="Feedback">

Modified: forrest/trunk/site-author/content/xdocs/docs_0_70/howto/howto-view-install.xml
URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/docs_0_70/howto/howto-view-install.xml?view=diff&rev=527010&r1=527009&r2=527010
==============================================================================
--- forrest/trunk/site-author/content/xdocs/docs_0_70/howto/howto-view-install.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_70/howto/howto-view-install.xml Mon Apr  9 20:48:52 2007
@@ -16,54 +16,50 @@
   limitations under the License.
 -->
 <!DOCTYPE howto PUBLIC "-//APACHE//DTD How-to V2.0//EN" "http://forrest.apache.org/dtd/howto-v20.dtd">
-
 <howto>
- <header>
-  <title>How to install the view package</title>
-  <abstract>
-    This How-To describes the setup of the plugins (needed to work with forrest:views and forrest:contracts) and a fresh seed.
-  </abstract>
-  <last-modified-content-date date="2005-06-06"/>
- </header>
-
+  <header>
+    <title>How to install the view package</title>
+    <abstract>
+      This How-To describes the setup of the plugins (needed to work with
+      forrest:views and forrest:contracts) and a fresh seed.
+    </abstract>
+    <last-modified-content-date date="2005-06-06"/>
+  </header>
   <audience title="Intended Audience">
-
-<warning>
-"Views" are a new functionality which is still in development phase. That is why it is in the
-"whiteboard" section of the Forrest distribution.
-This HowTo is a good start but still needs proof-reading.
-</warning>
-
+    <warning>
+      "Views" are a new functionality which is still in development phase. That
+      is why it is in the "whiteboard" section of the Forrest distribution. This
+      HowTo is a good start but still needs proof-reading.
+    </warning>
     <p>
-      Users/devs who wants to get started with view development.
-      This setup guide is valid for both users and devs.
+      Users/devs who wants to get started with view development. This setup
+      guide is valid for both users and devs.
     </p>
   </audience>
-  
   <purpose title="Purpose">
     <p>
       To help users install views. This is the "getting started" setup-guide.
     </p>
   </purpose>
-
   <prerequisites title="Prerequisites">
     <ul>
       <li>You have to use the trunk version of forrest to use views because it is in an early stage
       	of development.</li>
     </ul>
   </prerequisites>
-
   <steps title="Steps">
     <p>
-      The process of setting up the plugin is quite involved. We promise it will be easier in the future. 
-      Some of the instructions have to be modified with your local settings.
+      The process of setting up the plugin is quite involved. We promise it will
+      be easier in the future. Some of the instructions have to be modified with
+      your local settings.
     </p>
     <section id="localBuild">
       <title>Build the view and the viewHelper plugins</title>
       <p>
-        The first step is to build the view and the viewHelper plugins. Change to a console of your choice
-        and go (cd) to the trunk version of forrest {forrest-trunk}. Then do an update and after this 
-        deploy both plugins locally.
+        The first step is to build the view and the viewHelper plugins. Change
+        to a console of your choice and go (cd) to the trunk version of forrest
+        {forrest-trunk}. Then do an update and after this deploy both plugins
+        locally.
       </p>
       <source>
 cd {forrest-trunk}
@@ -76,11 +72,12 @@
     </section>
     <section id="newSeed">
       <title>Seed a new project</title>
-      <p> 
-				Go to the dir where you want to seed a new project and seed it. 
-        Next we have to prepare a default.fv directory ("conf") in project.conf-dir (forrest.properties) 
-        of the fresh seed. This will be needed as soon you modify the default view of your project.
-        A "templates" directory is needed as well, for your project-specific contract implementations.
+      <p>
+        Go to the dir where you want to seed a new project and seed it. Next we
+        have to prepare a default.fv directory ("conf") in project.conf-dir
+        (forrest.properties) of the fresh seed. This will be needed as soon you
+        modify the default view of your project. A "templates" directory is
+        needed as well, for your project-specific contract implementations.
       </p>
       <source>
 cd ~/src/newSeed
@@ -92,72 +89,85 @@
     <section id="forrestProperties">
       <title>Modifying forrest.properties</title>
       <p>
-        Now we have to tell forrest that we are planning to use the view plugins. We will do that
-        by editing to the forrest.properties to add the plugins:
+        Now we have to tell forrest that we are planning to use the view
+        plugins. We will do that by editing to the forrest.properties to add the
+        plugins:
       </p>
       <source>
 project.required.plugins=org.apache.forrest.plugin.output.viewHelper.xhtml,org.apache.forrest.plugin.internal.view
       </source>
       <p>
-	     We also have to change the project skin to leather-dev. The reason for this is that the plugins are still
-       not independent from the "old fashion skins".  
-      </p>
-      <note>We are exchanging only site2xhtml.xsl of leather-dev skin by the plugins and some contracts 
-      	are based on e.g. document2html.xsl output of leather-dev.</note>
-    	<source>
+        We also have to change the project skin to leather-dev. The reason for
+        this is that the plugins are still not independent from the "old fashion
+        skins".
+      </p>
+      <note>
+        We are exchanging only site2xhtml.xsl of leather-dev skin by the plugins
+        and some contracts are based on e.g. document2html.xsl output of
+        leather-dev.
+      </note>
+      <source>
 project.skin=leather-dev
       </source>
     </section>
     <section id="testing">
       <title>Test your new view-based project</title>
-      <p> 
+      <p>
         Now you have finished the preparation and the setup to finally try
       </p>
       <source>
 forrest run
       </source>
-      <p>then point to <a href="http://localhost:8888/">http://localhost:8888/</a> and you should see the default
-        view-based skin.</p>
-      <note>When developing styles with views 'forrest run' is the quickest
-way. You will see you do not have to build your project to see the
-changes on your pages when working with *.fv. </note>
+      <p>
+        then point to
+        <a href="http://localhost:8888/">http://localhost:8888/</a> and you
+        should see the default view-based skin.
+      </p>
+      <note>
+        When developing styles with views 'forrest run' is the quickest way. You
+        will see you do not have to build your project to see the changes on
+        your pages when working with *.fv.
+      </note>
     </section>
     <section id="availableContracts">
-	    <title>Available contracts</title>
-	    <p> 
-	     To start working with views you need to know which contracts you can use. 
-	     For this we will install another plugin <code>org.apache.forrest.plugin.input.viewHelper.xhtml.ls</code>.
-	     The setup is:
-	    </p>
-	    <source>
+      <title>Available contracts</title>
+      <p>
+        To start working with views you need to know which contracts you can
+        use. For this we will install another plugin
+        <code>org.apache.forrest.plugin.input.viewHelper.xhtml.ls</code>. The
+        setup is:
+      </p>
+      <source>
 cd {forrest-trunk}
 svn up
 cd whiteboard/plugins/org.apache.forrest.plugin.input.viewHelper.xhtml.ls/
 ant local-deploy
 </source>
-			<p>
-        The newly installed plugin will show the available contracts listed in an html page.
-        First we have to tell forrest that we are planning to use the new plugin. We will do that
-        by editing the forrest.properties of the <a href="site:howto/view/install">newSeed</a> 
-        to <strong>add</strong> the plugin:
+      <p>
+        The newly installed plugin will show the available contracts listed in
+        an html page. First we have to tell forrest that we are planning to use
+        the new plugin. We will do that by editing the forrest.properties of the
+        <a href="site:howto/view/install">newSeed</a> to <strong>add</strong>
+        the plugin:
       </p>
       <source>
 project.required.plugins=org.apache.forrest.plugin.input.viewHelper.xhtml.ls
       </source>
       <p>
-        Now point your browser to <code>http://localhost:8888/ls.contracts.html</code>. 
-        On this page you will find all contracts that you can use in your project.
+        Now point your browser to
+        <code>http://localhost:8888/ls.contracts.html</code>. On this page you
+        will find all contracts that you can use in your project.
       </p>
     </section>
   </steps>
   <extension title="Further Reading">
     <p>
-      Congratulations, you are now able to work with views. 
-      From here we recommend reading the following How-To's:
+      Congratulations, you are now able to work with views. From here we
+      recommend reading the following How-To's:
     </p>
     <ul>
-      <li><a href="site:v0.70//howto/view/DSL">Getting started with forrest:view DSL</a> </li>
-      <li><a href="site:v0.70//howto/view/contracts">Create your own contract implementation</a> </li>
+      <li><a href="site:v0.70//howto/view/DSL">Getting started with forrest:view DSL</a></li>
+      <li><a href="site:v0.70//howto/view/contracts">Create your own contract implementation</a></li>
     </ul>
   </extension>
   <feedback title="Feedback">

Modified: forrest/trunk/site-author/content/xdocs/docs_0_70/howto/index.xml
URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/docs_0_70/howto/index.xml?view=diff&rev=527010&r1=527009&r2=527010
==============================================================================
--- forrest/trunk/site-author/content/xdocs/docs_0_70/howto/index.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_70/howto/index.xml Mon Apr  9 20:48:52 2007
@@ -16,13 +16,10 @@
   limitations under the License.
 -->
 <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN" "http://forrest.apache.org/dtd/document-v12.dtd">
-
 <document>
-
   <header>
     <title>Overview of the How-To documents</title>
   </header>
-
   <body>
     <section>
       <title>Forrest Site and Documentation</title>
@@ -40,7 +37,6 @@
         </li>
       </ul>
     </section>
-    
     <section>
       <title>Using Forrest</title>
       <ul>
@@ -67,7 +63,6 @@
         </li>
       </ul>
     </section>
-    
     <section>
       <title>Extending Forrest</title>
       <ul>
@@ -77,5 +72,4 @@
       </ul>
     </section>
   </body>
-
 </document>

Modified: forrest/trunk/site-author/content/xdocs/docs_0_70/howto/multi/howto-multi.xml
URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/docs_0_70/howto/multi/howto-multi.xml?view=diff&rev=527010&r1=527009&r2=527010
==============================================================================
--- forrest/trunk/site-author/content/xdocs/docs_0_70/howto/multi/howto-multi.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_70/howto/multi/howto-multi.xml Mon Apr  9 20:48:52 2007
@@ -16,73 +16,81 @@
   limitations under the License.
 -->
 <!DOCTYPE howto PUBLIC "-//APACHE//DTD How-to V1.2//EN" "http://forrest.apache.org/dtd/howto-v12.dtd">
-
 <howto>
   <header>
     <title>Example of a multi-page how-to</title>
-    <abstract>This is the shell of a multi-page how-to. Add your own content.
+    <abstract>
+      This is the shell of a multi-page how-to. Add your own content.
     </abstract>
     <last-modified-content-date date="2003-09-10"/>
   </header>
-
   <audience title="Intended audience">
-     <p>Describe the audience here.</p>
+    <p>
+      Describe the audience here.
+    </p>
   </audience>
-
   <purpose title="Purpose">
-    <p>Explain the purpose of the howto here.</p>
+    <p>
+      Explain the purpose of the howto here.
+    </p>
   </purpose>
-
   <prerequisites title="Prerequisites">
-    <p>Configuration requirements:</p>
-    <ul> 
+    <p>
+      Configuration requirements:
+    </p>
+    <ul>
       <li>This.</li>
       <li>That.</li>
     </ul>
-    <p>Requisite skills:</p>
-    <ul> 
+    <p>
+      Requisite skills:
+    </p>
+    <ul>
       <li>These.</li>
       <li>Those.</li>
     </ul>
-
   </prerequisites>
-
   <steps title="Various Steps">
-    <p>After this brief introductory paragraph, the steps are described in
-     separate documents:</p>
+    <p>
+      After this brief introductory paragraph, the steps are described in
+      separate documents:
+    </p>
     <ul>
       <li><link href="step1.html">Step 1: Do foo</link></li>
       <li><link href="step2.html">Step 2: Do foobar</link></li>
       <li><link href="step3.html">Step 3: Finish up</link></li>
     </ul>
   </steps>
-
   <extension title="Real World Extension">
-   <p>Briefly describe some relevant extensions that go beyond these basics.</p>
-  </extension> 
-
+    <p>
+      Briefly describe some relevant extensions that go beyond these basics.
+    </p>
+  </extension>
   <tips title="Tips">
-   <p>If you have a problem running the example, then you can try the
-    following tips:</p>
-   <ul>
-     <li>Tip #1</li>
-     <li>Tip #2</li>
-   </ul>
-  </tips> 
-
+    <p>
+      If you have a problem running the example, then you can try the following
+      tips:
+    </p>
+    <ul>
+      <li>Tip #1</li>
+      <li>Tip #2</li>
+    </ul>
+  </tips>
   <references title="Related Resources">
-    <p>Cocoon resources:</p>
+    <p>
+      Cocoon resources:
+    </p>
     <ul>
       <li>For all Cocoon basics see the
         <link href="ext:cocoon">Cocoon Web site</link>.
       </li>
     </ul>
   </references>
-    
   <feedback title="Feedback">
-    <p>If you find any faults in this How-to or can see any improvements,
-      please contact the
-      <link href="site:mail-lists">project mail lists</link> with them.
+    <p>
+      If you find any faults in this How-to or can see any improvements, please
+      contact the <link href="site:mail-lists">project mail lists</link> with
+      them.
     </p>
   </feedback>
 </howto>

Modified: forrest/trunk/site-author/content/xdocs/docs_0_70/howto/multi/revision-howto-multi-2003-09-14.xml
URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/docs_0_70/howto/multi/revision-howto-multi-2003-09-14.xml?view=diff&rev=527010&r1=527009&r2=527010
==============================================================================
--- forrest/trunk/site-author/content/xdocs/docs_0_70/howto/multi/revision-howto-multi-2003-09-14.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_70/howto/multi/revision-howto-multi-2003-09-14.xml Mon Apr  9 20:48:52 2007
@@ -16,21 +16,20 @@
   limitations under the License.
 -->
 <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN" "http://forrest.apache.org/dtd/document-v12.dtd">
-
 <document>
   <header>
     <title>Sample Revision notes</title>
   </header>
-
   <body>
     <section>
       <title>Some text here</title>
-      <p>There is a problem with this approach</p>
+      <p>
+        There is a problem with this approach
+      </p>
       <ul>
         <li>Problem A.</li>
         <li>Problem B.</li>
       </ul>
     </section>
   </body>
-
 </document>

Modified: forrest/trunk/site-author/content/xdocs/docs_0_70/howto/multi/revision-howto-multi-2003-09-15.xml
URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/docs_0_70/howto/multi/revision-howto-multi-2003-09-15.xml?view=diff&rev=527010&r1=527009&r2=527010
==============================================================================
--- forrest/trunk/site-author/content/xdocs/docs_0_70/howto/multi/revision-howto-multi-2003-09-15.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_70/howto/multi/revision-howto-multi-2003-09-15.xml Mon Apr  9 20:48:52 2007
@@ -16,18 +16,17 @@
   limitations under the License.
 -->
 <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN" "http://forrest.apache.org/dtd/document-v12.dtd">
-
 <document>
   <header>
     <title>Another Sample Revision</title>
   </header>
-
   <body>
-<p>
-I see that the revision2document.xsl adds a footer to suggest that the
-author should be contacted to make revisions. This is not the opensource way.
-This would create a bottleneck at the author. Community feedback should be
-encouraged to go to the relevant listserver, and patches submitted via Bugzilla.
-</p>
+    <p>
+      I see that the revision2document.xsl adds a footer to suggest that the
+      author should be contacted to make revisions. This is not the opensource
+      way. This would create a bottleneck at the author. Community feedback
+      should be encouraged to go to the relevant listserver, and patches
+      submitted via Bugzilla.
+    </p>
   </body>
 </document>

Modified: forrest/trunk/site-author/content/xdocs/docs_0_70/howto/multi/revision-step1-2003-09-16.xml
URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/docs_0_70/howto/multi/revision-step1-2003-09-16.xml?view=diff&rev=527010&r1=527009&r2=527010
==============================================================================
--- forrest/trunk/site-author/content/xdocs/docs_0_70/howto/multi/revision-step1-2003-09-16.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_70/howto/multi/revision-step1-2003-09-16.xml Mon Apr  9 20:48:52 2007
@@ -16,21 +16,20 @@
   limitations under the License.
 -->
 <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN" "http://forrest.apache.org/dtd/document-v12.dtd">
-
 <document>
   <header>
     <title>Sample Revision notes for Step 1</title>
   </header>
-
   <body>
     <section>
       <title>Other comments</title>
-      <p>There is a problem with this approach</p>
+      <p>
+        There is a problem with this approach
+      </p>
       <ul>
         <li>Problem d.</li>
         <li>Problem e.</li>
       </ul>
     </section>
   </body>
-
 </document>

Modified: forrest/trunk/site-author/content/xdocs/docs_0_70/howto/multi/step1.xml
URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/docs_0_70/howto/multi/step1.xml?view=diff&rev=527010&r1=527009&r2=527010
==============================================================================
--- forrest/trunk/site-author/content/xdocs/docs_0_70/howto/multi/step1.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_70/howto/multi/step1.xml Mon Apr  9 20:48:52 2007
@@ -16,29 +16,36 @@
   limitations under the License.
 -->
 <!DOCTYPE howto PUBLIC "-//APACHE//DTD How-to V1.2//EN" "http://forrest.apache.org/dtd/howto-v12.dtd">
-
 <howto>
   <header>
     <title>Multi-page how-to: Step 1</title>
     <last-modified-content-date date="2003-09-10"/>
   </header>
-
-  <steps title="Step 1: Do foo"> 
+  <steps title="Step 1: Do foo">
     <section>
       <title>First section of this step</title>
-      <p>Description here.</p>
+      <p>
+        Description here.
+      </p>
     </section>
     <section>
       <title>Second section of this step</title>
-      <p>Description here.</p>
-      <p>Source code follows ...</p>
-      <source><![CDATA[
+      <p>
+        Description here.
+      </p>
+      <p>
+        Source code follows ...
+      </p>
+      <source>
+<![CDATA[
 <pointy-brackets>
   <are-allowed-in-source-CDATA-sections/>
 </pointy-brackets>
 ]]>
       </source>
-      <p>Now we move on to <link href="step2.html">Step 2: Do foobar</link></p>
+      <p>
+        Now we move on to <link href="step2.html">Step 2: Do foobar</link>
+      </p>
     </section>
   </steps>
 </howto>

Modified: forrest/trunk/site-author/content/xdocs/docs_0_70/howto/multi/step2.xml
URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/docs_0_70/howto/multi/step2.xml?view=diff&rev=527010&r1=527009&r2=527010
==============================================================================
--- forrest/trunk/site-author/content/xdocs/docs_0_70/howto/multi/step2.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_70/howto/multi/step2.xml Mon Apr  9 20:48:52 2007
@@ -16,22 +16,26 @@
   limitations under the License.
 -->
 <!DOCTYPE howto PUBLIC "-//APACHE//DTD How-to V1.0//EN" "http://forrest.apache.org/dtd/howto-v10.dtd">
-
 <howto>
   <header>
     <title>Multi-page how-to: Step 2</title>
     <last-modified-content-date date="2003-09-10"/>
   </header>
-
-  <steps title="Step 2: Do foobar"> 
+  <steps title="Step 2: Do foobar">
     <section>
       <title>First section of this step</title>
-      <p>Description here.</p>
+      <p>
+        Description here.
+      </p>
     </section>
     <section>
       <title>Second section of this step</title>
-      <p>Description here.</p>
-      <p>Now we move on to <link href="step3.html">Step 3: Finish up</link></p>
+      <p>
+        Description here.
+      </p>
+      <p>
+        Now we move on to <link href="step3.html">Step 3: Finish up</link>
+      </p>
     </section>
   </steps>
 </howto>

Modified: forrest/trunk/site-author/content/xdocs/docs_0_70/howto/multi/step3.xml
URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/docs_0_70/howto/multi/step3.xml?view=diff&rev=527010&r1=527009&r2=527010
==============================================================================
--- forrest/trunk/site-author/content/xdocs/docs_0_70/howto/multi/step3.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_70/howto/multi/step3.xml Mon Apr  9 20:48:52 2007
@@ -16,23 +16,27 @@
   limitations under the License.
 -->
 <!DOCTYPE howto PUBLIC "-//APACHE//DTD How-to V1.2//EN" "http://forrest.apache.org/dtd/howto-v12.dtd">
-
 <howto>
   <header>
     <title>Multi-page how-to: Step 3</title>
     <last-modified-content-date date="2002-09-10"/>
   </header>
-
-  <steps title="Step 3: Finish up"> 
+  <steps title="Step 3: Finish up">
     <section>
       <title>First section of this step</title>
-      <p>Description here.</p>
+      <p>
+        Description here.
+      </p>
     </section>
     <section>
       <title>Second section of this step</title>
-      <p>Description here.</p>
-      <p>Congratulations, you have finished. Now return to the
-      <link href="howto-multi.html">start</link>.</p>
+      <p>
+        Description here.
+      </p>
+      <p>
+        Congratulations, you have finished. Now return to the
+        <link href="howto-multi.html">start</link>.
+      </p>
     </section>
   </steps>
 </howto>

Modified: forrest/trunk/site-author/content/xdocs/docs_0_70/howto/project_sitemap.xmap.html
URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/docs_0_70/howto/project_sitemap.xmap.html?view=diff&rev=527010&r1=527009&r2=527010
==============================================================================
--- forrest/trunk/site-author/content/xdocs/docs_0_70/howto/project_sitemap.xmap.html (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_70/howto/project_sitemap.xmap.html Mon Apr  9 20:48:52 2007
@@ -15,19 +15,21 @@
   limitations under the License.
 -->
 <html>
-<head>
-<title>sitemap.xmap in the Project Documentation Directory</title>
-</head>
-<body>
-<h1>sitemap.xmap in the Project Documentation Directory</h1>
-<pre><![CDATA[
+  <head>
+    <title>sitemap.xmap in the Project Documentation Directory</title>
+  </head>
+  <body>
+    <h1>sitemap.xmap in the Project Documentation Directory</h1>
+    <pre>
+<![CDATA[
 <?xml version="1.0"?>
 <map:sitemap xmlns:map="http://apache.org/cocoon/sitemap/1.0">
  <map:pipelines>
-]]></pre>
-
-<h2>Example pipeline for '**custom.xml'</h2>
-<pre><![CDATA[
+]]>
+    </pre>
+    <h2>Example pipeline for '**custom.xml'</h2>
+    <pre>
+<![CDATA[
   <map:pipeline>
    <map:match pattern="**custom.xml">
     <map:generate src="{project:content.xdocs}{1}custom.xml" />
@@ -37,6 +39,7 @@
   </map:pipeline>
  </map:pipelines>
 </map:sitemap>
-]]></pre>
-</body>
+]]>
+    </pre>
+  </body>
 </html>

Modified: forrest/trunk/site-author/content/xdocs/docs_0_70/howto/sitemap.xmap.html
URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/docs_0_70/howto/sitemap.xmap.html?view=diff&rev=527010&r1=527009&r2=527010
==============================================================================
--- forrest/trunk/site-author/content/xdocs/docs_0_70/howto/sitemap.xmap.html (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_70/howto/sitemap.xmap.html Mon Apr  9 20:48:52 2007
@@ -15,12 +15,13 @@
   limitations under the License.
 -->
 <html>
-<head>
-<title>Annotated core sitemap.xmap</title>
-</head>
-<body>
-<h1>sitemap.xmap</h1>
-<pre><![CDATA[
+  <head>
+    <title>Annotated core sitemap.xmap</title>
+  </head>
+  <body>
+    <h1>sitemap.xmap</h1>
+    <pre>
+<![CDATA[
 <?xml version="1.0"?>
 <!-- ===============================================
 Default Forrest sitemap, defining the whole site.
@@ -29,10 +30,11 @@
 
 $Revision: 1.12 $
 ==================================================== -->
-]]></pre>
-
-<h2>Start of Sitemap</h2>
-<pre><![CDATA[
+]]>
+    </pre>
+    <h2>Start of Sitemap</h2>
+    <pre>
+<![CDATA[
 <map:sitemap xmlns:map="http://apache.org/cocoon/sitemap/1.0">
   <map:components>
     <map:generators default="file">
@@ -241,18 +243,20 @@
     </map:resource>
 
   </map:resources>
-]]></pre>
-
-  <h2>Start of Pipelines</h2>
-<pre><![CDATA[
+]]>
+    </pre>
+    <h2>Start of Pipelines</h2>
+    <pre>
+<![CDATA[
   <!-- =========================== Pipelines ================================= -->
   <map:pipelines>
 
   <map:pipeline type="caching" internal-only="true">
-]]></pre>
-
-<h2>Test for First Pipeline</h2>
-<pre><![CDATA[
+]]>
+    </pre>
+    <h2>Test for First Pipeline</h2>
+    <pre>
+<![CDATA[
       <map:match pattern="*.xlex">
         <map:select type="exists">
           <map:when test="resources/chaperon/grammars/{1}.xlex">
@@ -271,10 +275,11 @@
         </map:select>
       </map:match>
     </map:pipeline>
-]]></pre>
-    
-<h2>Insertion Point for Project Sitemap</h2>    
-<pre><![CDATA[
+]]>
+    </pre>
+    <h2>Insertion Point for Project Sitemap</h2>
+    <pre>
+<![CDATA[
       <!--
          This is the user pipeline, that can answer requests instead
          of the Forrest one, or let requests pass through.
@@ -335,10 +340,11 @@
       <!--                 Raw XML sources, typically doc-v12 format    -->
       <!-- ============================================================ -->
       <!-- http://forrest.apache.org/docs/sitemap-ref.html#source_pipelines -->
-]]></pre>
-     
-<h2>First Match for '**.xml'</h2>     
-<pre><![CDATA[
+]]>
+    </pre>
+    <h2>First Match for '**.xml'</h2>
+    <pre>
+<![CDATA[
       <!-- Body content -->
       <map:match pattern="**.xml">
      
@@ -434,10 +440,11 @@
       <map:match pattern="**body-faq.html">
         <map:mount uri-prefix="" src="faq.xmap" check-reload="yes" />
       </map:match>
-]]></pre>
-
-<h2>First Match for '**body-*.html'</h2>
-<pre><![CDATA[
+]]>
+    </pre>
+    <h2>First Match for '**body-*.html'</h2>
+    <pre>
+<![CDATA[
       <map:match pattern="**body-*.html">
         <map:select type="exists">
           <map:when test="{project:content.xdocs}{1}{2}.ehtml">
@@ -449,18 +456,20 @@
           </map:when>
         </map:select>
       </map:match>
-]]></pre>
-
-<h2>Second Match for '**body-*.html'</h2>
-<pre><![CDATA[
+]]>
+    </pre>
+    <h2>Second Match for '**body-*.html'</h2>
+    <pre>
+<![CDATA[
       <!-- Default matches -->
       <!-- (HTML rendered from doc-v11 intermediate format -->
       <map:match pattern="**body-*.html">
         <map:generate src="cocoon:/{1}{2}.xml"/>
-]]></pre>
-
-<h2>Returning to the '**body-*.html' Pipeline</h2>
-<pre><![CDATA[
+]]>
+    </pre>
+    <h2>Returning to the '**body-*.html' Pipeline</h2>
+    <pre>
+<![CDATA[
         <map:transform type="idgen"/>
         <map:transform type="xinclude"/>
         <map:transform type="linkrewriter" src="cocoon:/{1}linkmap-{2}.html"/>
@@ -525,10 +534,11 @@
           <map:parameter name="path" value="{0}"/>
         </map:call>
       </map:match>
-]]></pre>
-
-<h2>First Match for "**/*.html"</h2>
-<pre><![CDATA[
+]]>
+    </pre>
+    <h2>First Match for "**/*.html"</h2>
+    <pre>
+<![CDATA[
   <map:match pattern="**/*.html">
     <map:aggregate element="site">
       <map:part src="cocoon:/skinconf.xml"/>
@@ -679,6 +689,7 @@
 
   </map:pipelines>
 </map:sitemap>
-]]></pre>
-</body>
+]]>
+    </pre>
+  </body>
 </html>

Modified: forrest/trunk/site-author/content/xdocs/docs_0_70/index.xml
URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/docs_0_70/index.xml?view=diff&rev=527010&r1=527009&r2=527010
==============================================================================
--- forrest/trunk/site-author/content/xdocs/docs_0_70/index.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_70/index.xml Mon Apr  9 20:48:52 2007
@@ -16,31 +16,30 @@
   limitations under the License.
 -->
 <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd">
-<document> 
-  <header> 
-    <title>Apache Forrest documentation</title> 
-  </header> 
+<document>
+  <header>
+    <title>Apache Forrest documentation</title>
+  </header>
   <body>
     <section id="project">
       <title>Project-level documentation</title>
       <p>
-        See the <a href="../">Apache Forrest Project</a> website for
-        the main project-level documents.
+        See the <a href="../">Apache Forrest Project</a> website for the main
+        project-level documents.
       </p>
     </section>
     <section id="docs">
       <title>Product documentation</title>
       <p>
-        For the local docs for the version of Forrest that you are using,
-        see the menu at the left and the tabs above for
+        For the local docs for the version of Forrest that you are using, see
+        the menu at the left and the tabs above for
         <a href="site:v0.70//documentation/index">Docs</a> and
         <a href="site:v0.70//howto/overview">How-To</a> and
         <a href="site:plugins/index">Plugins</a>.
       </p>
       <p>
-        See links to 
-        <a href="site:versions/overview">other versions</a>
-        of documentation.
+        See links to <a href="site:versions/overview">other versions</a> of
+        documentation.
       </p>
     </section>
   </body>



Mime
View raw message