<div class="gmail_quote">On 29 May 2011 23:03, Jack Desert <span dir="ltr"><<a href="mailto:jackdesert556@gmail.com">jackdesert556@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Sat, 28 May 2011 01:19:34 +0300<br>
Eugaia <<a href="mailto:ngx.eugaia@gmail.com">ngx.eugaia@gmail.com</a>> wrote:<br>
<br></div>
<br>
I want to help the cause by getting all the documentation under one roof, easily accessible, and well-organized. Help me to understand how I can do this.<br>
<font color="#888888"><br>
Jack Desert<br>
</font><div><div></div><div class="h5"><br></div></div></blockquote><div><br></div><div>I'd be in favour of copying the pages of <a href="http://nginx.org/en/docs/">http://nginx.org/en/docs/</a> into <a href="http://wiki.nginx.org/">http://wiki.nginx.org/</a> along with links to security advisories, books, etc. It would need to be kept up-to-date, but this would be a start, unless Igor is keen to keep them separate. </div>
<div><br></div><div>I suspect there may be a better way to organise the top-level wiki sections (Install, Modules, Add-ons etc.) e.g. I was surprised to find <a href="http://wiki.nginx.org/HttpCoreModule">http://wiki.nginx.org/HttpCoreModule</a> in Modules when I first visited (it's logical, but wasn't obvious). I also think "Install" on the top level can be reworked to incorporate "Getting started" and "Full example", modified to implement auth_basic as well since this can easily be done dangerously by first-timers. </div>
<div><br></div><div>So I would love to see two navigation paths streamlined: the path first-time users take in downloading, setting up, configuring, and the path returning users take getting reference on core, or on modules. Would be happy to help implement, if this makes sense to anyone else. </div>
<div><br></div><div>Thomas</div><div><br></div></div>