I've never believed that the web is a natural place for applications, so I am amused that you want a wiki to work offline - a typical webhead contradition. Having said that, I think aspects of Tiddlywiki may have some of these features.
Given a Wikis job and audience, its obvious that using only HTML isn't practical. You are denying the need for a DSL for a domain specific job. I accept that many users are just going to use the full GUI anyway, so don't care either way.
I use Confluence and its slow, organised a bit haphazardly and it definitely is a bit "enterprisey". But its easy to do the basics, and you can learn it iteratively. That matters - complexity that can be uncovered at the users own pace is fine.
But Confluence is certainly full of strangeness. URLs tend to ignore folder hierarchy. Search also appears to ignore hierarchy (hence, I can't search for tags in sub pages - only in "spaces"). Access to CSS or templates is vague.
So by all means get with git - but don't forget what job wikis are supposed to do, as opposed to just what you would like them to do.
First, full HTML is usually to complicated for intended audience to edit; wiki syntax (or reStructuredText, or Markdown, or Textile) is much simpler. Additionally you have to worry less about cross-site scripting and similar hacking, hidden spam and like. So don't diss wiki syntax.
Second, you might be interested in ikiwiki, which is wiki compiler which you can then use with version control system of your choice, for example Git.
Or you might want to try out a new kind of wiki: Gazest by Yannick Gingras, which tries to bring merge based (instead of usual lock based) version control workflow to wikis.
2008-03-09EDT19:56:15+00:00
#
Second, you might be interested in ikiwiki, which is wiki compiler which you can then use with version control system of your choice, for example Git.
Or you might want to try out a new kind of wiki: Gazest by Yannick Gingras, which tries to bring merge based (instead of usual lock based) version control workflow to wikis.
Since TiddlyWiki was mentioned, I wanted to point out another option: Luminotes, which is a WYSIWYG personal wiki notebook. It definitely doesn't satisfy all of your wiki longings, since it's online-only and doesn't use git or svn for a backend. However, its big redeeming feature is that you don't have to use a funny little wiki markup language. It's more like editing a traditional document, but with the ability to make links between notes.
If it sounds interesting, you can check it out at http://luminotes.com/
(Disclaimer: I'm a Luminotes developer.)
2008-03-19EDT20:48:16+00:00
#
If it sounds interesting, you can check it out at http://luminotes.com/
(Disclaimer: I'm a Luminotes developer.)
I liked this blog post. I used to maintain a local copy of mediawiki for all my notes and code snippets, but the syntax drove me nuts. Eventually I ditched it and just used grep and vim like you, in a bunch of text files, because I don't need a pretty web front end to quickly access my own information. But obviously for other users this wouldn't work.
I'm going to take a look at git-wiki, because I think wiki's are very valuable for users, and I just can't deal with most wiki syntaxes that slow me down.
2009-04-05EDT06:04:16+00:00
#
I'm going to take a look at git-wiki, because I think wiki's are very valuable for users, and I just can't deal with most wiki syntaxes that slow me down.
