Should I use the built-in Django admin for a decent sized project?

I haven't used Django for too long, but I'm going to start a project with a fairly large size. I am always nervous using fairly new frameworks (new to me) in large projects, because I was burned before. However, I'm pretty sure about Django ... it will finally be a project that will make me jump from my native PHP infrastructure to the popular Python infrastructure. (Yay!)

In any case, my question is whether the Django admin is built-in enough to be used for a full-fledged client-oriented interface (clients will use it themselves, not me). I see that this is pretty customizable, but I'm wondering if enough is enough to handle various non-standard cases. I have no concrete examples since I have not started yet.

Has anyone used the Django admin for some pretty customizable interfaces that non-programmer users use? Was it worth it? Would you rather just create your own admin interface specifically for the site?

To clarify, users will be completely non-technical.

+5
source share
4

, admin django , .
, , -, , Django book ( ):

- . -, , , .

(, ), .
, , .

, , , , ReviewBoard: , .

, . , , , , Django . , , .

+4

CMS Django, ( , , , , youtube flickr, , , ..), . , .

, admin.py, . , , tinyMCE Filebrowser, .

, , . , Django . , , .

+3

. , , , , , . , . , , .

, , ( filter_horizontal raw_id_admin !)

, , , . , , ( , , ), , . -, django, .

+2

, Django admin . , ( Django ), , Django (, , " ".

, - ", , " , , , , , .

+2

All Articles