Hello, what I am looking for is some pointers/articles about a fully modularized architecture, where some of the functionality could depend on an existence of a model in a given project. We are (re)building one of our portal applications, and I would like to fully modularize it.
Just a little example. Let's assume that the portal engine has an 'article' module, and a 'gallery' module. If a specific installation has the privileges for both modules (there are feauture switch apps for this part fortunately) then the editors can attach galleries to the articles in the admin. Same with the 'downloads' module, utilizing it they can attach files to the articles. So far so good, a simple model with some generic relations could solve the problem. But then we add a new module/content type, let's call it 'events'. Both the galleries and files should be attachable to this new content type also. That's the goal I would like to achieve - decouple the modules, but keep the possibility of interaction between them. Are there any open source projects using a similar architecture to look at? Or any articles, examples, I would be grateful for any pointers really, because right now I am stuck here. The only idea I have so far is to create an abstract base class from which all the content types would be extended, and use some custom managers (to check if a given feature is enabled or not) to implement the feature, but I am not 100% convinced it is the right path. Any ideas or advice? Thank you. -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/iapKbwgXD7AJ. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
