St�phane, First, thank you for your response.
> First of all are we speaking about some limited structured > content (e.g. > some XML newsfeed) or some unstructured content which mixes content, > layout, files, etc.. for hundreds of different pages (e.g. > usually HTML web > sites)? Yes, it's only unstructured content as a classic static web site including HTML pages, style sheets, images and documents (word, pdf and xls). No dynamique page, that's why we would like to import it into a CMS. > The latter is far more complex as you will need to go from some > unstructured content to some structured one. > Of course you may basically just import your raw HTML files > inside some > basic Jahia HTML template (e.g. you just extract or recreate > the sitemap in > Jahia, remove the navigation from your HTML files (with some > kind of PERL > scripts) and finally import this files as HTML files in Jahia and > automatically map them to some kind of basic template with > just one large > unstructured HTML area in the central column. Then the > editors may just > call a WYSIWYG HTML editor in order to edit their text. Of > course you will > also have to clean up the HTML with some tools such as Tidy - > http://tidy.sourceforge.net/ - in order to be sure that the > fragment of > imported HTML will not "break" the full page in which it will > be included). > I must say that I am not convinced at all by this solution as > this just > looks like a kind of FTP access to some HTML files. You loose all the > advantages of moving from an unstructured to a structured > content repository. May you tell me more about this solution : I guess we will have to rename the links, change the images, the layout, add the access rights. What else and how ? This solution sounds good to me because it's only for the startup at the first time. Then, the content will evolve and those pages will become outdated. But we need to let the users to modify them at the beginning. Thank you, Olivier.
