django-wiki
- 0 ratings
Wiki system with complex functionality for simple integration and a superb interface. Store your knowledge with style: Use django models.
Deploy this app to Linode with a free $100 credit!
For upgrade instructions, please refer to the Release
Notes <https://django-wiki.readthedocs.io/en/latest/release_notes.html>__
Django-wiki is fully translated into 13 languages, apart from the default (English) and some additional languages underway.
But please help out in adding more languages! It's very easy and you don't even need to be a programmer.
Some languages...
Visit the django-wiki project on Transifex <https://www.transifex.com/django-wiki/django-wiki/>__
A demo running the latest main branch is available here:
Sign up for an account to see the notification system, or you can log in with the existing account:
adminadminPlease use our IRC or mailing list (google group) for getting in touch on development and support. Please do not email developers asking for personal support.
<https://github.com/django-wiki/django-wiki/discussions>__#django-wiki on libera.chat <https://web.libera.chat/?channel=#django-wiki>__django-wiki@googlegroups.com <https://groups.google.com/forum/#!forum/django-wiki>__twitter:djangowiki <https://twitter.com/djangowiki>__On a number of factors, this project has proven itself useful and stable.
wiki), using SemVer <https://semver.org/>__ versioning schema.What should I customize? What can break? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
You will need to learn a bit of Django to customize django-wiki.
The simplest 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, plugins and security fixes.
You can also override the whole Bootstrap theming. At present, you're best off maintaining your own Bootstrap SCSS and hard-copying, then overriding django-wiki's rules.
All Python views are class-based. However for most cases overriding views and URLs shouldn't be the best place to start since most customization can be achieved through plugins, templates and SCSS.
Contributions are welcome! ❤️
Please read our
Developer Guide <https://django-wiki.readthedocs.io/en/latest/development/index.html>__
Django needs a mature wiki system appealing to all kinds of needs, both big and small:
1100
extension projects <https://phabricator.wikimedia.org/diffusion/query/all/?after=1100>__
written for MediaWiki. We should learn from this.This
is <https://upload.wikimedia.org/wikipedia/commons/f/f7/MediaWiki_1.24.1_database_schema.svg>__
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.See the docs/ folder, or read them at:
https://django-wiki.readthedocs.io/en/latest/
If you wish to add something, please ask in the google group or raise an issue if you're in doubt about whether something might change.
Django-wiki is a rewrite of
django-simplewiki <https://code.google.com/p/django-simple-wiki/>__, 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.
wiki ? Because when we tried
pip install wiki, it returned "No distributions at all found
for wiki", so we had to make up for that! ...oh, and django-wiki was occupied.Markdown <https://pypi.python.org/pypi/Markdown>__. The markup
renderer is not a pluggable part but has been internalized into core
parts. Discussion should go here:
https://github.com/django-wiki/django-wiki/issues/76There is a docker container available here: https://github.com/riotkit-org/docker-django-wiki
edX <https://www.edx.org/>__ & MIT for finding
and supporting the project both financially and with ideas.django-mptt <https://github.com/django-mptt/django-mptt>__, a
wonderful utility for inexpensively using tree structures in Django
with a relational database backend.oscarmcm <https://github.com/oscarmcm>,
atombrella <https://github.com/atombrella>,
floemker <https://github.com/floemker>,
rsalmaso <https://github.com/rsalmaso>,
spookylukey <https://github.com/spookylukey>,
jluttine <https://github.com/jluttine>,
duvholt <https://github.com/duvholt>,
valberg <https://github.com/valberg>,
jdcaballerov <https://github.com/jdcaballerov>,
yekibud <https://github.com/yekibud>,
bridger <https://github.com/bridger>,
TomLottermann <https://github.com/TomLottermann>,
crazyzubr <https://github.com/crazyzubr>, and everyone
else <https://github.com/django-wiki/django-wiki/graphs/contributors>
involved!Original source of inspiration back in 2009 was django-cms, and since then Wagtail has also done a tremendous amount of work to promote Django models as a fundamental structure and enabler for application design.
Please login to review this project.
No reviews for this project yet.
Comments (0)
Please login to join the discussion on this project.