How should the project be organized to best suit third-party use?

[odinho]

Other assignments I've worked on could just have the settings files as part of the project. Only taking out the secret keys etc. -- However, this is meant to be generally useful for third-parties, and I don't think we all should have our configs in this project.

Also, it's eaiser when it's just one django app, and you don't expect to give any project at all. But this is in-between those. It's no single pluggable app, it's meant to be used as a project, but django does not always make that super easy.

It's worth looking into what other projects do here.

[odinho]

I remember Armstrong CMS standing out. It used something similar to django-admin.py, and you did armstrong-admin startproject mysite to create the project mysite. It copied in all the skel files and set up a working structure.

Maybe that's a solution worth going for. The way it is currently structured also do work, since I am already using it, -- but it requires some python-path specification and keeping the settings files outside the project. There might be better idioms to follow.