Priorities! Priorities!
Published: jul 17, 2012
Category: Tech
Tags: blog
Language: [English]
page views: 317

So, i havn't blogged in ages. There's nobody to blame but me...

Basically the problem has been that I've been annoyed with this platform. I want something better then this. But then, i don't find the time/energy to actually do the work. So I get annoyed with the platform, wonder about what to change it with, what framework / database etc.

But since I don't get around actually do any writeups either, nothing happens. A classic catch 22 mixed with some proper yak-shavin'.

The possible alternatives i've come up with (in no particular order) are:

• tiddlyweb with a custom javascript front end. This is nice since the tiddly API  is really neat and fits with my vision of how web should be. Also good is that it is basis for a wiki and all navigation is unstructured. Bad is that I can't wrap my head around how it all works both administration and development wise.. The standaard backend seems to be filebased, which is not that cool. And maybe more of a javascript climb then i'm willing to do at this moment.
• smallest-federated-wiki by Ward Cunningham. Again, this is how i see the web should work. With some really interesting wiki federation semantics worked out. But the implementations are done in ruby and node.js... and to learn/manage yet an other language is not what i'm looking for. However a federation of loose sites is how facebook will be undone at some point (open always wins)
• django-cms might be a good idea. it certainly ticks a lot of the boxes. But then it's a CMS again, and i really want a structure free wiki thing. That whould mean adapting a lot of content scanner stuff to make sure it starts to associated like a wiki does. This seems to be the most reasonable route at the moment.
• MoinMoin2. Honestly i havn't looked at it. but the word at Europython 2012 was, that i is currently in full-non-production ready-flux and do i want to base some development on that?
• use a no-sql (like mongodb or redis) and add a thin layer of Flask or somesutch to get it all going. This is the hardcore route, and lots of fun, but not for this moment.

Anyway. I've decided that whatever happens, it will involve moving the existing content from the old to the new system. So then what better to do then make sure there is some content in the old system? All i did for now was add ckeditor to the Django admin and will now compose from there. and maybe add some features along the way.

And it seems to work.