You are viewing a plain text version of this content. The canonical link for it is here.
Posted to svn@forrest.apache.org by cr...@apache.org on 2004/10/02 09:10:00 UTC
svn commit: rev 51794 - forrest/trunk/src/documentation/content/xdocs/docs
Author: crossley
Date: Sat Oct 2 00:10:00 2004
New Revision: 51794
Modified:
forrest/trunk/src/documentation/content/xdocs/docs/your-project.xml
Log:
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 2004
@@ -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>forrest.properties</code> file
+ to set <code>project.skin=leather-dev</code> or some other skin name.
</p>
- <p>
- To change the skin, edit the <code>forrest.properties</code> file, and
- change the following entry to the name of the new skin.
- </p>
- <source>project.skin=my-fancy-skin</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>
- -->
<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.
</note>
+
+ <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>
<p>
Projects can define their own skin in the
<code>src/documentation/skins</code> directory (or wherever