Separate top-level module

[ivorbosloper]

Interesting project! I'm trying to figure out the best way to incorporate it into an application, and I kind of miss a top level package for the project. Is there a specific reason for putting everything in top-level scope (e.g. crm.urls instead of django_crm.crm.urls ? Or maybe my question is out-of-scope and it's not intended way to use this project.

I want to build an application that also does CRM, in addition to very specific other functionality. By cloning and modifying the django-crm project, I will run into a project-update problem. My idea for the cleanest way to extend this project, is to create a new Django project, install django-crm as a dependency, and by including the django-crm settings/urls I can create an extended application that has additional url/views/models.

However, after pip install django-crm-admin, the webcrm, voip, chat modules become top-level modules (and are usable), but my site-packages now also has the django-crm templates directory and locale. These are not reusable, and everything will conflict/overlap with other packages. I think this could be solved by putting many resources in a top-level django_crm module.

[nitsujri]

I'm in a similar boat in that I have an existing Django project that I would like to add CRM capabilities to as such it doesn't seem like this is designed to do that and that it is its own standalone system.

[DjangoCRM]

Yes, that's right. Django CRM is a Django project which itself consists of Django apps such as:

• Tasks,
• CRM,
• Analytics,
• Massmail,
• ...

The project can be expanded by adding new apps to it.
We will do it - join us!