<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><BR><DIV><DIV>On Oct 4, 2006, at 10:25 AM, IchBin wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"><P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Comic Sans MS" size="3" style="font: 12.0px Comic Sans MS">Sorry but where will this be documented once 2.2 goes live. Also will<SPAN class="Apple-converted-space"> </SPAN></FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Comic Sans MS" size="3" style="font: 12.0px Comic Sans MS">there be an index, for the release of 2.2, of all the changes and details?</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Comic Sans MS; min-height: 16.0px"><BR></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Comic Sans MS" size="3" style="font: 12.0px Comic Sans MS">Just new here and do not know these things for a new release.</FONT></P> </BLOCKQUOTE></DIV><BR><DIV>Anyone can document it. Right now it ought to be documented on the Release Notes page. I did look but didn't see it there, so I figured my first step would be to tell the list. I didn't want to add it to the release notes quite yet.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Since these features are technically in beta, the actual documentation pages will probably not be updated quite yet.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Many people write the documentation. PmWiki is documented collaboratively. Any time you find a new solution to a problem and don't see it where you think it should be in the documentation, you can fix the documentation by adding a note, a link, an example, etc. I know I occasionally correct pages in the wiki at pmwiki.org, and I sometimes add things to documentation for script add-ons written by other contributors.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>It's also how I started out with PmWiki volunteerism -- before I knew much, I took posts from the list where people gave each other examples, but the examples and explanations were not in the pmwiki.org documentation -- I cut & pasted wholesale as needed and put the info in the documentation myself. Now that I develop modules for PmWiki, I try to make sure they are well-documented as well, but I have less time to maintain the overall documentation of the site.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>I think I heard something about "Those who can, do. Those who can't, teach." *ducks Patrick* :) In this case "Those who can code, contribute. Those who can't, document." :) Anyone who wants to volunteer their time to help document will be doing PmWiki a great service, whether or not they can write code.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Right now, in this beta release cycle, things change so fast we're better off waiting for the dust to settle before changing the documentation.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Crisses</DIV></BODY></HTML>