Portlets

[tisto]

@sunew any news on that? Would be great if you could share your work. Maybe others can help or take over then...

[sunew]

I have been on Holiday :) I plan to continue during the next week.

On Fri, 5 Jan 2018 at 15.49, Timo Stollenwerk notifications@github.com wrote:

@sunew https://github.com/sunew any news on that? Would be great if you could share your work. Maybe others can help or take over then...

— You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub https://github.com/plone/plone.restapi/issues/445#issuecomment-355572211, or mute the thread https://github.com/notifications/unsubscribe-auth/AA2g1kVKJ-jtbnGKVQOX5xdCXe-PlrNWks5tHjZ-gaJpZM4Qpfwd .

-- Sune Brøndum Wøller +45 24256610 skype: sune.woeller

[rodfersou]

My 20 cents: https://github.com/plone/plone.restapi/pull/669/files

Hope someone can continue this work, since I have other priorities now.

[datakurre]

@tisto @sneridagh Now that you have good experience of Volto in real-life projects, what's your take on portlets?

We love criticizing them, but in years with Mosaic in production, we still have a valid use case for them: being able to add inheritable (yet overridable) configuration into folder hierarchy. Even the famous "Blocks based layouts"-manifesto was missing replacement for portlets (only vague ideas, that would only have reimplemented them).

How have you solved use cases for portlets? Would portlets as a way to store inheritable configuration make sense for your use cases?

@sneridagh For example, could you think of using Plone portlet machinery to store Volto blocks' configuration in re-usable and inheritable way so that a regular Volto block could render "sub blocks" from a named portlet manager? (Or are "university sites" only complex enough for use cases like this :)