Congratulations Denis, 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.
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. You could just manage your content with the Text content type as raw HTML but that might undermine the power of the CMS. Hope that helps a bit. On 23/02/2008, Denis Balog <[EMAIL PROTECTED]> wrote: > > Warrel, Ard > > thanks to both of you, > > I read all documentation on Hippo site and i'm familiar with cocoon > (not as you of course, but understand principle and xsl > transformations). > > As every beginner at something new i'm just a little confused and > can't see some points you see clearly. > > And some qustions :-) > > 1) Do you make new hippo sites with cocoon project wizard? > > 2) I can't install project wizard, command "maven clean cocoon:deploy" > get failed 301 status > I went to ibilio and there is no hippo-cocoon directory under maven, i > have installed all before it (svn maven cocoon plugin hippo repo hippo > cms etc). > > 3) Would you explain me, in short, process for site creation. I have > Photoshop pages from designer, than i give it to web designer to > translate it to HTML/CSS with correct div tags. AND what then.Just > short,not full explanation, i'll read everything twice to solve it. > > > Thanks in advance, > > Denis Balog. > > > > > > On Fri, Feb 22, 2008 at 11:25 AM, Ard Schrijvers <[EMAIL PROTECTED]> > wrote: > > Warrel, > > > > thanks a lot for your comprehensive elucidation, I couldn't have done > it > > better :-) > > > > @Denis, excuses that nobody yet reacted from Hippo. We always strive to > > help out everybody as quick as possible, but with some persons on > > holiday ( I am also leaving in 2 hours for holiday) and some others > > occupied in stringent projects. > > > > As Warrel indicates, we do have to make our money somewhere, but this > > does not imply however that we only help paying Hippo CMS users. Not at > > all. Being open source, also implies helping out people getting started > > with our software. When you are really satisfied, or you have large > > customers wanting a possible 'backup team' you may choose to have a > > support contract. You'll get extra garantuees with help and Hippo > > persons helping the solve the issues. > > > > But, for just general questions on how to use our software, you are > > always free to ask on this list! Actually, we encourage people to make > > use of this list. > > > > So, I'll be back in one week, I can (if Warrel did not explain > > everything already :-) ) then help you out with some bits and bytes if > > you like, > > > > Regards Ard > > > > > > > > > > > > Hi Denis, > > > > > > Speaking as someone from a strong Cocoon background who has > > > adopted HippoCMS I would have to say that there is plenty of > > > material out there and a very helpful community within and > > > outside of Hippo (the company). However, they have to make > > > their money somewhere and what you seek is probably met under > > > the terms of their supported offering. Having said that, you > > > can take a look at the site skeleton, the Community Apps and > > > the other documentation on the Wiki site and you should be > > > able to make reasonable progress. > > > > > > What I have done is use the CMS to manage the core content, > > > the XSLT and the CSS for a few bespoke content types. These > > > are the served from the WebDAV repository through a vanilla > > > Cocoon distribution (with a couple of added Hippo > > > components). I use this to test the site then I 'bake' the > > > whole site using the Cocoon CLI and serve it up statically. > > > It helps to be familiar with CForms to be able to put make > > > your custom content types. > > > > > > If you do turn up what you are asking about do let me know! > > > > > > Please feel free to ask the most stupid questions and even Skype me > as > > > warrell1 to chat about the basics. > > > > > > Regards, > > > > > > Warrell > > > > > > On 21/02/2008, Denis Balog <[EMAIL PROTECTED]> wrote: > > > > > > > > Hi all, > > > > > > > > this is my first post to this mailing list and I'm also new > > > at HippoCMS. > > > > > > > > I have some questions to you. > > > > > > > > 1) If i want to migrate to hippoCMS site which is based on php/asp > > > > with similar layout, i can use css which exist , is there any tool > > > > that can help me to make sitemap or templates or anything. > > > > > > > > 2) Is there any site example for download that is made in hippocms > > > > that is fairly complicated, not too much, not commercial > > > based, which > > > > I can test and learn from on my local PC. > > > > > > > > Thanks in advance > > > > > > > > Denis. > > > > ******************************************** > > > > 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 > ******************************************** Hippocms-dev: Hippo CMS development public mailinglist
