Forums / General / New projects based on web interface or not?

New projects based on web interface or not?

Next topic

Author	Message
Wei Dai	Friday 04 December 2009 2:16:32 am Hi, I want to start a poll to see how many you guys usually start a new project by customizing the web interface package or start from the plain site. I always start from the plain site. Will it going to be more complex by customizing the web interface? Certified eZ Publish 4 developer looking for develop information & collaboration.
Gaetano Giunta	Friday 04 December 2009 3:07:23 am No! :D [edit: it will not be much more hard] I generally start from ezflow, just to make sure that all the needed classes are there (maybe the end user decides he wants frontpage-style functionality later on in the project). But then I always rewrite the pagelayout from scratch, I do not take the existing one and alter it. Since pagelayout is executed on every page view, it is important to me to have as fast as possible and also as readable/clean as it is doable. Other templates that I override, I look at the one currently in use (might be part of ezflow, ezwebin or standard designs) and make an override based on copy+change. Principal Consultant International Business Member of the Community Project Board
Carlos Revillo	Saturday 05 December 2009 4:09:45 am I'm like Gaetano with this. Always starting from ezflow and rewriting pagelayout (also css and js, btw). then copying existing files and make the necessary changes. (sometimes just easy as move one piece of code above or down)
Wei Dai	Monday 07 December 2009 7:00:15 pm Ok. I understand. Are you guys do your own html/css stuff or has another dedicate team do this? Do they always like do "skin" the eZ Publish? Certified eZ Publish 4 developer looking for develop information & collaboration.
Gaetano Giunta	Tuesday 08 December 2009 2:21:51 am Most of the time I have two separate teams: designer team doing the html/css dev team transforming that into tpl of course that varies with project size. 1+1 persons is usually good; the important part is to have the designer available for feedback from the templater, as often there will be need to fix the html/css to better suit the eZP model to have a good designer able to produce clean html/css and undertsand the specific requirements of the eZ Publish pagelayout/contentview model Principal Consultant International Business Member of the Community Project Board
Wei Dai	Wednesday 09 December 2009 12:48:19 am Thank you Gaetano Giunta . Yeah, we too have two separate teams. But, my quesions is, do the html/css team need learn specifics of eZ Publish? I think so. I mean, do you use the classes-colors.css and site-colors.css? It means, the html/css person need to study the specific output mark up by the eZP to skin it? Most of time, we don't have or have to use the "factbox" tag , or "itemized_sub_items" view. So, what is the best way to do? And what do you think about what I said in this ariticle http://readtheweb.info/2009/11/29/get-start-a-new-ez-publish-project-part-i/ (The set up : Plain site) ? And, another question hangs in my mind is that, when only use the Plain site design, if we want to do the edit templates, make the Frontend Edition available for example; is there a whole set of edit view template need re-do the html/css and re-transforming them into tpl? Do you skin the style.css in the plain site? What is your approach? Thanks Certified eZ Publish 4 developer looking for develop information & collaboration.
rek kremlin	Monday 11 January 2010 12:50:56 am I always customize the web interface package and then code this interface. How about that work? What do you think about? [url=http://www.practicebuildingcenter...ing_Chiropractic_Video_Episode58.cfm]marketing chiropractic[/url] [url=http://www.blogtalkradio.com/bencummings]chiropractic marketing[/url] [url=http://toymodeltrains-secrets.org/toy-model-trains/]Toy Model Trains[/url]