Re: [Perfparse-devel-int] Re: PP Docs

[Ben C. <BCl...@pe...>]

Ben write:
>>Flo, would you like to include any comments about wiki?

Yves wrote:
> Are you sure that a comment about the wiki should go into an "installation guide" ? :)

Probably not.

There are other parts of this documentation which need a clean fork as 
well.  The installation guide has become the one true source of 
information.  You did a too good job :)

I note parts of the same document in the wiki system.  This worries me 
because the xml version in the package is editable, and I presume the 
wiki version as well.  One only must be master...

In the same way there is other documentation on the sf.net project page. 
  So we have four sources of documentation:
   -  http://sourceforge.net/projects/perfparse
   -  http://perfparse.sf.net  (== http://www.perfparse.org)
   -  http://wiki.perfparse.org
   -  /doc in distribution.
Some of it must be out of date.  It's a mess :)

(http://wiki.perfparse.org/ is now working and looking very good, thanks 
Flo.)

We need something better which includes the tiki sections and fixed 
documentation.  Can I suggest a new menu for the main site which 
reflects all the document sources.

(This is descriptive only.  Actual URI may differ.)

Menu Option			URI
----------------------------------------------------------
Install Guide		http://perfparse.sf.net/install_guilde.html
Source: doc/install_guide.docbook.html

Readme			Not on site.
Source: doc/introduction.docbook.html

Introduction (new)	http://perfparse.sf.net/introduction.html
Source: doc/README

FAQ			http://wiki.perfparse.org/faq
Copied from: http://perfparse.sf.net/faq.html

Specifications		http://wiki.perfparse.org/??


Any other ideas?

As a final point, we have five locations of html:

perfparse.cgi
perfparse.php
http://perfparse.sf.net  (== http://www.perfparse.org)
http://wiki.perfparse.org
http://sourceforge.net/projects/perfparse

This product overlaps local CGI and true Internet.  Such applications 
and documentation should have consistent html, therefore it all looks 
like the same project.

Some time we will have to look into a consistent look to all of these, 
where possible.  A single style sheet for instance might be an excellent 
start?

Ben