The default application is defined by the ETP package at server startup time as follows:
etp::define_application default {
index_template packages/editthispage/templates/article-index
index_content_type etp_page_revision
index_object_name "subtopic"
index_title_attr_name "Title"
index_description_attr_name "Description"
index_content_attr_name "Content"
content_template packages/editthispage/templates/article-content
content_content_type etp_page_revision
content_object_name "page"
content_title_attr_name "Title"
content_description_attr_name "Description"
content_content_attr_name "Content"
allow_subtopics t
allow_extlinks t
allow_symlinks t
auto_page_name ""
}
You may customize the default application, or create new
applications based on it, thereby changing the appearance and content of
your web pages.
Now you can change thecd /web/MYSERVER/www mkdir templates cp ../packages/editthispage/www/templates/* templates
tag at the top of article-index.adp and article-content.adp to refer to your master template. Next, create a file in the MYSERVER/tcl directory, and add the following code:
etp::modify_application default {
index_template www/templates/article-index
content_template www/templates/article-content
}
After restarting your server, every instance of ETP that's using the "default" application will be rendered using your master template.
etp_define_application
procedure. The real power of defining new applications is that you can create
templates that reference structured data that is stored for each page in
the content repository, and ETP gives you the means to edit and organize the structured data. To learn about how that works, please go on to read about Content Types.
| luke@museatech.net |