Choosing a wiki engine.
Django has a wiki at its official site. https://code.djangoproject.com/wiki I suppose this wiki engine must me rather stable and well supported. Maybe this is the best choice.
Could you tell me what is the name of this wiki application.
djangoproject.com uses Trac as an issue tracking system, Trac has a built-in wiki engine so I guess it is what they use (I grepped the djangoproject.com source code and did not find reference to any other Wiki engine).
A dedicated Wiki engine probably is a better choice than Trac's one but I have no expertise on the issue so I can't help you any further.
Related
I'm starting to learn how to use Django on the Google App Engine.
I had search about some introducing tutorials, like this one.
But looks like isn't really updated (November, 2010).
I really appreciate if someone could point to me a good tutorial, updated (to works with the latest stable release of django/django-nonrel and GAE).
(Strange, why the tutorials tag is not allowed?)
I was able to get it up and runnining, with very little Django or App Engine experience, using this:
http://www.allbuttonspressed.com/projects/djangoappengine
The one big difference I would say is grab the source from the django-nonrel github account, which is more recent than the ones indicated in that tutorial
https://github.com/django-nonrel
Note, allbuttonspressed is outdated, use the following:
http://django-nonrel.org/
http://djangoappengine.readthedocs.org/
I'm looking to "embed" a forum into an existing website. I've talked to Ray about what it'd take to do this with Galleon (a great CF-based forum), and it's doable.
As part of due diligence, I'd like to know if any existing ColdFusion-based forum software was designed with embeddedness in mind; in other words, forum software that wasn't built to just be run as a standalone application.
Thanks!
Marc, if you're looking for an add-on to a Mura CMS site, you should check out Meld Forums - https://github.com/meldsolutions/Meld-Forums. Free, open-source, etc.
I am at present building a medium-sized educational website containing text, academic articles, blog, audio book excerpts, mathematical demos, etc., using custom CSS styles. I am leaning toward two ready-made solutions:
django-cms; and
textpattern.
I have ruled out WordPress because customization is not so easy. Joomla is overkill for this website and the table based design it uses is against my philosophy.
Because I have a number of years of experience in django, django-cms seems to be the natural way to go, but textpattern has more out-of-the-box features and is well supported.
What are the pros and cons between django-cms and textpattern based on prior experience of the people on this list?
Many thanks.
For a comparison of CMSes the best site I have found so far is:
http://cmsmatrix.org/matrix
Over 1200 CMSes are listed and you can compare CMSes by clicking on the checkboxes provided this helped me make my decision and ended up turning back to one of the popular CMSes namely WordPress.
Because I have a number of years of experience in django, django-cms seems to be the natural way to go, but textpattern has more out-of-the-box features and is well supported.
django-cms also has a lot of features from plugins and are well supported too.
django-cms is a fine software which even has it's own hosting site. If as you seem to suggest, the only reason you are looking at textpattern is because it has many out-of-the-box features, then you should really go the natural way with django-cms.
I'm a fan of Textpattern and have been using it for years now. It's benefits are its simplicity and light-weight making it perform well. However, these might be an issue for you if you are wanting to build different content types. Textpattern's interface treats all article content as the same (unless you start install a load of plugins to tweak this). This is fine if your site is primarily for articles, but from what you've said in your question I suspect not.
It is really simple to download and install; so I'd recommend giving it a quick look to see what it can do for you.
I have read the original and updated guides in the Mantis Wiki on how to integrate DokuWiki, but when I follow those instructions now it gives me a number of errors. While doing so I noticed that a lot of Wiki integration is now already supported, and the instructions conflict with what is already there.
In the administrator and developer guides in the Mantis documentation there is nothing relating to wiki integration, and I don't see anything in plugins either.
So, where will I find decent documentation on integrating a Wiki (the DokuWiki on has some excellent integration, would prefer that) with Mantis?
It appears that the answer was on the original page, but fairly easy to miss. Basically just ignore everything in the Mantis Steps section, and edit the wiki values in the config_inc.php file.
I'm working on a Django-based web app in which the community fuels the content on the site, much like a wiki. Content is in the form of HTML, and users have total freedom to fork articles/chapters or make their own modifications to existing ones and add them to the current 'working version'. The maintainer of each article/chapter (the original authors[s]), will have the option of accepting these changes.
We're also planning on maintaining two versions - or at least views - of any given article: the author-approved edits version and the free-for-all community based edits version.
The revision system that would manage all this forking, merging and branching on top of detailed histories is starting to sound a lot like what a source revision system does. So I'm considering using Git to manage these revisions.
My question to those more experienced in this type of thing than I:
Is it worth the effort and after that, will it be better than rolling something out in a RDBMS?
And if so, roughly, how should I go about implementing this with Django/Python?
asked again in hopes of catching more replies, this is very important to me
I don't know any Django module which would offer what you want (at least wiki i.e. editable text with some lightweight markip language, coupled with version control system), but you can take a look at InterfacesFrontendsAndTools page at Git Wiki, section "Wikis, blogs, etc.". Among others you can find there:
wikiri: simple, single-file wiki written in Python, with optional git support for history tracking
Chuyen: a weblog software written in Python, using the Django web framework and Git as its data storage backend through PyGit
Pystl: very simple, small blog engine in Python, using Git for version control.
You might consider looking at how ikiwiki works. It's a simple wiki system that can be backed by a real version control system (I use it with a Git repository).
GitPython is a python library that interacts with Git repositories. I've played around with it, but not used it in production. It seems solid and relatively easy to use, and is under active development.
If you have difficulties integrating Git with your Django project, you might look at Mercurial. I strongly prefer Git, with its elegant and powerful data model, but Mercurial offers functionality similar to Git and it is written in python, so it might be easier for you.
django-rcsfield might be helpful. It is a field (like models.TextField) for the Django web framework which - under the hood - versionizes its content. The 'rcs' in the name is short for revision control system.
http://code.google.com/p/django-rcsfield/
I've just seen this on reddit:
https://launchpad.net/django-wikiapp/
Django WikiApp is a pluggable
application for Django that aims to
provide a complete Wiki (for really
small values of "complete").
HIH,