Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

...

Rate Macro

Outcome

The mindmap as created during the workshop:

Legend:

  • green might go into STK 1.5
  • red might go into STK 2.0

Overview:
Image Added

All exploded:
Image Added

Download XMind file

Summary:

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 too 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 support 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

What

The STK 2.0 kickoff workshop will be comprised of a small team of mainly developers that are experienced with STK and wish to improve it. The Goal of the workshop is to gather specific feedback, decide on features for STK 2.0 and define a roadmap as well as responsibilities for the further development (i.e. who does what). 

There is no obligation for the participants to work on the actual implementation, but the likelihood that a feature will be implemented will much increase if the person who wants it also provides it.

Agenda of the Workshop

Image Added

Feedback

  • Feedback by VPRO stk-remarks-vpro.pdf
  • Feedback by Aperto:
    • Mindmap I
      Image Added
    • Mindmap II
      Image Added

Date, Time, Location

Monday June 14 & Tuesday June 15th
St. Johanns Vorstadt 38 (new office)
9 AM - 5 PM

Dinner

We'll have a joint dinner Monday night unless we can't stand each other, in which case we will simply sit at separate tables (wink)

Participants

Rainer Blumenthal <rainer.blumenthal@aperto.de>

Rainer Blumenthal is a Technical Project Manager at Aperto AG. At Aperto he has been realizing Magnolia projects since 2007. His responsibilites include the technical coordination and conception of IT-projects for clients like Volkswagen, EADS, Frankfurt School, degewo or INSM.

Rebecca Heinen <Rebecca.Heinen@aperto.de>

Rebecca Heinen is a Frontend-Developer at Aperto AG since October 2007. Her responsibilites include conception, construction and quality assurance of html-prototypes in use with css and javascript. Her special capabilities are in the fields: web standards, accessibility, usability, SEO and mobile web.
Rebecca Heinen graduated an apprenticeship for media design (balance point design, non-print) with Vipex GmbH in Cologne. Furthermore she finished a study for multimedia producing at SAE College in Cologne.

Ernst Bunders <E.Bunders@vpro.nl>

My name is Ernst Bunders. I have been a Java web developer for about 8 years now. I am at the VPRO for nearly three years. During that time I worked a lot with a dutch object-oriented content management system called MMBase. In many projects I participated in I did the technical design.
I started playing around with magnolia for about half a year now, Investigating and customizing Magnolia and the stk on all levels.
Apart from creating many custom paragraph- and template model classes, I developed dam integration for the simple media module (which has been accepted as a patch). Currently I am discovering the inner workings of magnolia caching and preparing some optimizations to the standard caching configuration.

Nils Breunese <N.Breunese@vpro.nl>

My name is Nils Breunese, I will be 29 years old tomorrow and I have been with VPRO since November 2008. Like all of my colleagues at VPRO we have started using Magnolia last year. Magnolia-wise I have been primarily working on building custom paragraphs and model classes and integrating with our own backend systems (mainly CouchDB at the moment).

More details about me can be found on my LinkedIn profile: http://nl.linkedin.com/in/breun

...

:= }
Note
title
Mail
from
Gerbrand
/
VPRO

Initially

we

thought

we

would

use

the

STK

to

get

us

started

and

would

write

our

own

'VPRO

Templating

Kit'

later

on.

Knowing

a

bit

more

we

think

we

can

keep

using

STK,

especially

as

we

can

help

make

it

better.

We

are

currently

discovering

how

to

override

the

template

classes

so

we

can

be

more

flexible

about

areas

etc

(this

was

the

main

worry

for

a

time).

This

seems

to

go

well

and

makes

the

use

of

STK

for

future

projects

much

more

viable.

{note} h3. Boris Kraft

Boris Kraft (Magnolia)

...

CTO

...

and

...

product

...

owner.

...

Started

...

this

...

initiative

...

together

...

with

...

Aperto

...

and

...

ensured

...

that

...

STK

...

also

...

works

...

marketing

...

wise.

...

Philipp

...

Bärfuss

...

(Magnolia)

...

Head

...

of

...

Product

...

Development.

...

Working

...

for

...

Magnolia

...

for

...

about

...

5-6

...

years

...

and

...

worked

...

out

...

the

...

main

...

backend

...

concepts

...

of

...

STK

...

1.0

...

and

...

guided

...

its

...

development.

...

He

...

would

...

like

...

to

...

streamline

...

and

...

simplify

...

STK.

...

Christian

...

Ringele

...

(Magnolia)

...

Software

...

Developer.

...

Implemented

...

the

...

bigger

...

part

...

of

...

the

...

STK

...

based

...

on

...

the

...

static

...

prototype

...

delivered

...

by

...

Aperto.

...

Grégory

...

Joseph

...

(Magnolia)

...

Magnolia

...

Developer

...

for

...

about

...

4

...

years

...

and

...

our

...

future

...

community

...

manager.

...

He

...

will

...

help

...

to

...

setup

...

the

...

future

...

collaboration

...

and

...

is

...

the

...

author

...

of

...

the

...

imaging

...

module.

...

Among

...

other

...

things

...

he

...

would

...

like

...

to

...

improve

...

the

...

integration

...

of

...

the

...

imaging

...

module

...

and

...

the

...

form

...

processing.

...

Markus

...

Erdmann

...

(esense)

...

Frontend

...

developer

...

at

...

esense

...

and

...

used

...

STK

...

to

...

develop

...

custom

...

websites.

...

He

...

will

...

provide

...

feedback

...

and

...

ideas

...

about

...

possible

...

improvements.

...

Media Catalyst

  • are not participating due to heavy project pressure