|
Wednesday 24 June 2009 1:47:36 am
From my experience i came to conclusion that is better to start with a plain site except for very small pages that have to be done quickly and won't require further development. For all bigger project is definitely better to "start from scratch" make your own classes and write your templates that suit your needs. There are some templates that can be used from default eZ installation (like templates for rendering OE fields and tags), but they are all available when you use the plain site. Also when you work with eZ publish for a long time it's useful to have a set of your own templates for some common functionality that can be reused on many sites. Some reasons why is better to "start from scratch": 1) you have your own code for which you know how it works (rewriting other people's code can give you a lot of headache) 2) the templates will be organized in a way that you want so it will be more easy for you to work with them 3) if you are working in a team with a frontend developer which makes HTML/CSS it is better that the frontend developer gives you his HTML/CSS and then you intergrate eZ functionality into it. Of course, the frontend developer must be familiar with eZ concepts 4) the templates that come with eZ are not always up to date with the newest eZ version so you could find some obsolete pieces of code in it (like {section} instead of {if} and {foreach})
--
Nothing is impossible. Not if you can imagine it!
Hubert Farnsworth
|