Forgot your password?
New user?
Micro Howto
Document Actions
1. Create project in OGo WebUI
Publisher has a one-to-one mapping between projects and
websites. Eg websites cannot span multiple projects, except by
using external (completely absolute) URLs.
For example we store the SKYRIX website in a project we call
"www.skyrix.com".
2. Create folders/templates/documents
The most important file in a Publisher project is the so called
"mastertemplate". It is always called Main.xtmpl and
is the place where all Publisher processing starts, that is, for each
HTML page path being exported the master template is being
triggered initially. It then can either import other templates that
work on the active content document or use the body of the
document itself.
The mastertemplate usually contains content which is applied to
any page, eg the <head> section of a document or
some common HTML header, like a company logo.
Note that templates are always looked up depending on the path
of the object being exported. That is, you can change the common
section of a website in some subfolder by placing a separate
Main.xtmpl into that subfolder.
For a small sample website: upload documents from sample to the new OGo project.
You can get a preview of the website by pressing the Publisher Preview button in the OGo WebUI project viewer.
For a more extensive examples take a look at the 'www' repository of the OpenGroupware.org cvs - it contains the complete OGo website.
