Sean Schertell wrote: > I'd really like to use Django templates and stay DRY by using the > same base template for my static pages as I do for any apps in the > site. But I'm a little bit put-off by the "flatpages" middleware > because it store the content in a database -- seems to complicate > things unnecessarily
I think that from the point of view of users of your CMS it's less complicated, not more, simply because they can edit flatpages right in the admin. From the point of view of performance you can just cache flatpages and they won't hit DB most of the time. Which is also recommended for any static content be it flatpage or not. > (and seems to require a separate base template > too). Not at all. FlatPage model has a field where you can specify any template. But this is really depends on complexity of your static pages. If they have only one user-editable block of text then flatpages would play nice. If they are more complicated (for example there is some "links sidebar" that is different for each page and should be edited manually) then it's better to make a simple model with couple of text fields and use generic views to save yourself some coding time. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
