On Tue, Sep 6, 2016, Patrick Heneghan <patrickhenegha...@gmail.com> wrote:
>It might help for me to explain this in context - for example, I'm going to >have a "post type" called "blog", which should have title and content >fields, and then "event", which should have additional location, date, and >time fields. Hi Patrick. I hadn't realised that by Page Type you meant, in effect, a different content model. Page Types in django CMS are a way to take a snapshot of a page for resuse, to save you having to re-do a complex layout that you often reuse. If you want to manage weblog content, or events, use a weblog or events application, so that instead of shoe-horning information into unsuitable containers, you can have models that are designed to hold it in the most useful way. Other CMSes (like Wagtail and Mezzanine) extend their pages in the way you describe, but django CMS has always avoided that as a core principle. Daniele -- Message URL: https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id Unsubscribe: send a message to django-cms-developers+unsubscr...@googlegroups.com --- You received this message because you are subscribed to the Google Groups "django CMS developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-cms-developers+unsubscr...@googlegroups.com. To view this discussion on the web, visit https://groups.google.com/d/msgid/django-cms-developers/20160909124333.1996452482%40mail.wservices.ch. For more options, visit https://groups.google.com/d/optout.
