On 6/21/07, Tyson Tate <[EMAIL PROTECTED]> wrote: > > > On Jun 21, 2007, at 5:11 PM, Noah Gift wrote: > > > I think your being a bit misleading. Of course you can use django > > for a CMS. It certainly doesn't hurt that CMS was the problem > > domain being addressed while Django was being written either. Just > > take a look at 99% of the jobs on django-users. "Hi, I work for a > > newspaper.....". So yes it can be a CMS if you write the code for > > it, and it is probably one of the problems django does best. > > Saying django is not a CMS is kind of like Elvis saying he wasn't > > influenced by the Blues... :) > > Well, technically, Django is a *framework*. It is *not* a CMS. Once > you install and configure Django, you still have absolutely nothing. > You can build a CMS with it, certainly, but that doesn't make Django > a CMS itself.
Yes. That was my point as well if you notice. My other subtle point was when someone means to ask the question, "I have heard that the Django web application framework is friendly toward the creation of CMS sites", but really asks, "I need Django for a CMS..." understand this is probably what they mean. Btw, isn't a Newspaper quite literally content being managed systematically? Seems like the framework certainly helps solve that problem: "Developed and used over two years by a fast-moving online-news operation..." Seems like yes...CMS is something the "Django Framework" was built for no? Saying Django is a CMS because you can use it to make a CMS is like > saying my oven is a pie because I can make a pie with it. > > > -- http://www.blog.noahgift.com --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
