Hi there, is there any progress in this area? I have the same feeling about explaining that "all the other parts of the site" behave differently (i.e. publish changes immediately). From a user perspective all pieces of a CMS-driven website must work the same, users take this for granted. Zinnia blog is one specific example of an app that is somewhat well integrated (CMS placeholders for editing blog entries, dedicated CMS toolbar menu), but lacks the final polish.
That translates to nothing else than: provide integration points for CMS plugins. All features that are available for "CMS objects" (pages, placeholders) should be available for integration to 3rd-party apps. For the publishing concept this translates to: there must be an API function that allows, probably, extending the model "the django CMS way" (by magic) including the integration with the Publish button on the CMS toolbar. >From my perspective, it's all about enhancing the feature set of the django CMS plugins API. As for what I can see, there is nothing about that on the roadmap, at least not on the one publicly available [1]. I do believe though that this should be one of the core features, the actual "purpose" of django CMS' existence and the differentiator towards other CMSes: Be just a thin layer, an integrator for apps of the Django eco system. It should be easy to integrate everything seamlessly into a Django powered website, provided you use django CMS. Any thoughts or plans about this? Peter [1] https://www.django-cms.org/en/roadmap/ Am Montag, 15. August 2016 08:31:14 UTC+2 schrieb Angelo Dini: > > Hello benzkji > > Yes we thought already about it and it seems a bit more complicated than > expected. It requires some major refactors of several CMS components to > make this work. Eventually Paulo or Martin could lay out the problematics > in more detail. > > Cheers > Angelo > > On Saturday, 13 August 2016 08:37:30 UTC+2, benzkji wrote: >> >> Hi all >> >> Publishing content with django-cms is super easy, and the draft/live >> concept is great. But, have you ever thought about applying that concept to >> external apps/models too, ie, generalize the concept and make it available >> to all apps? >> >> It's just...more than one time, I felt a bit awkward when explaining like >> "but with the news/jobs/whatever, the changes are online immediatly" to a >> client (my models normally just have a "published" BooleanField). >> >> Any thoughts on this (I already posted this to google, but might reach >> another audience here...)? >> >> Best >> Ben >> > -- Message URL: https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id Unsubscribe: send a message to [email protected] --- 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 [email protected]. To view this discussion on the web, visit https://groups.google.com/d/msgid/django-cms-developers/cb57acfe-0771-498f-982a-719e75a25e81%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
