Re: Some feedback on using Forrest

[David Crossley]

Pedro I. Sanchez wrote:
> David Crossley wrote:
> > Pedro I. Sanchez wrote:
> > >
> > > 3. Why do I get "2005 2005" in the copyright label? I have this
> > > in skinconf.xml
> > > 
> > >   2005
> > >   Sello Propio.
> > > 
> > > I'd like this to read "2004-2005" but if I put 2004-2005 I
> > > get "2004-2005 2004-2005". The skin always doubles up the content of the
> > >  :(
> > 
> > Strange. That configuration does not seem to be any different
> > to what we have for forrest.apache.org and it works for us.
> > 
> > You said that you copied the pelt skin and changed some things.
> > Perhaps you accidently added something to the stylesheets
> > when you were experimenting with changing the English terms.
> > Doing 'diff -r skins/sello-propio skins/pelt' will reveal your
> > changes.
> 
> I just did a svn update on my local copy of Forrest. Then I run "forrest
> seed; forrest" in a clean, empty, directory. I get the "2005 2005"
> thing. You can see the result at http://colcan.biz/forrest

However, that does not prove anything - that will just merge any
changes that we might have recently made. You said that you created
a new skin. I reckon that that is where the problem might be.
Would you please do the diff command described above.

> > > 4. You will notice that the date in the top right of the pages is
> > > the current date/time as of the moment you click to see each page.
> > > This is supposed to be the "Published" date instead! (I removed
> > > the "Publicado", in Spanish, because it is simply not working).
> > > 
> > > The server serving the pages doesn't have Java available. Could this
> > > be the reason why I get this weird behaviour?
> > 
> > Perhaps there is a problem with your web server. When i request
> > HEAD of that document, it shows that there is no "Last-Modified"
> > header in the response.
> 
> I have no control over the server. What exactly is required for this
> feature to work?

I notice that you are using the Apache HTTP Server, so send
your web guy to http://httpd.apache.org/docs/

--David

Re: TOC in FAQ

[David Crossley]

The Web Maestro wrote:
> David Crossley wrote:
> >David Crossley wrote:
> >
> >At one stage you were using a project-specific sitemap
> >for your FOP website, IIRC. If you are still, i wonder
> >if that has an extraneous match that is interfering with
> >the faq pipeline.
> 
> I don't believe we're using any special project-specific items except  
> for the compliance2*.xsl files in ViewCVS here:
> 
>  stylesheets/>
> 
> As for the fop-specific sitemap.xmap file, I believe it's been replaced  
> with the standard version from the Forrest distribution. IIRC, that's  
> one of the 'tricks' we took to making xml-fop work again.

Are you sure that you don't use a sitemap.xmap file? I remember long
discussions with you late last year on our dev list:
"Subject: "xml-fop Build Failed". It involved using special sitemap
matches to handle your special compliance2html document. IIRC you
had it in your local working copy, but it wasn't in the FOP CVS.
It would probably be at src/documentation/sitemap.xmap

If you don't have a project sitemap then great, we can rule that out
as a possible source of your FAQ ToC problem, and close FOR-507.

> FWIW, I just created a new Task/Issue in CocoonDev issues ([#FOR-507]  
> xml-fop *.xmap files). I've attached my $FORREST_HOME/context/*.xmap  
> files to the issue.

No that doesn't help. There is no difference between those and
the default forrest 0.6 core sitemaps. It was good to know that they
haven't been changed, but i wasn't actually talking about the
core sitemaps anyway, i was referring to a project-specific sitemap
(discussed above).

--David

> I had a colleague try, and the TOC doesn't generate for him either...
> 
> Regards,
> 
> Web Maestro Clay
> -- 
> <[EMAIL PROTECTED]> - 
> My religion is simple. My religion is kindness.
> - HH The 14th Dalai Lama of Tibet

Re: How to Try Currently Useable Skins?

[Tim Williams]

> The sections in skinconf do not relate to a specific skin. They are used
> to create the CSS. The included sections are provided as examples.
> 
> If you want to experiment with the colours for tigris (for example)
> simple look at the class names you want to affect and add an appropriate
> entry to skinconf.

Is the following technically accurate as a proposed comment update for
skinconf.xml?  I also moved the "Forrest" section of colors to the top
of the block because having a "named" skin at the top was initially
misleading to me.  Anyway, just a thought.
--tim
...

  

Re: How to Try Currently Useable Skins?

[Ross Gardler]

Maurice Lanselle wrote:
I am learning to use Forrest v0.6.  I am very confused by the 
information on changing skins and skin properties, and I think there may 
be issues.


Yes, this is true, we welcome patches for improvements once you 
understand things. Right now I'll try and help you get through the 
inadequate docs.



I would like to simply:
1) Try the available skins, to see how they look and how they vary so I 
can choose my favorite.


edit the forrest.properties file to set project.skin to the name of the 
skin you want to use.


or

forrest site -Dproject.skin=SKINNAME
(as is correctly suggested later in this thread by Tim Williams)


2) Customize the colors of the chosen skin.
This is not as simple or successful as I expected.  There seems to be 
inconsistent information on what skins are currently useable, and also 
the inclusion of their color tags in skinconf.xml.
a) The "available-skins" command gives out-of-date information : "crust, 
pelt, tigris"


