webphlex isn't a server-side application producing web pages 'on the fly'. It is used off-line to produce 'static' web pages which are then uploaded to the server. This has its advantages and disadvantages. Although a site generated by webphlex can include portals to server-side applications such as Dynamic Customer Self Service, forums and E-commerce transactions, it cannot provide these services itself. If you need to generate pages which change more than, say, a few times a day, this probably isn't the best product for you.

webphlex isn't a WYSIWYG editor and doesn't attempt to reproduce or predict what generated files will look like in any particular browser. It does, however, contain extensive facilities for previewing files (or parts of files) in a real browser.

webphlex doesn't actually write any code (i.e. it doesn't write its own HTML or Javascript statements*). It just replaces the codes in the (user-designed) templates with actual data (provided by the user). The user remains totally in control of, and responsible for, the final result.

webphlex doesn't generate images, e.g. it won't itself produce thumbnails from large images. There are many good products available for this purpose.

webphlex doesn't transfer generated files to a web site; these must be uploaded by the user with an external FTP client. Future releases may be capable of uploading files.

* There are some minor exceptions to this rule, e.g. the optional replacement code parameters HTML and LINK.

see also:

static versus dynamic site generation parameter HTML parameter LINK