Forum OpenACS Q&A: Documentation: Packages and "Documentation / Packages"

Collapse
1: Documentation: Packages and "Documentation / Packages"
Posted by Malte Sussdorff on 06/24/07 08:16 AM
At the moment we have two places to store package documentation on the XoWIKI. This does not make any sense at all.

I know this was discussed, but we cannot continue to do things which make it harder and harder for new users to find documentation.

My only question is, which of the two can I delete? Furthermore, which one should be linked from /doc ?

Collapse
2: Re: Documentation: Packages and "Documentation / Packages" (response to 1)
Posted by Torben Brosten on 06/24/07 10:39 AM
afaik, the discussion on this topic is ongoing here:

https://openacs.org/xowiki/Documentation_Project_Discussion

I don't see any reason to choose one over the other when we can blend the two in a harmonious way. I would be pleased as punch if there were some more input on this at the above link (or in this thread).

There are many stale pages in openacs.org outside of the /doc area that need addressing also (updated, removed, or at least added to the robots.txt page etc). Maybe someone with access to those areas can attend to them.

Collapse
3: Re: Documentation: Packages and "Documentation / Packages" (response to 1)
Posted by Torben Brosten on 06/24/07 02:29 PM
Oops, I just got the literal meaning of your references.

You are refering to "Packages" and "Documentation / Packages" in the Xowiki categories located on the left column of each xowiki page on openacs.org, instead of https://openacs.org/test-doc/ vs https://openacs.org/xowiki/openacs-handbook

Each of those has a different purpose.

The "Packages" section is intended to be project pages for each package, where status and other non-documentation items are maintained.

The "Documentation / Package Documentation" I believe is an effort by Robert to move the Package Documentation (that is located in the right column at https://openacs.org/doc/current ) to the xowiki, so that non-cvs committers can contribute to package documentation.