We only actively support pelt. All other skins are either in development 
or deprecated, although some are still usable (you can find out what 
they are by looking in the skins directory of the distribution).


You comment above indicates that the list provided by availabl-skins is 
out of date, please raise an issue for us so we can remember to fix it 
for the upcoming 0.7 release.


b) When I asked for "crust" (no longer exists), the handler chooses a 
deprecated skin : "krysalis-site" , which in turn provokes a warning and 
a recommendation to use "pelt".


It should default to pelt, please add an issue about this too.

c) skinconf.xml has color tags for "krysalis", "Forrest", "Collabnet", 
"Lenya using pelt", but these are all either deprecated or not mentioned 
in the available and defaults lists. So how would I change the colors 
for, say, tigris (which does work for me)? How could I (easily) obtain 
the color tags to use the correct names and know the initial settings?


The sections in skinconf do not relate to a specific skin. They are used 
to create the CSS. The included sections are provided as examples.


If you want to experiment with the colours for tigris (for example) 
simple look at the class names you want to affect and add an appropriate 
entry to skinconf.


Also confusing for me, at [http://forrest.apache.org/0.7/docs.html] in 
the body it lists

0.6 - the current release
0.7 - the current development version

but in the menu under "Other>Overview" it lists
- 0.8-dev
- 0.7 (current)
- 0.6


Oooopa, this is a result of us being in the middle of preparing for the 
0.7 release (which is currently development).


Thanks for taking the time to highlight confusions with our docs. One of 
the hardest things for us to do is write docs that are useful to the 
newcomer. We have all been using Forrest for quite some time and don't 
often have to think about these issues. Your feedback is important.


It would be really useful, both to the devs and to subsequent newbies if 
you could provide a patch or suggested improvement to the docs as an 
issue once you fully grasp what we try to explain here. We'll happilly 
apply your improvements.


Ross

Re: How to Try Currently Useable Skins?

[Tim Williams]

Will the following not do what you want?
$> forrest site -Dproject.skin=krysalis-site

You'd have to rename the directory after each build if you wanted to
compare side by side.  I couldn't find a property to change the
build-directory on the command line but I don't doubt that it exists
too.

As for your number 2, skinconf.xml will allow you to customize most things.

--tim


On 5/26/05, The Web Maestro <[EMAIL PROTECTED]> wrote:
> 
> On May 26, 2005, at 3:57 AM, Maurice Lanselle wrote:
> 
> > I am learning to use Forrest v0.6.  I am very confused by the
> > information on changing skins and skin properties, and I think there
> > may be issues. I would like to simply:
> > 1) Try the available skins, to see how they look and how they vary so
> > I can choose my favorite.
> > 2) Customize the colors of the chosen skin.
> 
> I would second this. It would be nice to have the ability to generate
> output for each type of skin, so they can be compared. This could be
> done using the seed, or alternately using someone's forrest generated
> site. They could output like this:
> 
> build/site_crust/
> build/site_pelt/
> build/site_leather/
> 
> etc.
> 
> Regards,
> 
> Web Maestro Clay
> --
> <[EMAIL PROTECTED]> - 
> My religion is simple. My religion is kindness.
> - HH The 14th Dalai Lama of Tibet
> 
>

Re: i18n: menu or doc, but not both! (and no language override menu)

[Børre Gaup]

