introduction

introduction
iphlex > webphlex > documentation > introduction

how data is structured in the system
languages & multilingual text blocks
templates and text replacement
companies, users and data
translation management
lists
web generation

page groups, pages and page elements
web sites and page groups
the three types of page
language versions
navigation texts

top of page

page groups, pages and page elements
The basic unit of data is a page group. Each page group has

a location on disk where the generated output files will be placed,
default locations for images and preview images (thumbnails), and
a remote location to which the output files are intended to be uploaded.

A page group consists of pages, each with its own template containing replacement codes, and the data with which these codes will be replaced during generation. When generated, a page will produce at least one output file, e.g. a HTML or Javascript file.
A page is made up internally of one or more page elements. Whereas the pages generate output files, a page element can never in itself produce an output file, but only form part of a page.
An element can consist of a block of text, an image, a hyperlink, or any combination of these.

(image_0009)

see also:

data structure
top of page

web sites and page groups
A web site can consist of one page group, or be made up of several.
Although a 'web site' as such doesn't exist in this system, page groups which form part of the same web site can be handled as a group by putting them on a list which represents the web site. To ensure internal link consistency, the entire web site can be generated before uploading any changed files.

(image_0007)

see also:

data structure
lists
other screens: screen: lists
top of page

the three types of page
A page group can consist of three types of page:

The main page is always present, and will always produce at least one output file during generation, e.g. a file called index.html. It may, however produce more: index.html, index2.html, index3.html, etc.
Detail pages can be produced for each element. In a picture gallery, the main page(s) might contain preview images, clicking on which would call up the relevant detail page with the main image.
Extra pages can be produced for each main page, for each detail page or once for the whole page group.

the main page
The main page consists of a number of elements. Each element can be a block of text, an image, etc.
A simple picture gallery page might look like this:

(image_0001)

If there are a lot of elements, the main page might be spread out over several files. Our picture gallery might have index pages for images 1-100, 101-200, etc.:

(image_0002)

detail pages
Each element on the main page can generate a detail page. The detail page could for example contain extra text, an image, etc.
Using the picture gallery example, each preview image on the main page(s) is linked to its own detail page containing the full size picture, title, descriptive text etc.:

(image_0003)

extra pages
In many situations it can be useful to generate extra files based on the same data used to produce the main pages and detail pages. Any number of extra files can be produced for a page group. They can be generated for each main page, for each detail page, or just once for the whole page group (e.g. a HTML file containing a frameset). They can be HTML files, but also, for instance, Javascript routines which need to be different for each main page or detail page.
Continuing with the example of a photo gallery, suppose that for each detail page with the standard size photo we want another detail page with larger versions. For each main page an extra page will also be generated with preview images pointing to the large version detail files:

(image_0004)

The group might also include a frameset page for the structure, and a search page showing all picture titles in alphabetical order. These will only be generated once for the page group:

(image_0005)

see also:

data structure
data structure: how many main pages?
subscreen: web pages (extra)
top of page

language versions
Last but not least, the entire page group can be duplicated in different languages.

(image_0006)

see also:

languages
navigation: language navigation
data structure
top of page

navigation texts
In various parts of a web site it can useful to offer users an easy way of navigating between different pages. webphlex contains powerful, flexible and language-independant methods of generating such code.
This is done in one of two ways. The first method is to offer the user a menu pointing to the various target pages. This could be a complex Javascript pull-down menu or a simple collection of hypertext links - that's entirely up to the creativity of the designer.
In the second method, blocks of code are generated for the first, last, previous and/or next target pages.
The blocks of code generated can be called up using replacement codes, either as part of a page template or as data (at page or element level), as often as necessary.
These two navigation methods are used in various situations. In page navigation, the target pages in question are the various files (for pages 1, 2 ... n) generated for a main page. In element navigation, they are the elements within a page or the different detail pages produced by these elements. In site navigation, they are the various page groups above the current page group in the site hierarchy, and in language navigation, they are the different languages in which the page group is generated.
Next to the various navigation texts in the page group screen, you'll find buttons for previewing the generated output in the browser ( ) or as text ( ) .

(image_0015)

see also:

navigation
previewing generated code
top of page

iphlex > webphlex > documentation > introduction Copyright © 2006 iphlex systems

	page groups, pages and page elements The basic unit of data is a page group. Each page group has a location on disk where the generated output files will be placed, default locations for images and preview images (thumbnails), and a remote location to which the output files are intended to be uploaded. A page group consists of pages, each with its own template containing replacement codes, and the data with which these codes will be replaced during generation. When generated, a page will produce at least one output file, e.g. a HTML or Javascript file. A page is made up internally of one or more page elements. Whereas the pages generate output files, a page element can never in itself produce an output file, but only form part of a page. An element can consist of a block of text, an image, a hyperlink, or any combination of these.

	web sites and page groups A web site can consist of one page group, or be made up of several. Although a 'web site' as such doesn't exist in this system, page groups which form part of the same web site can be handled as a group by putting them on a list which represents the web site. To ensure internal link consistency, the entire web site can be generated before uploading any changed files.

	the main page The main page consists of a number of elements. Each element can be a block of text, an image, etc. A simple picture gallery page might look like this:

	If there are a lot of elements, the main page might be spread out over several files. Our picture gallery might have index pages for images 1-100, 101-200, etc.:

	detail pages Each element on the main page can generate a detail page. The detail page could for example contain extra text, an image, etc. Using the picture gallery example, each preview image on the main page(s) is linked to its own detail page containing the full size picture, title, descriptive text etc.:

	extra pages In many situations it can be useful to generate extra files based on the same data used to produce the main pages and detail pages. Any number of extra files can be produced for a page group. They can be generated for each main page, for each detail page, or just once for the whole page group (e.g. a HTML file containing a frameset). They can be HTML files, but also, for instance, Javascript routines which need to be different for each main page or detail page. Continuing with the example of a photo gallery, suppose that for each detail page with the standard size photo we want another detail page with larger versions. For each main page an extra page will also be generated with preview images pointing to the large version detail files:

	The group might also include a frameset page for the structure, and a search page showing all picture titles in alphabetical order. These will only be generated once for the page group:

	language versions Last but not least, the entire page group can be duplicated in different languages.

	navigation texts In various parts of a web site it can useful to offer users an easy way of navigating between different pages. webphlex contains powerful, flexible and language-independant methods of generating such code. This is done in one of two ways. The first method is to offer the user a menu pointing to the various target pages. This could be a complex Javascript pull-down menu or a simple collection of hypertext links - that's entirely up to the creativity of the designer. In the second method, blocks of code are generated for the first, last, previous and/or next target pages. The blocks of code generated can be called up using replacement codes, either as part of a page template or as data (at page or element level), as often as necessary. These two navigation methods are used in various situations. In page navigation, the target pages in question are the various files (for pages 1, 2 ... n) generated for a main page. In element navigation, they are the elements within a page or the different detail pages produced by these elements. In site navigation, they are the various page groups above the current page group in the site hierarchy, and in language navigation, they are the different languages in which the page group is generated. Next to the various navigation texts in the page group screen, you'll find buttons for previewing the generated output in the browser ( ) or as text ( ) .