This may be beyond the reach of Django, but I figured it was worth a shot.
I have a site tool not unlike many blogs or CMSs for adding/editing pages. Recently, to enable common components to pages (such as contact forms, site-maps, carts, pre-filled content pages, etc.), the needs for the "Page" administration has changed from: >> Title: Foo >> Content: Bar Baz to >> Title: Foo >> Content: Bar Baz >> Components: >> |- Header >> |- Footer >> |- Sitemap >> |- Contact Form Where each "Component" is its own inherited model that defines any config settings needed. For example, the Contact Form model may have a "To:" field defaulted, while the Footer component has no config settings. The components are assembled in the view. Is there a way to achieve this, or is this beyond the scope of Django? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
