Djiki is designed to work as a simple drop-in application. However, it still offers flexibility to adapt to different environments. You may easily set up access policy, change the markup language or replace templating engine to match your needs.
You decide who is able to perform certain operations in the wiki. The actions for which you may implement authorization checks, are:
The authorization is handled by a backend, which you may choose out of the default ones or implement yourself. Just point it in your settings.py file, like in the following example:
DJIKI_AUTHORIZATION_BACKEND = 'djiki.auth.base.UnrestrictedAccess'
The default backends, which reside in djiki.auth.base, support the following policies:
Djiki allows you to use custom markup parser. You may point to the parser in the settings file:
DJIKI_PARSER = 'djiki.parsers.wikicreole module'
The included parsers are:
The default Django templating engine is great but no one is forced to use it. I, for example, use Jinja2 in some of my projects. Djiki has a hook, which allows for quick replacement of the templating backend. The default is:
DJIKI_TEPLATING_BACKEND = 'djiki.templating.django_engine'
There are no other backends included at the moment.
There are more settings to configure Djiki's behavior: