h1: Setting up Complete any of the following steps that you did not perform during your ewok installation and configuration. ewok's staging/publishing model lets you use dynamic component-based pages for authoring, and then publish those files to static html for presentation (for performance). First, set up your staging area, then your publishing area. N. Set up your staging directory Staging directories can be located either within your document root or outside it and mapped in using aliases. - Create a new directory: $ mkdir /home/http/foo - or copy some existing content to a new tree: $ cp -rp /home/http/htdocs /home/http/foo N. Set up your publishing directory $ mkdir /home/http/foo_publish There's no need to populate this tree, as ewok will do that for you at publishing time. N. Edit Config.pm Na. Open $EWOK_HOME/conf/Config.pm for editing. Na. Update at least the variables in the section marked 'MANDATORY'. It is recommended that you update at least the following: - @EWOK\_STAGE\_DIRS - replace the placeholder '/PATH/TO/foo' with the staging directory you created above - @EWOK\_PUBL\_DIRS - replace the placeholder '/PATH/TO/publ' with the publishing directory you created above - @EWOK\_TOP\_DIRS\_ADD - if your staging directory is outside your document root replace the placeholder 'foo' with the alias name you want to use; if it is within your document root comment out or delete the 'foo' placeholder - @EWOK\_ADMINS - replace the 'johnny\_admin jane\_admin' placeholders with the usernames you wish to be ewok administrators (superusers) - $EWOK\_ADMIN\_MAILTO and $EWOK\_MAILDOMAIN - update appropriately for your domain N. Edit ewok.conf Na. Open $EWOK_HOME/conf/ewok.conf file for editing, and change the /PATH/TO/foo placeholders to the full path of your staging directory. If your directory is outside apache document root you should update the staging Alias directive appropriately (to whatever you used in @EWOK\_TOP\_DIRS\_ADD in Config.pm); if it is within the document root, comment out the Alias directive. Na. Review the Authentication Sections in the /ewok and staging directories. If you have no existing authentication mechanisms set up you will need to set up usernames and passwords in the AuthUserFile file. See "http://httpd.apache.org/docs/howto/auth.html": http://httpd.apache.org/docs/howto/auth.html for an introduction to apache authentication and access control. Of course, if you have existing authentication mechanisms in place, simply update the Authentication Sections appropriately. You may choose to perform additional configuration. Read the descriptions of each setting in the Config.pm and and ewok.conf files and customise their values for your environment. h2: Creating and managing trees=#create As your love of ewok -- and your supported user base -- expands, you will want to add additional trees. N. Simply add additional file system paths, space separated, to EWOK\_STAGE\_DIRS and EWOK\_PUBLISH\_DIRS in your Config.pm file. Obviously, you should specify a publishing directory for each staging directory you create. N. Then make the appropriate adjustments to ewok.conf, as you did when setting up your first staging and publishing trees, and you're away. h2: Hints for ewok-ing an existing site=#exist If you have an existing site, simply point ewok at it. Then you can "ewok-ise" one step at a time. You might choose to provide access only to yourself and your webmaster first, and incrementally provide access to other users as required. Each time you're making a change to your site, consider how ewok will help. Changing the navigation? Perfect time to enable the sidebar functionality and put your navigation structure in a template. Updating your contact details? Move your standard footer details out of each page and into a template file. h4: Examples The footers for the ewok documentation are generated automatically from a footer-doc.epl file in the $SITE_ROOT/templates directory (the documentation files' meta data instructs ewok to use the *doc* template). "View the footer-doc.epl file.": footer.htm Similarly, the headers are generated from header-doc.epl. "View it.": header.htm