I'm one of those people who has to at least try to keep all their neurons running smoothly, and as such, now that I'm back into Marketing, I've been trying to redress the balance when it comes to coding - just as my hobbies at home revolved around reading business news when I was in Engineering, I'm now starting to go the other way and have begun to exercise the more technically bent grey cells around one of my pet projects - and one that I've been postponing for, oh, a couple of years, give or take a few months.
Which, in a nutshell, means that Yaki is here, running off a test account on my mini while I hack away on it. Expect a lot of breakage (and lots of missing content, since all it has are its own docs and a few test pages), but hopefully it will be up to the task of running this site within, oh... half a year or so.
And yes, I could probably use something coded by someone else, but like I said only this morning, some people build model boats as a hobby. Me, given the time constraints I have, painstakingly code in the simplest way possible (refactoring endless times) so that I can pick things up again after this week's 20 minutes of quality coding time are up.
A few things that will eventually make it to a FAQ:
- It supports HTML, Textile and Markdown (everything is rendered into HTML, strained through the utterly, utterly amazing Beautiful Soup and pre-cached to kingdom come).
- There's no browser-based editing, by design. Some people will say it isn't a Wiki without that, but I'd much rather have a text file tree that I can index using Spotlight and rsync across, and I honestly don't want to fiddle with browser-based editing until Safari does it properly.
- No, I'm not publishing source code for the moment - I have very little time to code my own bits, let alone manage feedback or fix bugs for other folk, and that will stand until it's "good enough". Once it is good enough to run this site, I'll put it up on Google/Code.
- It only seems slow because it will be running from my home DSL connection for a while (like this very site did right at the start). That will be the main incentive for my re-implementing all the caching goodness I did for PhpWiki.
Oh, and by the way, it runs pretty well on an NSLU2. The only reason it isn't running there right now is that I couldn't bother to set up Subversion on the NSLU2, so it's a bit of pain to update the code on it - but you can bet that I will be optimizing some bits of it there...