personally I have a beef with the wiki, I see no real reason to keep the wiki.... In my opinion it serves no purpose if our docs are good enough, and kept in SVN they can be updated easy enough by the people that need to.... It&#39;s crazy.<div>

Thanks,</div><div>Ian Caldwell<br><br><div class="gmail_quote">On Tue, Dec 14, 2010 at 7:51 PM, Ian Caldwell <span dir="ltr">&lt;<a href="mailto:inchosting@...400...">inchosting@...400...</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

<span style="font-family:arial, sans-serif;font-size:13px;border-collapse:collapse"><div><span style="font-family:arial, sans-serif;font-size:13px;border-collapse:collapse">hello, </span></div>
<div>This email is sent on behalf of <span style="color:rgb(0, 104, 28);font-weight:bold;white-space:nowrap">Steven M. Ottens.</span></div>
<div><span style="color:rgb(0, 104, 28);font-weight:bold;white-space:nowrap"><br></span></div>I&#39;ve been pondering the wiki-issue ever since I sent my mail on site/menu-structure to Ian.<br>
A few observations:<br>-The current wiki is a MediaWiki-wiki, which is the same as Wikipedia and as such quite known to a broad audience.<br>-A wiki is inherently different from a pre-structured website.<br>-We want to have both a structured website guiding the various target groups towards the info they need and have a dynamic place where new info is quickly (and chaotically) added.<br>


-We want to point people towards the more chaotically but richer information source that is the wiki from the structured website<br>-Any &#39;fixed&#39; content system is not a wiki. I&#39;ve had experiences with various combinations of plain HTML, blogs, CMS and wiki&#39;s and there is no holy grail which will do everything perfect.<br>


<br>So I think we shouldn&#39;t try to get the wiki into Django. The wiki is the wiki and people are reasonably aware of the principle of a wiki.<br>That being said, currently the wiki is a whole separate entity which I never ventured into until today. There is a wealth of information there, but it is hidden behind the simple link &#39;wiki&#39;<br>


<br>So I don&#39;t think we should try to create a design which forces the wiki to behave as the rest of the site, but to create a separate (but similar) design for the wiki to make it clear for the users they are in the wiki with a clear way back to the site.<br>


Also we should make more appropriate links from the site to the wiki. There are many topics in the site which are also discussed in the wiki, we should link to those. I came up in my restructuring mail with &#39;landing pages&#39; on various topics. Having various main pages in the wiki which reflect the menu-structure in the website might create a stronger bridge between the two, without restricting the wiki to the website-structure.<br>


<br>Regards<br>Steven<br><br>note: I know making a difference between the wiki and &#39;the website&#39; isn&#39;t entirely fair, the wiki is part of the website etc etc. It is just a quick way to get the message across (I hope)</span>
</blockquote></div><br></div>