[Plone-conference] Openspace: growing plone | as a brand

Martin Aspeli optilude at gmail.com
Thu Oct 30 09:41:37 UTC 2014


This is the PDF, thanks to Laurent for rescuing!

On 30 October 2014 08:42, Maurizio Delmonte <maurizio.delmonte at abstract.it>
wrote:

> I still remember the night I discovered that document, the tears of joy at
> the end of the reading, the fact that I could not get asleep, and the deep
> gratitude and respect for such a valuable, clean and fresh perspective on
> CMS you guys were proposing.
>
> Thanks,
> Maurizio
> Il 29/ott/2014 09:26 "Laurent Lasudry" <laurent.lasudry at affinitic.be> ha
> scritto:
>
>  There it is :-)
>>
>> Laurent.
>>
>>
>> Laurent Lasudry wrote:
>>
>> I do !
>>
>> Laurent.
>>
>>
>> Martin Aspeli wrote:
>>
>> I have it... the problem is it's in some old version of Pages that I can
>> no longer open. ;) Anyone have Pages '09?
>>
>> On 27 October 2014 16:21, Asko Soukka <asko.soukka at iki.fi> wrote:
>>
>>> Hi all,
>>>
>>> Martin Aspeli wrote:
>>>
>>>> Of course we tried this in 2007 when Alex and others invented Deco (the
>>>> original, bold, clean and beautiful concept) and that may well have done
>>>> it. I still think that it's better than anything else out there even
>>>> now, although the gap is narrowing.
>>>>
>>>
>>>  I hope that somone could bring the original "Deco+UI proposal.pdf"
>>> online again.
>>>
>>> As you may know, Mosaic Sprint Barcelona worked hard to fix the "boring
>>> legacy stuff" to give the Deco vision a yet another change as Plone Mosaic.
>>> So, with plone.app.mosaic (and its versions of plone.app.blocks and
>>> friends), it's possible to use these new style layouts side by side legacy
>>> templates, already with Plone 4.3+.
>>>
>>> And how is Mosaic relevant to this discussion? The Deco/Mosaic vision
>>> describes the UI layer using such terms and technologies that it's no
>>> longer tied to the current Plone technologies. Deco/Mosaic page composition
>>> (be it plone.app.blocks, Varnish ESI, or something else) does not really
>>> need to care where do those layouts and tiles come from.
>>>
>>> So, as long as used tiles are not interdependent, their backend could be
>>> replaced one by one with any fancy new technology (of course, it would
>>> help, if we could make Plone ZODB accessible from Python 3 code).
>>>
>>> Cheers,
>>> Asko
>>>
>>> _______________________________________________
>>> Plone-conference mailing list
>>> Plone-conference at lists.plone.org
>>> http://lists.plone.org/mailman/listinfo/plone-conference
>>>
>>
>>
>>
>> _______________________________________________
>> Plone-conference mailing listPlone-conference at lists.plone.orghttp://lists.plone.org/mailman/listinfo/plone-conference
>>
>>
>>
>>
>> _______________________________________________
>> Plone-conference mailing list
>> Plone-conference at lists.plone.org
>> http://lists.plone.org/mailman/listinfo/plone-conference
>>
>>
> _______________________________________________
> Plone-conference mailing list
> Plone-conference at lists.plone.org
> http://lists.plone.org/mailman/listinfo/plone-conference
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.plone.org/pipermail/plone-conference/attachments/20141030/6702a820/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Blocks.pdf
Type: application/pdf
Size: 89959 bytes
Desc: not available
URL: <http://lists.plone.org/pipermail/plone-conference/attachments/20141030/6702a820/attachment-0001.pdf>


More information about the Plone-conference mailing list