If you don't have DBPrism CMS up and running go to the install section for more information. You can start using DBPrism CMS Front End with a DBPrism CMS Web Site or with a Demo Web Site. DBPrism CMS Web site installation comes with all the XML pages of www.dbprism.com.ar web site installed. DBPrism CMS Demo web site only have some sample pages and obviusly is the best starting point for end users.

The first point to be taken into account is the concept of private and public stage areas. Content authors are allways editing his private area and will only use DBPrism CMS Front End for publishing the content on the public area.

For accessing to the private area you can use a numbers of different options, such as

• Windows Web Folders (using WebDAV Access)
• KBear ftp explorer on linux (using ftp access on port 2100)
• Editing tools with ftp or WebDAV protocols support, such as JDeveloper, XMLSpy, KWrite, and others

With any of the above options you will edit the XML Content located on the XMLDB repository /home/USERNAME/cms/[en|es] directory.

Once the content is edited you can check it using DBPrism CMS Front End, if its OK you can publish in your public area using the menu options, before doing this operation the directory of the public area must be exist, it mean that if you are trying to publish a page /docs/example/test.html, your public area must content a directory named /docs/example/, if not an error will occurs.

We have succesful tested a numbers of tools for working with DBPrism CMS. You can select the editing tool based in your skill, I am using JDeveloper for editing DBPrism's project documentation, End Users preferes the Front End wysiwyg editor, other users prefers XMLSpy editor because it can check the compliance with document-v20.xsd on the fly and it includes a syntax checker.

Also you can use OpenOffice 2.0 Writer, because the Front End application can import sxw and odt document formats, with these formats you can use all the formating styles provided by the Web styles such as bold, italic, bullets, tables and inline images and directly import the content with the Front End application

• Choose one languaje as primary languaje
• Create a layout structure first into your private area
• Create almost an index.xml page into every directory
• Run update WebDAV metadata
• Synchronize your private area to the public area
• Look for non publishid pages and publish them
• If you have a lot a pages, find non published pages at directory level, not in the root directory
• Sinchronize your secondary languaje directory structure with the public area of the primary languaje
• Create almost an index.xml page for every directory into the second languaje
• Run update WebDAV metadata into your second languaje private area
• Synchronize your second lanjuage private area to the public one
• Look for non publishid pages on the second languaje and publish them