django-qa is a fork from Simple-Q-A-App-using-Python-Django aimed to create a pluggable package than allows to implement a StackOverflow-like forum site for your Django web project. The development of this package is kindly supported by SWAPPS and constantly developed by it's colaborators. Feel free to use it, add some issues if you find bugs or think of a really cool feature, even clone it and generate a pull requests to incorporate those cool features made by yourself; If you have special requirements, drop us a few lines and perhaps we can help you out too.

Please take in considerations than this application is still under active development and we cannot guarantee that nothing will break between versions. Most of the core features are already there, so we expect to release a beta version soon.

Starting with version 0.10.12, django-qa requires Django 2.0 or later and is only compatible with Python 3.5 or later.

• Assumes nothing about the rest of your application.
• Create questions and answers.
• Comment on questions and answers.
• Upvote/Downvote questions and answers.
• Users have a reputation and a profile.
• Support for tagging questions with django-taggit.
• Support for hit counts with django-hitcounts.
• Questions are categorized by latest, popular and most voted.

• The package is integrated with the framework authentication process, right now the package defines an user profile linked to Django's user model, this models was created to contain information related to the user's activities inside the package functionalities.
• It has comments on questions and answers.
• It has no support for anonymous questions nor answers or comments.
• It has a basic implementation for score and reputation records.
• The package has no moderation options on none of the models, and has no REST support.

For better understanding and information, please take a look at the documentation and report bugs and issues in the issue panel if you find one.

With this setup you will have a functional questions and answers section inside your project. Probably you will need to work on the default templates to integrate the look and feel of your site.

If your project has an user profile already, you may want to merge it with the data provided by this app (questions, answers, comments, reputation, etc). That requires some extra work, but can be done without using ugly hacks.

The template structure serves as a foundation for your project, but you can (and should) override the defaults to better suit your needs. For example we load bootstrap3 from a CDN, but if your application already has bootstrap in a package you can just extend from your main base template.