Re: [Plone Mosaic Sprint Barcelona discussion] Re: Plone Mosaic Sprint Barcelona June 10 - 13

Guido Stevens wrote:
>>> freedom to decide how much control the admin and editors have
>>> over the layout, ie a decision made at the birth of a new site.
>
> Very important. This was my immediate concern when I saw the initial
> Deco demos way back when. And this should not only be a global policy
> but something that can be different for various parts of the site, or
> even tweakable at the tile/block level.

This was possible, althought maybe not in such a flexible way as you'd
require.

In Deco-model (p.a.pages) designers could have designed section /
content type specific site layouts and in those layouts, define areas
which would then be editable by the editors (by adding content specific
tiles there; effectively creating a page layout). The demos only
contained the area usually known as "main-slot", but the composition
(p.a.blocks) supports any amount of such areas.

What really is missing is more granular editor permissons. Currently, if
a custom permission could be required for adding a new tile (I think it
only protects the add form), but cmf.ModifyPortalContent is enough to
edit all the tiles (and also remove tiles). That's because the layout is
stored in single attribute, protected by cmf.ModifyPortalContent.

Custom UI could, of course, enforce more strict permission for users
without cmf.ModifyPortalContent.

>> This sounds like how p.a.blocks is made to support two level of
>> layouts ootb: site layout and page layout.
>
> I have some concerns about that. That doesn't seem to support the
> level of granularity in access controls we're used to in Plone. It also
> cuts the rendering problem space in two, which seems awkward. While I'm
> all for solving the #portal-columns rendering first I'd rather not lock
> myself in a box.

I don't fully understand these concerns.

"Site layout" and "Page layout" can be tought as replacements for the
current main_template's master-macro and its main-slot. Except that the
blocks' site layout is simple enough that it could be customized e.g.
for each section in site without the long term issues from overriding
the main_template. (And when a proper layout storage is used, all
layouts are stored in a single place, where they can be batchfixed when
major changes occur).

Also, all the actual content is eventually rendered by tiles, and tiles
are just parametrized views, with all the possibilities we are used to.

Cheers,
Asko

P.S. I'm not trying to make the Barcelona sprint a Deco sprint, but I'd
like to learn from the history and avoid re-inventing too much.

------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs