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.
|