Publish workflow for all apps

[benzkji]

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

[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

[Peter Bittner]

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/

[Ben Stähli]

HI Peter

For me, the CMS integration with other apps is almost perfect - we have already have placeholders for external models, frontend model editing and different list views in the frontend... , the publishing workflow would be one of the bigger final pieces - for me. Though it would be quite heavy to integrate, as Angelo pointed out.

I don't know Zinnia, but from my personal experience, just taking an existing app and adding an CMSAppHook is normally not a good idea, at least if there are "customer facing" parts. Zinnia might be somewhat in between, as it has at least CMSPlugin support.

Anyway, would be glad to see it on the roadmap - somewhen ;-)

Best
Ben

-
Ben Stähli
bn...@bnzk.ch
+41 22 575 25 77
bnzk.ch
-

> --
> Message URL: https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id
> Unsubscribe: send a message to django-cms-devel...@googlegroups.com
> ---
> You received this message because you are subscribed to a topic in the Google Groups "django CMS developers" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/django-cms-developers/OlmhWkb-1NM/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to django-cms-devel...@googlegroups.com.
> 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.

[googl...@jensdiemer.de]

Any news here?


I use https://github.com/andersinno/django-model-publisher-ai for this. But it would be nice to have this feature from django-cms, with the same workflow.

I think the effort is manageable, isn't it?

I see nothing on the roadmap: https://www.django-cms.org/en/roadmap/

[googl...@jensdiemer.de]

See also: https://github.com/andersinno/django-model-publisher-ai/issues/15

[benzkji]

Hi Jens

As always, response times from the core team vary...understandable, for an open source project.

-

I, on the other hand, have implemented an experimental autopublisher for the cms, as for small sites, it just is in the way...

-

As said, very experimental, and just dont mention performance: https://github.com/bnzk/djangocms-misc

But it werks!

-

Best

Ben