Warrell, Thank you for answers > > You are probably in a better position than I by starting with the project > > wizard. I have used the CMS without the project wizard or site skeleton. In > > your position I would have your web guy give you the CSS and XHTML XSL. The > > XSL should render volatile content delivered from the repository e.g. the > > navigation, editorial, article etc.
My web designers don't know to translate html/css to xhtml/xsl/css.Is there some tools that do that or,web designers need to know xsl? > > > > You could serve the XSL and CSS from the repository and both manage and > > version it there using the UI but that may be a bit much at the moment. You > > most important thing you nedd to do is create Content types with schemas > > that reflect the content structure. This allows you to create instance > > documents of those types which are readily editable via the CForms that are > > generated from the Content type definition documents. > > Bad thing is that I didn't understand the most inportant thing :-) Do you think about templates defined in types.xml? If it's that than I will read more times 03.developing templates. Where types.xml exist in repository or HippoCMS directory /coocon/types How to edit sitemenu, I upload it with webdav pilot, but get clear page when try to edit Think because it is not defined as type, only text and widget types exist. Is there sitemenu type which is universal and free to download? Regards, Denis Balog. ******************************************** Hippocms-dev: Hippo CMS development public mailinglist
