<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><DIV><DIV>On Aug 8, 2007, at 11:33 AM, Kieran Lal wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"><SPAN class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-align: auto; -khtml-text-decorations-in-effect: none; text-indent: 0px; -apple-text-size-adjust: auto; text-transform: none; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; ">I think all the documentation should be a wiki. Click here to edit. Give admins the ability to lock pages, were necessary.<BR><BR>The current status of having 50 comments on a page for something as critical how to upgrade your module to the next API version, is completely unacceptable. We are forcing companies and admins to spend collectively millions of dollars on upgrading their sites between versions with inconsistent and unclear documentation.<SPAN class="Apple-converted-space"> </SPAN><BR></SPAN></BLOCKQUOTE></DIV><BR><DIV>Agree on this 100%.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Something sepeck and I discussed at OSCMS was that all the versions are intermingled, and that ideally we would have handbook views by version number, and done in a way that avoids massive node duplication in order to effect hierarchy.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>The handbooks are a particularly tough challenge. Wonder if what we really need are tabbed views for each page, with each tab offering potentially version-specific info. Even in a wiki, that approach might be helpful from a usability standpoint. The tagging alone gets us part of the way there.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Laura</DIV><DIV><BR class="khtml-block-placeholder"></DIV></BODY></HTML>