Currently, the model API is subject to smaller changes, and the plugin
API seems pretty stable.

In order to customize the wiki, best idea is to override templates and create
your own template tags. Do not make your own hard copy of this repository in
order to fiddle with internal parts of the wiki – this strategy will lead you
to lose out on future updates with highly improved features and plugins.
Possibly security updates as well!

The release cycle has already begun, so you can administer django-wiki
through Pypi and pip.

All views are class-based, however don’t take it as an encouragement to
extend them, unless you are prepared to modify both templates and view
classes every time there is an update.

Django needs a mature wiki system appealing to all kinds of needs, both
big and small:

Be pluggable and light-weight. Don’t integrate optional features
in the core.

Be open. Make an extension API that allows the ecology of the
wiki to grow in a structured way. Wikipedia consists of over 1100
extension projects
written for MediaWiki. We should learn from this.

Be smart.This
is
the map of tables in MediaWiki - we’ll understand the choices of
other wiki projects and make our own. After-all, this is a Django
project.

Be simple. The source code should almost explain itself.

Be structured. Markdown is a simple syntax for readability.
Features should be implemented either through easy coding patterns in
the content field, but rather stored in a structured way (in the
database) and managed through a friendly interface. This gives
control back to the website developer, and makes knowledge more
usable. Just ask: Why has Wikipedia never changed? Answer: Because
it’s knowledge is stored in a complicated way, thus it becomes very
static.

Django-wiki is a rewrite of
django-simplewiki, a
project from 2009 that aimed to be a base system for a wiki. It proposed
that the user should customize the wiki by overwriting templates, but
soon learned that the only customization that really took place was that
people forked the entire project. We don’t want that for django-wiki, we
want it to be modular and extendable.

As of now, Django has existed for too long without a proper wiki
application. The dream of django-wiki is to become a contestant
alongside Mediawiki, so that Django developers can stick to the Django
platform even when facing tough challenges such as implementing a wiki.

Why not use django-reversion? It’s a great project, but if the
wiki has to grow ambitious, someone will have to optimize its
behavior, and using a third-party application for something as
crucial as the revision system is a no-go in this regard.