It really depends on the project you're working on. The resistance comes mostly from developers who utilize the admin as an open interface to the database with minimal restrictions. I like to use the admin this way for large projects that are used by many people, building out a custom "staff" portal for non-technical staff users (more data validation, form helpers, general improved UX) and using the Django admin strictly for developer use.
I have built smaller projects, generally standard brochure style sites (things most people would use Wordpress for) and used the admin as the CMS for the client. I only ever customized the nav bar with client brand name/colors <http://ryangallen.com/wall/4/tidy-django-admin/> and utilized the options on the ModelAdmin object <https://docs.djangoproject.com/en/1.8/ref/contrib/admin/#modeladmin-options> to make it as convenient as possible. Never had any complaints, it's pretty straightforward and still allows you to upgrade Django gracefully. On Wednesday, September 23, 2015 at 4:00:01 PM UTC-4, Joshua Pokotilow wrote: > > Hello! I just had a fairly lengthy conversation with my colleagues about > whether or not Django admin is well-suited to external users outside our > company. I took the position that for certain use-cases, exposing Django > admin to third parties makes a lot of sense, given that the admin > application has all kinds of features baked in that are well-suited to > certain admin tasks (ACL, customizable templates, dynamically built CRUD > forms, etc.). Unfortunately, I met with a lot of resistance on account of > fears over ease of customizability, security, and technology lock-in. > Furthermore, there was some concern that exposing Django admin to > third-parties might send us off the beaten path, and that doing so could be > an antipattern. > > I would appreciate knowing how other developers feel on this subject, and > would love to hear about how some larger companies that use Django > (Instagram, Disqus) think things through. > > Thanks. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/3c494e01-a5fe-4c40-873d-d07a6b5eaa58%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
