On Oct 31, 10:42 am, Andy McKay <a...@clearwind.ca> wrote: > One key thing to remember is that Django and Drupal (and the other > things you mentioned) are quite different things. You are comparing > apples to oranges which makes the sell harder.
To clarify - I'm very aware that one is a framework and the other a CMS. That part of the question resolves to something like "Is it easier to use a prefab CMS (Drupal) with all of its opinions and assumptions you have to wrestle with, or to start from the base level (Django) and build up to what you need?" In my experience, the Django admin suffices just fine AS the CMS in many/most use cases, with a few modifications and the occasional custom view. It's been said that Drupal is a CMS with framework-like tendencies while Django is a framework with CMS-like tendencies. The lines get fuzzy. To me, questions like "Is the fact that Drupal is not object oriented and not MVC/MTV a major or minor annoyance?" (to me it's a major annoyance). So I'm aware of the overlaps and differences. I'm really looking for responses to the questions in my OP. ./s --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
