Hi, I want to use Django for portal-like project. There will be no real "public" and "cms" parts -- everybody with an account can log in in one place, even admin. Sort of site where Plone was made for.
Now i was thinking what would be the most effecient, DRY way to use Django here. My first though is to use admin site as a site template. Copy admin templates into new location and try to use it as much as possible, and where it needs customizing -- hook in generic views, and if it is not sufficient -- custom modifiers. Is it the right way of work? Another thing is authentication. Hard to say without tutorial, but Django authentication seems powerfull enough for a portal. I am not sure about ownership of records, the only thing that has something to do with it is auth_admin_log, is it what you use to track down the owner and to do some workflow stuff? ( i can imagine that on a news site content provider cannot publish news, only editor can do it -- that's what I need too). Anyway, if I want to hook in custom authentication, does it make any sense to use admin for this? I believe this question was asked already, but what is the proper way to use custom authentication? Thanks a lot. -- Ksenia
