forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: rev 51794 - forrest/trunk/src/documentation/content/xdocs/docs
Date Sat, 02 Oct 2004 07:10:00 GMT
Author: crossley
Date: Sat Oct  2 00:10:00 2004
New Revision: 51794

Added new section "Configuration of skins" to point to skinconf.xml comments.
Added intro para to "Defining a new skin" to encourage use of core skins.

Modified: forrest/trunk/src/documentation/content/xdocs/docs/your-project.xml
--- forrest/trunk/src/documentation/content/xdocs/docs/your-project.xml	(original)
+++ forrest/trunk/src/documentation/content/xdocs/docs/your-project.xml	Sat Oct  2 00:10:00
@@ -916,26 +916,34 @@
           "skins" to instantly change a site's look and feel.  Forrest provides one
           primary skin, <code>pelt</code>, and some others in various
           states of development.
+          To change the skin, edit the <code></code> file
+          to set <code></code> or some other skin name.
-        <p>
-          To change the skin, edit the <code></code> file,
-          change the following entry to the name of the new skin.
-        </p>
-        <source></source>
-        <!--
-        <note>
-          The mechanism for defining which skin to use will change in the future from
-          Ant @token@ values to Cocoon input module values.
-        </note>
-        -->
           Forrest supplies a collection of 
           <link href="site:skins">default skins</link> which are configurable
           and so should meet the needs of most projects. The aim is to provide
           many capabilities so that extra skins are not needed.
+        <section id="skin-configuration">
+          <title>Configuration of skins</title>
+          <p>
+          All configuration is done via your project
+          <code>src/documentation/skinconf.xml</code> file.
+          It contains many comments to describe each capability.
+          Please read those, there is no point repeating here.
+          </p>
+        </section>
         <section id="new_skin">
           <title>Defining a new skin</title>
+          <p>Consider discussing your needs on the mailing lists. There may
+          be planned enhancements to the core skins. Also consider contributing
+          your extensions to the core skins, rather than write your own skin.
+          Bear in mind that you could be creating an update and management
+          issue. Anyway, ...
+          </p>
             Projects can define their own skin in the
             <code>src/documentation/skins</code> directory (or wherever

View raw message