Gaskavahkku, miessemánu 25. b. 2005 19.26, Sjur Moshagen čálii:
> Hello,
>
> I've been silent for a long time - sorry for not giving any feedback
> sooner!
>
> We have now tested the i18n features with the latest svn version (of
> today), and the behaviour we find is a little strange. Here's what
> we've done, and the result:
>
> - made a new dir
> - fresh forrest seed
> - turned forrest.i18n on
> - added index.sme.xml and index.no.xml to .../xdocs/
> - added menu_sme.xml (menu_no.xml is part of the distro)
>
> The outcome:
>
> $ forrest run
>
> In the browser:
>
> localhost:/index.html
> -> Norwegian menu, default (English) page (Norwegian locale from the
> browser)
>
> localhost:/index.html?locale=sme
> -> English menu, North Sámi (sme) page
>
> localhost:/index.html?locale=no
> -> English menu, Norwegian page
>
> That is, it is not possible to override the menu locale, only the
> document locale. When the menu locale is not taken from the browser
> (because of a URL override), it falls back to the default.
>
> That is, it is almost impossible to get the document and menu locales
> to match:-(
>
> On the *very* positive side, Forrest does not any more (=since last
> time we tested) return a 404 when it can't find a specified locale.
>
> Also, when i18n is turned on, we would expect a language override
> menu to be generated, but see none. What is needed to get one?
>
> Thanks for the great work on Forrest, we're looking forward to the
> 0.7 release:-)
>

Hello, I am Sjurs co-worker, and we continued our research on forrest i18n.

I tested the i18n features of forrest-0.7-dev, svn revision 106393, using the 
same method as described above, except that the index.xml file was renamed 
index_sme.xml. 

Using the same URL's as above I get the correct languages in both menus and 
documents, and an internal server error when specifying a non-existing 
locale.

So, the expected behavior would be if forrest behaves like the old svn version 
with regards to specifying a locale, and degrades gracefully if the requested 
locale does not exist, as in the new svn version.

Is it easy to fix, or should we open an issue in the bug tracker?

Børre Gaup
Samediggi

Re: How to Try Currently Useable Skins?

[The Web Maestro]

On May 26, 2005, at 3:57 AM, Maurice Lanselle wrote:

I am learning to use Forrest v0.6.  I am very confused by the 
information on changing skins and skin properties, and I think there 
may be issues. I would like to simply:
1) Try the available skins, to see how they look and how they vary so 
I can choose my favorite.

2) Customize the colors of the chosen skin.


I would second this. It would be nice to have the ability to generate 
output for each type of skin, so they can be compared. This could be 
done using the seed, or alternately using someone's forrest generated 
site. They could output like this:


build/site_crust/
build/site_pelt/
build/site_leather/

etc.

Regards,

Web Maestro Clay
--
<[EMAIL PROTECTED]> - 
My religion is simple. My religion is kindness.
- HH The 14th Dalai Lama of Tibet

Re: TOC in FAQ

[The Web Maestro]

On May 25, 2005, at 5:04 PM, David Crossley wrote:

David Crossley wrote:

I will try to add your FAQ to another site and see what
your problems are. However, i am not sure if i have the
correct file. Is this it? ...


Forget that - you already told us the URL in your
original message, sorry. Also you proved that your
faq.xml is okay by adding it to a fresh 'forrest seed'.


Thanks for the follow-up!


At one stage you were using a project-specific sitemap
for your FOP website, IIRC. If you are still, i wonder
if that has an extraneous match that is interfering with
the faq pipeline.


I don't believe we're using any special project-specific items except  
for the compliance2*.xsl files in ViewCVS here:





As for the fop-specific sitemap.xmap file, I believe it's been replaced  
with the standard version from the Forrest distribution. IIRC, that's  
one of the 'tricks' we took to making xml-fop work again.


