> Could you grant me /zdeneks/ access to that mindmap?
It is an xmind file and attached to the wiki page. w

> I'm going to fix some stk bugs when time allows and wouldn't like to be
> in conflict with your plans.
fixing bugs never conflicts my plans ;-)

> 
> -z 
> 
> On Thu, 2010-06-17 at 17:20 +0200, Philipp Bärfuss wrote:
>> Hi,
>> 
>> 
>> I summarized our workshop on the workshop's wiki page[1]. I also
>> uploaded a mindmap in which I tried to mark potential changes for STK
>> 1.4 (green) and STK 2.0 (red).
>> 
>> 
>> Thanks a lot for all the valuable input!
>> 
>> 
>> [1] http://wiki.magnolia-cms.com/display/DEV/STK+2.0+Workshop
>> 
>> 
>> Mindmap:
>>     * STK 2.0 Workshop - Overview.png
>>     * STK 2.0 Workshop.png
>> 
>> 
>> Summery as found on the wiki page:
>> We will improve the framework
>> 
>>     * separate framework templates/paragraphs and the base framework
>>       should get separated, the set of base templates should be
>>       smaller, extras as Glossary, FAQ, ... will go into an extra
>>       module
>>     * less paragraphs combine paragraphs like the various teaser
>>       groups into a single one. Magnolia 5.0 will support such
>>       dialogs in a better way, alternatively we could introduce tabs
>>       in the paragraph selection dialog
>> 
>> The STK is on a good path, but few things are to complex and should
>> get improved.
>> 
>>     * imaging
>>             * the CSS selector based system is not transparent
>>               enough, we prefer a less flexible solution
>>     * resources
>>             * use same pattern as for template scripts: list of
>>               loaders (webapp, workspace, jar)
>>             * support binaries
>>             * far future caching
>>             * align with files in mgnl-resources
>>     * themes
>>             * better deploy process (zip upload)
>>             * configurable themes (few parameters, like color and
>>               font)
>>             * simpler base CSS (separate functional and style)
>> 
>> The focus is more on simplifying things rather than adding new
>> features, still there are some we should mention here:
>> 
>>     * ajax provide a best practice example using the new
>>       direct-paragraph-request feature
>>     * social media integration to youtube, twitter, facebook, flickr
>>     * templates redirect, structure, iframe, ...
>> 
>> And beyond: we collected ideas which will be realized while developing
>> 5.0, some of them are well known but requested so often that I still
>> mention them here:
>> 
>>     * developer mode show developer related information: script
>>       executed, direct link to script
>>             * dialog to edit paragraph definitions (show script,
>>               direct editing)
>>     * usability
>>             * show template, paragraph name in the bars or info-box
>>             * direct upload to DMS (and preview) and suppor for
>>               search in the selection dialog
>>             * execute actions as activation directly in the page
>>               view
>>             * create page -> select template -> open dialog -> save
>>               creates page
>>             * visualization in paragraph selection list
>> Cheers
>> - Philipp
>> 
>> 
>> 
>> ______________________________________________________________________
>> ----------------------------------------------------------------
>> For list details see
>> http://www.magnolia-cms.com/home/community/mailing-lists.html
>> To unsubscribe, E-mail to: <[email protected]>
>> ----------------------------------------------------------------
> 
> 
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <[email protected]>
> ----------------------------------------------------------------

Cheers
- Philipp


----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to