> I am working with a small team to create a new web site for our > church. > We have found a site (http://www.prestonwood.org) that we would like > to > use as a model and I am wondering if django is the right tool for the > job. I looked at other django powered sites (http://www.ljworld.com/, > http://www.lawrence.com/) and they have some of the same features. > What > I am wanting to do is give login access to the pastors and other > leaders to update the pages that go with their ministries. > > OK, so now to the questions (assuming that django is the right tool to > use). > > 1. Would it be best to do this all as one app or a separate app for > each page? > 2. Should there be one database instance or multiple (one for each > page/app)? > 3. Is the admin page the tool to use for the posters to use to update > the site? >
Django is definitely great for that kind of project, as long as you are expecting to write python code and not just plug stuff in. If you are weighing it against an off the shelf CMS like Drupal, it may or may not be the best solution. If you were planning on doing any degree of coding and customization yourself, then I'd say it's worth the effort to learn Django. As to the answers: - one app and one database will be fine and probably easiest for you to do while learning - yes, it's very easy to add accounts to the admin interface that have limited privileges. Iain --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