FWIW, I just created a new Task/Issue in CocoonDev issues ([#FOR-507]  
xml-fop *.xmap files). I've attached my $FORREST_HOME/context/*.xmap  
files to the issue.


I had a colleague try, and the TOC doesn't generate for him either...

Regards,

Web Maestro Clay
--
<[EMAIL PROTECTED]> - 
My religion is simple. My religion is kindness.
- HH The 14th Dalai Lama of Tibet

Re: Some feedback on using Forrest

[Ross Gardler]

Pedro I. Sanchez wrote:

On Thu, 2005-26-05 at 12:16 +0100, Ross Gardler wrote:


David Crossley wrote:


Pedro I. Sanchez wrote:


...


4. You will notice that the date in the top right of the pages is
the current date/time as of the moment you click to see each page.
This is supposed to be the "Published" date instead! (I removed
the "Publicado", in Spanish, because it is simply not working).

The server serving the pages doesn't have Java available. Could this
be the reason why I get this weird behaviour?



Perhaps there is a problem with your web server. When i request
HEAD of that document, it shows that there is no "Last-Modified"
header in the response.


To be clear, the last published time is taken from the LAST-MODIFIED 
header, if it is not present the current date/time is used. Note that it 
*should* be present, this is a config problem on your server.





As I said before, I have no control over the web server. But I'd like to
know what exactly is needed there to get this feature working. Maybe I
can convince someone to do it :|


How to get it working is dependant on your server. I you want to do it 
in the generation of the pages search your skin files for 
document.write("Last Published: " + document.lastModified);


You could change the way this is generated, perhaps taking a value from 
skinconf. Not ideal as you will have to update skinconf each time you 
published, but at leat it would work if you can't get the last-modified 
header.



I glad to see this is helpful. I will continue working with 0.7-dev and
would let you know how it goes. BTW, understanding the menu generation
thing was not trivial. There's a few things the docs fail to mention.
I'll try to put them in some good wording later this week.


That would be superb, if you can then put a patch on our issue tracker, 
see http://forrest.apache.org/0.7/contrib.html#patch. If you can't 
provide a patch comments on the issue will help.


Ross

Re: Some feedback on using Forrest

[Pedro I. Sanchez]

On Thu, 2005-26-05 at 12:16 +0100, Ross Gardler wrote:
> David Crossley wrote:
> > Pedro I. Sanchez wrote:
> 
> ...
> 
> >>I've worked with the svn version of Forrest and I'd like to share some
> >>comments on my experience so far.
> > 
> > 
> > Oh thank you. That is exactly what we need - feedback.
> > Also people testing 0.7-dev is helping to create a better release.
> 
> I also want to thank you, this is a very valuable contribution to the 
> development of Forrest.
> 
> >>2. My site.xml file has the following:
> >>
> >>
> >>...
> >>
> >>
> >>
> >>However,  is rendered as the link
> >>http://sello-propio.com/eventos/ which you can see in the front
> >>page. Where did the "index.html" part go? This is annoying 
> >>because while testing the site in my local hard drive (with
> >>URLs like file:///path/to/build/site) these links give me
> >>the list of files in the directory instead of the "index.html"
> >>file I am expecting.
> >>
> >>Basically, there seems to be the implicit assumption that the
> >>web server will always figure out that index.html is the file
> >>that has to be rendered. This is not always the case. In particular
> >>several "embedded" web server don't have this logic built in
> >>and require a explicit mention of the target file.
> > 
> > 
> > I wonder if this FAQ would address that issue:
> > http://forrest.apache.org/0.7/docs/faq.html#defaultStartPage
> 
> This is a different issue, That FAQ is about changing the default page 
> used if none is defined in the URL.  In this case the page to be used 
> has been defined in the HREF and therefore should be included in the link.
> 
> However, I have never seen this before, and a fresh-seed site shows that 
> this functionality works correctly. Do:
> 
> mkdir fresh
> cd fresh
> forrest seed
> forrest run
> http://localhost:/samples/linking.html#site
> 
> Note the links in this section, they correctly link to the named page, 
> for example:
> 
> site:faq
> 
> generates the link:
> 
> http://localhost:/samples/faq.html
> 
> 
> Do you have another element in your site.xml called "eventos", that 
> could be getting in the way?
> 

Thanks! you got it. There is a tab called "eventos" as well. Removing
this duplication fixes the problemm.

> If you change the site.xml entry to  href="eventos/testing.html"/> what is the resultant link?
> 
> 
> >>4. You will notice that the date in the top right of the pages is
> >>the current date/time as of the moment you click to see each page.
> >>This is supposed to be the "Published" date instead! (I removed
> >>the "Publicado", in Spanish, because it is simply not working).
> >>
> >>The server serving the pages doesn't have Java available. Could this
> >>be the reason why I get this weird behaviour?
> > 
> > 
> > Perhaps there is a problem with your web server. When i request
> > HEAD of that document, it shows that there is no "Last-Modified"
> > header in the response.
> 
> To be clear, the last published time is taken from the LAST-MODIFIED 
> header, if it is not present the current date/time is used. Note that it 
> *should* be present, this is a config problem on your server.
> 

As I said before, I have no control over the web server. But I'd like to
know what exactly is needed there to get this feature working. Maybe I
can convince someone to do it :|

> Once again, thanks for your feedback. Being made aware of these issues 
> is how we try and make sure Forrest works for everyone as intended. 
> Without this feedback the devs cannot do their job properly. For all 
> those lurkers here, you can contribute to Forrest directly simply by 
> providing feedback like this.
> 

I glad to see this is helpful. I will continue working with 0.7-dev and
would let you know how it goes. BTW, understanding the menu generation
thing was not trivial. There's a few things the docs fail to mention.
I'll try to put them in some good wording later this week.

-- 
Pedro

> Ross

Re: Some feedback on using Forrest

[Pedro I. Sanchez]

On Thu, 2005-26-05 at 15:55 +1000, David Crossley wrote:
> Pedro I. Sanchez wrote:
> > Hello,
> > 
> > I created a web site which is on-line at http://www.sello-propio.com
> > since a few days ago. It is pretty simple and uses the default skin.
> > But my customer is really happy, both with the quality, and with the
> > speed at which changes can be introduced.
> > 
> > I've worked with the svn version of Forrest and I'd like to share some
> > comments on my experience so far.
> 
> Oh thank you. That is exactly what we need - feedback.
> Also people testing 0.7-dev is helping to create a better release.
> 
> > 1. The web site is in Spanish. I had to manually modify the default
> > skin to get rid of English messages, i.e., "Published", "Search", etc.
> > It would be great if the skins would refer to some file which actually
> > holds the translations for these messages.
> 
> This could be quite easily added to the skinconf.xml configuration,
> rather than a separate file. The skinconf DTD would need a tweak.
> Would you please add an Issue to our tracker. See the left-hand
> menu of our Project tab.
> 

I'll do.

> > 2. My site.xml file has the following:
> > 
> > 
> > ...
> > 
> > 
> > 
> > However,  is rendered as the link
> > http://sello-propio.com/eventos/ which you can see in the front
> > page. Where did the "index.html" part go? This is annoying 
> > because while testing the site in my local hard drive (with
> > URLs like file:///path/to/build/site) these links give me
> > the list of files in the directory instead of the "index.html"
> > file I am expecting.
> > 
> > Basically, there seems to be the implicit assumption that the
> > web server will always figure out that index.html is the file
> > that has to be rendered. This is not always the case. In particular
> > several "embedded" web server don't have this logic built in
> > and require a explicit mention of the target file.
> 
> I wonder if this FAQ would address that issue:
> http://forrest.apache.org/0.7/docs/faq.html#defaultStartPage
> 

Can't connect. It doesn't seem to be the same issue.

> > 3. Why do I get "2005 2005" in the copyright label? I have this
> > in skinconf.xml
> > 
> >   2005
> >   Sello Propio.
> > 
> > I'd like this to read "2004-2005" but if I put 2004-2005 I
> > get "2004-2005 2004-2005". The skin always doubles up the content of the
> >  :(
> 
> Strange. That configuration does not seem to be any different
> to what we have for forrest.apache.org and it works for us.
> 
> You said that you copied the pelt skin and changed some things.
> Perhaps you accidently added something to the stylesheets
> when you were experimenting with changing the English terms.
> Doing 'diff -r skins/sello-propio skins/pelt' will reveal your
> changes.
> 

I just did a svn update on my local copy of Forrest. Then I run "forrest
seed; forrest" in a clean, empty, directory. I get the "2005 2005"
thing. You can see the result at http://colcan.biz/forrest


> > 4. You will notice that the date in the top right of the pages is
> > the current date/time as of the moment you click to see each page.
> > This is supposed to be the "Published" date instead! (I removed
> > the "Publicado", in Spanish, because it is simply not working).
> > 
> > The server serving the pages doesn't have Java available. Could this
> > be the reason why I get this weird behaviour?
> 
> Perhaps there is a problem with your web server. When i request
> HEAD of that document, it shows that there is no "Last-Modified"
> header in the response.
> 

I have no control over the server. What exactly is required for this
feature to work?

> > Despite these problems, I'm really happy with Forrest and I want to
> > say thank you to the development team.
> 
> Thanks to you. If you have any general changes that you needed
> to make to the pelt skin, then send them in. That would make
> it easier for you to keep your code synchronised.
> 
> > And if you feel is worth it,
> > I'd be delighted to see this new web site in the list of samples
> > in the Forrest's web site.
> 
> Of course it is. Done. If you want to change the entry, then
> send us the output of
> svn diff site-author/content/xdocs/live-sites.xml
> 

Thank you,

Pedro

> --David

Re: Some feedback on using Forrest

[Ross Gardler]

David Crossley wrote:

Pedro I. Sanchez wrote:


...


I've worked with the svn version of Forrest and I'd like to share some
comments on my experience so far.



Oh thank you. That is exactly what we need - feedback.
Also people testing 0.7-dev is helping to create a better release.


I also want to thank you, this is a very valuable contribution to the 
development of Forrest.



2. My site.xml file has the following:


...



However,  is rendered as the link
http://sello-propio.com/eventos/ which you can see in the front
page. Where did the "index.html" part go? This is annoying 
because while testing the site in my local hard drive (with

URLs like file:///path/to/build/site) these links give me
the list of files in the directory instead of the "index.html"
file I am expecting.

Basically, there seems to be the implicit assumption that the
web server will always figure out that index.html is the file
that has to be rendered. This is not always the case. In particular
several "embedded" web server don't have this logic built in
and require a explicit mention of the target file.



I wonder if this FAQ would address that issue:
http://forrest.apache.org/0.7/docs/faq.html#defaultStartPage


This is a different issue, That FAQ is about changing the default page 
used if none is defined in the URL.  In this case the page to be used 
has been defined in the HREF and therefore should be included in the link.


However, I have never seen this before, and a fresh-seed site shows that 
this functionality works correctly. Do:


mkdir fresh
cd fresh
forrest seed
forrest run
http://localhost:/samples/linking.html#site

Note the links in this section, they correctly link to the named page, 
for example:


site:faq

generates the link:

http://localhost:/samples/faq.html


Do you have another element in your site.xml called "eventos", that 
could be getting in the way?


If you change the site.xml entry to href="eventos/testing.html"/> what is the resultant link?




4. You will notice that the date in the top right of the pages is
the current date/time as of the moment you click to see each page.
This is supposed to be the "Published" date instead! (I removed
the "Publicado", in Spanish, because it is simply not working).

The server serving the pages doesn't have Java available. Could this
be the reason why I get this weird behaviour?



Perhaps there is a problem with your web server. When i request
HEAD of that document, it shows that there is no "Last-Modified"
header in the response.


To be clear, the last published time is taken from the LAST-MODIFIED 
header, if it is not present the current date/time is used. Note that it 
*should* be present, this is a config problem on your server.


Once again, thanks for your feedback. Being made aware of these issues 
is how we try and make sure Forrest works for everyone as intended. 
Without this feedback the devs cannot do their job properly. For all 
those lurkers here, you can contribute to Forrest directly simply by 
providing feedback like this.


Ross

How to Try Currently Useable Skins?

[Maurice Lanselle]

I am learning to use Forrest v0.6.  I am very confused by the 
information on changing skins and skin properties, and I think there may 
be issues. I would like to simply:
1) Try the available skins, to see how they look and how they vary so I 
can choose my favorite.

2) Customize the colors of the chosen skin.

This is not as simple or successful as I expected.  There seems to be 
inconsistent information on what skins are currently useable, and also 
the inclusion of their color tags in skinconf.xml.
a) The "available-skins" command gives out-of-date information : "crust, 
pelt, tigris"
b) When I asked for "crust" (no longer exists), the handler chooses a 
deprecated skin : "krysalis-site" , which in turn provokes a warning and 
a recommendation to use "pelt".
c) skinconf.xml has color tags for "krysalis", "Forrest", "Collabnet", 
"Lenya using pelt", but these are all either deprecated or not mentioned 
in the available and defaults lists. So how would I change the colors 
for, say, tigris (which does work for me)? How could I (easily) obtain 
the color tags to use the correct names and know the initial settings?


Regards,
Maurice


Docs I consulted :

- In the doc at 
http://forrest.apache.org/docs/your-project.html#skin-configuration it 
says to "edit the forrest.properties file to set 
project.skin=leather-dev or some other skin name." and provides a link to
- a list of default skins [http://forrest.apache.org/docs/skins.html]: 
pelt, leather-dev, tigris, and plain-dev. It says "krysalis-site" and 
"forrest-site" are old and deprecated.
- On the page Skin packages 
[http://forrest.apache.org/docs/skin-package.html], it says "To see the 
names of the remote skins: forrest available-skins". 



P.S
Also confusing for me, at [http://forrest.apache.org/0.7/docs.html] in 
the body it lists

0.6 - the current release
0.7 - the current development version

but in the menu under "Other>Overview" it lists
- 0.8-dev
- 0.7 (current)
- 0.6