commit ea4497e82f89ae7ab610ea0720450458b35c9664
parent b8bac453719be46ad38a899172af71987fdddb67
Author: Santtu Lakkala <inz@inz.fi>
Date: Fri, 3 Oct 2014 08:16:02 +0000
Wiki with git backend
Diffstat:
1 file changed, 8 insertions(+), 0 deletions(-)
diff --git a/posts/wiki-with-git-backend.md b/posts/wiki-with-git-backend.md
@@ -0,0 +1,7 @@
+# Wiki with git backend
+
+ During a time void, also known as compile time among programmers, I started to play with an idea that had surfaced earlier in lunch time discussions with colleagues. The more I though about it, the worse the idea seemed, and the more I wanted to see how much work it would be. The original idea was that a git would make a great knowledgebase, giving nice diffs and logs and so on, but the less technologically savvy were a bit reluctant, as the magic black-boxes-with-gray-text are not what they consider user friendly. Hence a better interface was needed. And of course plugging a server side wiki engine to a git backend was too simple of a solution. No no no. Of course it had to be done in browser. And hence giki was born.
+
+ So, what exactly is giki? It is a slightly modified js wiki formatting engine, [jquery-wikitext](http://www.kajabity.com/jquery-wikitext/) glued on self made git repo parser, utilizing inflate.js from [zip.js](http://gildas-lormeau.github.io/zip.js/). The result is a very simple read-only wiki, using a git repo over HTTP and doing all the magic in the browser.
+
+ Does it work? Sure it does. Is it useful? Not in the least. Why then? Because I could. If you're still interested, see it [action](http://inz.fi/giki/) (use view source to get to the source). I also used the same git blob parser to implement a simple [repo browser](http://inz.fi/gitweb-js/).
+\ No newline at end of file
