<?xml version="1.0"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
   <channel>
      <pubDate>Sat, 11 Oct 2008 07:16:06 GMT</pubDate>
      <lastBuildDate>Sat, 11 Oct 2008 07:16:06 GMT</lastBuildDate>
      <language>en</language>
      <docs>http://www.rssboard.org/rss-specification</docs>
      <title>CrunchBang ~ wiki</title>
      <link>http://crunchbang.org/tags/wiki/</link>
      <description>Code, Design &amp; GNU/Linux</description>

<item>
    <title>Wikka Wakka Wiki</title>
    <link>http://crunchbang.org/archives/2008/02/10/wikka-wakka-wiki/</link>
    <pubDate>Sun, 10 Feb 2008 04:54:02 GMT</pubDate>
    <dc:creator>Philip Newborough</dc:creator>
    <guid>http://crunchbang.org/archives/2008/02/10/wikka-wakka-wiki/</guid>
    <description><![CDATA[
    <p>Over the last couple of days I have mainly been playing with <a href="http://wikkawiki.org/ " title="WikkaWiki">WikkaWiki</a>, a flexible, standards-compliant and lightweight wiki engine written in PHP. I&#39;ve toyed with the idea of creating a personal wiki for sometime, but, I&#39;ve been reluctant to start one for fear of it becoming just another thing to update and maintain. Anyhow, I now seem to have conquered this fear and I&#39;ve created <a href="http://crunchbang.org/wiki/ " title="CrunchBangWiki">my first wiki</a>.</p>

<p>Now, being a new wiki it naturally doesn&#39;t contain much of any content, but, at this moment that&#39;s not too important, the important thing is that I&#39;ve started it, the content will come later. I&#39;m planning on using the wiki to document my <a href="http://www.ubuntu.com/ " title="Ubuntu, Linux for human beings.">Ubuntu</a>/<a href="http://crunchbang.org/projects/linux/ " title="CrunchBang Linux project page.">CrunchBang Linux</a> projects. I&#39;ll also be using it to privide supporting supporting material for my blog. For example, stuff like this <a href="http://crunchbang.org/archives/2007/10/26/howto-setup-a-crontab-file/ " title="Howto set-up a crontab file.">crontab howto</a>, and these <a href="http://crunchbang.org/archives/2007/11/17/150-extra-gimp-brushes-for-ubuntu/ " title="150 extra brushes for GIMP and Ubuntu.">GIMP brushes</a> would be better suited to the wiki.</p>

<p>Regarding the WikkaWiki software, it&#39;s quite impressive and fairly easy to work with. I looked at several other PHP based wiki projects, but IMHO WikkaWiki was the best &#8212; apart from maybe <a href="http://meta.wikimedia.org/wiki/MediaWiki " title="MediaWiki - it powers Wikipedia dont you know!">MediaWiki</a>, but then I considered that to be overkill for my needs. If you&#39;re starting a new wiki then I&#39;d certainly recommend at least looking into the possibility of using WikkaWiki. It has many great features, some that I noticed include:</p>

<ul>
<li>a super easy installation process</li>
<li>a nice default design and easy to customise CSS</li>
<li>code base is very hackable, including actions/plugins</li>
<li>RSS feeds for recently updated content, comments etc</li>
<li>syntax highlighting of published code, courtesy of the <a href="http://qbnz.com/highlighter/ " title="GeSHi">GeSHi plugin</a></li>
<li>it&#39;s super scary fast</li>
</ul>

<p>All-in-all WikkaWiki has impressed me a lot; besides, if it&#39;s <a href="http://puppylinux.org/wikka/PuppyLinuxMainPage " title="WikkaWiki - good enough for Puppy Linux!">good enough for Puppy Linux</a>, it&#39;s good enough for me ;)</p>

    <p style="font-size:smaller;">Tags: <a href="http://crunchbang.org/tags/php/" title="Browse all posts tagged with &#8220;php&#8221;">php</a>, <a href="http://crunchbang.org/tags/software/" title="Browse all posts tagged with &#8220;software&#8221;">software</a>, <a href="http://crunchbang.org/tags/ubuntu/" title="Browse all posts tagged with &#8220;ubuntu&#8221;">ubuntu</a>, <a href="http://crunchbang.org/tags/wiki/" title="Browse all posts tagged with &#8220;wiki&#8221;">wiki</a></p>
    ]]></description>
</item>

 </channel>
</rss>