|
Thursday 22 April 2010 5:58:32 am
Hi, I completely agree with Piotrek when he writes: If I look at ezwebin, I see an intelligent GUI, not a skin. This interface is crucial for developers to ease the learning curve and also pick up some good practices, but with around 40 eZ Publish implementations, we haven't yet had a customer who would fit into ezwebin precisely (or sometimes - at all). and I agree with Felix too when he writes: For developers, a blank (plain) design combined with the functionality provided in webin is all that is needed. I think that the most important aspect of the themes provided by default (ezwebin an ezflow) is to provide us technical and ideas solutions that we can copy to fit them to our particular cases. Maybe, the http://www.z2us.com site can be a nice solution for people who don't have html, CSS and ez template language skills (in that case, how hard it should be to use eZ Publish !). But I don't think that it is the role of eZ to supply these themes but the job of the community instead. To finish, I don't share David's point of view when he says: Looking at different eZ-powered sites they tend to look quite the same. CSS and Image-changes of course but you can still 'feel' that it is the same base-template. eZ Publish lets us, naturally, free to create any design. Pascal
Ce qui embellit le désert c'est qu'il cache un puits... quelque part... (A. de Saint-Exupéry) - http://luxpopuli.fr/eZ-Publish
|