EVOKE can be used to create and maintain flat (i.e. non-interactive page content) websites.
Note that, in order use this facility, you must currently have low level access to the EVOKE system code, to set up a style theme for this site: this process is not covered here: it will be replaced with online style theme configuration in a later version of EVOKE
creating a site
Sites can only be created by those with page admin permission. When you have such a permit, you can add a site to any group or member home page, by using the "new site" facility on the relevant page. That site can then be edited and maintained only by that group or member.
Once created, you can return to the site page, from any page within it, via the link underneath (or beside) the page title.
Note that the site page itself cannot be published: it is simply a container for the pages that are published.
Once created, you can return to the site page, from any page within it, via the link underneath (or beside) the page title.
Note that the site page itself cannot be published: it is simply a container for the pages that are published.
adding pages
A site consists of one or more pages. When the site is created, a Home page is also created, which will be stored as index.html and thus will be the default page for that site. The name of this page may be altered, and the page may be deleted - it is just like any other page, and is added automatically for convenience only.
Further pages can be added simply by using the "new page" facility on the site page. Give the page a suitable name - preferably one word, but this is not essential - by which you want it to be referred to in the navigation menu for the site.
Further pages can be added simply by using the "new page" facility on the site page. Give the page a suitable name - preferably one word, but this is not essential - by which you want it to be referred to in the navigation menu for the site.
editing pages
Page content is created just as for articles and replies. The same formatting can be used. The main differences are that:
After previewing a page, you should use the browser's back button to return to the edit/view page.
Once a page has been published, beware of subsequently deleting images or included files, as these will immediately disappear from the live site. This is an issue that will be fixed in a later version of EVOKE.
- areas may be referenced in boxes, in place of other content
- pages are published rather than posted. Publishing creates an HTML page
- pages can be previewed, when they will be seen more or less as they will appear when published: note that certain links may not work correctly on a previewed page, and menu items will be restricted only to those pages which have already been published.
After previewing a page, you should use the browser's back button to return to the edit/view page.
Once a page has been published, beware of subsequently deleting images or included files, as these will immediately disappear from the live site. This is an issue that will be fixed in a later version of EVOKE.
areas
areas are used for content that you wish to repeat on different pages. They can be added by using the "new area" facility on the site page. They are similar to pages, in terms of content and editing.
Once an area exists, you can use it in each page you want it in, as follows: when editing any box on the page other than the first box, you will see an area button. Use this to select the area, and press save. The contents of the area will then replace the contents of that box on the page.
Once an area exists, you can use it in each page you want it in, as follows: when editing any box on the page other than the first box, you will see an area button. Use this to select the area, and press save. The contents of the area will then replace the contents of that box on the page.
site preferences
The site page has the following preferences which can be viewed and edited on the preferences tab:
- page titles?: when checked, published pages will show the page titles you have assigned to them. When unchecked, published pages will not show the page titles.
- publishing filepath: this is the filepath on the server where the site is to be published - this must tie in with the webserver home page setup for the domain which you wish to access the site with (this setting is outwith the EVOKE system). A filepath of "~" means use the default home page specified in the underlying configuration of the EVOKE system (in the pubish_filepath setting}. To publish to the htdocs folder of the EVOKE domain (i.e. where the site you are creating is to be the front end for the EVOKE system you are creating that site with), this can be set to ../htdocs/ for a standalone app, or ../<appname>/htdocs for a multiserver app.
- thumbnail size: this is the default used for image thumbnails subsequently-added to that site
page preferences
Each page has the following preferences which can be viewed and edited on the preferences tab.
- file name: this is the name the page will be published under. If no name is given, this will be defaulted to <page title>.html when you first publish the page (any spaces will be replaced by underscores). Normally, no name need be given. The exception is the home page of the site where this should be set to index.html: this is done for you by default when a new site is created.
- in menu: when checked, the title you have given this page will be included in the page navigation menu (note that this will only work if the style theme for this site uses this standard menu data). When unchecked, this page will be excluded from the menu.
publishing pages
When creating a page, you should use the preview button to see what it will look like when published: then use the browser's back button to return to the edit/view page. This preview process will also show up any problems with the style theme being used.
When you are happy with the page, you can publish it. This will create the HTML file on the server, which can then be viewed via the appropriate URL. Note that the file name used can be seen in the file name page preference.
Once a page is published, if its' in menu preference is checked, it will be added to the navigation menu for the site (assuming that the style theme uses this data).
Once all pages for the site have been published individually, the whole site should be re-published using the publish all button on the site page. This will ensure that every HTML page has the correct entries in its' navigation menu.
When any subsequent changes are made to pages, they need not be published individually: simply make all changes required to all pages (checking previews as you go), then use the publish all button on the site page.
When you are happy with the page, you can publish it. This will create the HTML file on the server, which can then be viewed via the appropriate URL. Note that the file name used can be seen in the file name page preference.
Once a page is published, if its' in menu preference is checked, it will be added to the navigation menu for the site (assuming that the style theme uses this data).
Once all pages for the site have been published individually, the whole site should be re-published using the publish all button on the site page. This will ensure that every HTML page has the correct entries in its' navigation menu.
When any subsequent changes are made to pages, they need not be published individually: simply make all changes required to all pages (checking previews as you go), then use the publish all button on the site page.