Hi Denis,

I think the other thread concerning the usage of the sitemenu content type
is probably more useful to you than my non-sitemenu approach. Indeed, I will
take a closer look at that technique and may well adapt my approach to it. I
will post some xsl here once I've absorbed the sitemenu content type.

Regards


On 25/02/2008, Denis Balog <[EMAIL PROTECTED]> wrote:
>
> Warrell,
>
> Thank you again, I really appreciate your honesty.
>
> I think I understood what you talked about xml xsl xhtml/css connections.
> I have made simple site with simple one level navigation, but with no
> header ,left right content.
> If you can post an example as you sad it will help me a lot.
> You can send me directly if it is not allowed here to put xsl code or
> whatever.
>
> Regards,
>
>
> Denis Balog.
>
>
>
> On 2/25/08, warrell harries <[EMAIL PROTECTED]> wrote:
> > Hi Denis,
> >
> >  IMHO XML content works best with XSL templates. Hippo is a CMS for
> managing
> >  XML content. Therefore, a decent site structure should decompose into
> CSS
> >  classes which define the layout and presentation style, XHTML
> encapsulated
> >  within XSL templates which map to the XML content structure and the
> 'pure'
> >  XML packaged content.
> >
> >  For example, imagine the classic web page layout of header, left
> navigation
> >  column, centre page body for editorial content, right hand column for
> >  adverts and a footer. This layout will map to CSS box layout classes
> which
> >  will each have the appropriate HTML for the site. However, the content
> of
> >  each of these XHTML elements e.g. the names of the links, where they go
> and
> >  the images etc can all be put into the Hippo XML content type that will
> be
> >  surrounded by the HTML at the render stage. This is the key point.
> Because
> >  these will be individual to you there is no one size fits all.
> >
> >  I will try to post an example here later,
> >
> >  Good luck
> >
> >
> >  On 25/02/2008, Denis Balog <[EMAIL PROTECTED]> wrote:
> >  >
> >  > 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
> >  >
> >  ********************************************
> >  Hippocms-dev: Hippo CMS development public mailinglist
> >
> ********************************************
> Hippocms-dev: Hippo CMS development public mailinglist
>
********************************************
Hippocms-dev: Hippo CMS development public mailinglist

Reply via email to