So I'm taking over a project (which already has a strong start in Django) from a few guys. I'm new to the framework (but experienced as a programmer) and excited for everything about it (the project, Python, and Django).
I have one general design question. But first, some background The site is something we will be providing as SaaS to various customers (lets call them units) for interfacing with their own customers. Each unit will have various sub-units. So we are dealing with a product having several web interfaces, with varying levels of r/ w access to data: The interfaces: - sys admin (Default Django Admin: my co.) - unit dashboard (i.e. unit admin): (can edit data related to their specific unit) - sub-unit dashboard: (can edit a little bit of data, specific to their subunit) - authenticated public interface (subunit's customers) - unauthenticated public interface We're working on pretty designs for everything but the sysadmin, for which we're stoked to be using Django admin. So the question is, for each of the "dashboards"--which are essentially limited admin interfaces--would it make sense to extend or inherit from Django Admin in some way? Or should I just design these like I would client-side pages, with specific forms to edit the pertinent data that a user has permission to edit. I realize this may be a total noob question, but I wanted to get a general idea of which tree to start barking up from an architecture standpoint Thanks, bdr -- You received this message because you are subscribed to the Google Groups "Django users" group. 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.
