I am working on a Django-based web app that fuels content on community sites, very wiki Kind . The content is in the form of HTML, and users have complete freedom for fork articles / chapters or existing people make their own modifications and add them to the current 'working version'. Maintenance of every article / chapter (original authors [s]) will have the option to accept these changes.
We are also planning to maintain any given two versions - or at least the visuals. Article: For the author-approved editable version and all community-based editing editions.
The amendment system which will handle all the above, mergers and branches at the top of the elaborate history, there is much that is a source modification system, so I consider using the guit to manage these modifications I am doing
My question for the more experienced people of this type of my thing:
-
Is it worth the effort and after this, is it in RDBMS Would it be better than some rolling?
-
And if so, almost, how should I go about implementing it with Django / Python?
Asked again in hopes of catching more answers, this is very important to me
I do not know any Django module what you want (at least the wiki i.e. some light markup language With editable text, coupled version control system), but you can take a look at the page of Git Wiki, section "Wiki, Blog, etc."
Comments
Post a Comment