The feeling you're left with is that it's quite hard to have an evolving
project going on with Magnolia if you want to use the last version of the
CMS.
Maybe the normal use case is to do one website and then start the next one
without sharing much with the previous one, but we tried to build a good
platform to build several websites with the same evolving template.

We started with Magnolia 4.3 to build our project, had to do a massive
migration for 4.5, and we were thinking of migrating to 5 at the end of the
year.
We were doing the "best practice" by extending the STK to our needs, and
now the STK is going away.

When you've worked for three years on a project, you want it to keep
evolving, not keep using a deprecated feature that will not be updated. And
the cost of re-starting again everything from scratch is too big to be
realistic (my boss still doesn't believe why the migrations are so hard,
explain now this).

To say the least, it's hard not to be disappointed.

2014-07-22 13:51 GMT+02:00 Nils Breunese <[email protected]>:

> Tobias Reinhardt wrote:
>
> > No, thats not a joke:
> > http://wiki.magnolia-cms.com/display/DEV/Magnolia+5.4+and+next+half+year
> >
> > I did refuse to work with the STK for years and finally concede to it a
> few month ago. Now I can throw all the effort into the bin and learn
> something new again.
> >
> > The problem is: With Magnolia I had to make the step to 4.5, then to 5,
> the STK and with 5.4 I will have to learn a new xtk.
> > As a freelancer I can not afford to learn new technologies all the time
> if I can not use this new knowledge for more than one project.
>
> The message I got at the conference, and also from the comment by Philipp
> on this wiki page, is that STK will still be available (but feature frozen
> and no longer bundled by default). If you really like STK, you can still
> start projects with it after 5.4 is released. AFAIK the reason STK is being
> deprecated is that many people feel it is forcing too many things on their
> projects and they want more freedom to use whatever frameworks, etc. they
> like.
>
> Nils.
>
> ----------------------------------------------------------------
> For list details, see
> http://www.magnolia-cms.com/community/mailing-lists.html
> Alternatively, use our forums: http://forum.magnolia-cms.com/
> To unsubscribe, E-mail to: <[email protected]>
> ----------------------------------------------------------------
>
>


-- 

Leonard Lozes
*Jefe de Proyecto*
[email protected] <[email protected]>
[image: Logo] <http://www.dome-consulting.com/>

Dome Consulting & Solutions
Tlf: *902 889 288* · Fax: *971 439 702*
www.dome-consulting.com
 Visita nuestro Blog:[image: Logo] <http://blog.dome-consulting.com/>


*Parc Bit, Parque Balear de Innovación Tecnológica, Edificio U, Local
14 Ctra. Valldemosa Km 7,4. - C.P. 07121 Palma de Mallorca - BALEARES.*

Este correo electrónico, en su caso, cualquier fichero anexo, contiene
información de carácter confidencial exclusivamente dirigida a su
destinatario. Queda prohibida su divulgación, copia o distribución a
terceros sin la previa autorización escrita de *DOME CONSULTING AND
SOLUTIONS S.L.* En caso de haber recibido este correo electrónico por
error, se ruega notifíquese inmediatamente esta circunstancia mediante
reenvío a la dirección electrónica del remitente. Al mismo tiempo *DOME
CONSULTING AND SOLUTIONS S.L.* le recuerda que sus datos forman o formarán
parte de un fichero mixto registrado  en la Agencia General de Protección
de Datos, propiedad de la empresa *DOME CONSULTING AND SOLUTIONS S.L.*y
C.I.F. *B57023533*, con domicilio arriba indicado. Usted tiene derecho de
acceso, oposición, rectificación y cancelación a estos datos que deberá
ejercer mediante escrito a la dirección: [email protected]


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

Reply via email to