|
Product Review Site Executive 3.0 Content Management System
Site Executive 3.0 Content Management System
By: Jennifer Larkin
Apr. 3, 2003 12:00 AM
Site Executive 3.0 promises ease of use, standardization, rapid site implementation, rights- and role-based security, versioning, workflow, and easy custom module implementation. It largely succeeds in these areas. Load balancing and failover are also supported. This version does not have true localization support, but it's planned for future versions. Double-byte characters are supported. The installation process sets up the required database in your system. CFMX and the target database must be working and communicating properly and DNS must be responding. Parts of the installation process will fail if the server doesn't respond properly. Additional sites may be added within the Web application, but DNS must be handled externally.
Administration and Site Security
Content Management Interface There is no ability to paste HTML into the template builder, so the Web designer will have to re-create the templates in the administrator. Also, the body content is not surrounded by the template in the interface, requiring the user to close the editing screen to preview the content within the template. Uploading images must be done with the editor closed, so if an expected image is missing, the user must complete several steps in order to upload the image. The system allows separate stylesheets for the template and page content, encouraging standardization by limiting style differences in the page content. Only the default stylesheet can add new styles, and these cascade to other stylesheets. The stylesheet builder does not handle link styles, which are handled per template. Applied styles will not override link colors, making it virtually impossible to enable links in more than one color per template. Figure 1 shows the template builder displaying several content modules and the styles dropdown, and Figure 2 shows the page content editor with an "open and on top" module customization form.
Versioning and Workflow The approval workflow is set by the administrator and may be set per site, per directory, per page, or per template. Workflow is normally set recursively, applying site-wide workflow rules, which can be overridden per item. An unlimited number of ordered approval steps can be implemented, with final publication by the original author. The reporting tool lists what is ready for approval or publication.
Features and Modules The custom form builder allows administrators to create a wide variety of forms, the results of which can be e-mailed or exported in delimited text, Excel, or XML file formats. The exports can be downloaded by the user or processed by a custom module. Despite the Site Map and DHTML menu modules, there is no easily implemented standard sidebar menu. Lack of automatic updates in the DHTML module requires the administrator to individually add new content links. The custom module API allows structured module insertion while allowing technical users to create any CFMX-supported functionality. Custom modules are registered at startup and on demand, with functionality much like custom tags. The API allows access to existing data and modules, easily handling versioned and approved data. However, there is a learning curve for creating complex modules.
Should You Buy It?
Vitals
Specs: Pricing: Pricing per server with flexible bulk licensing. Starting price is $35,000 with average multiserver installation at $70,000. VAR programs and educational/nonprofit pricing disocounts are available.
Test Environment: Reader Feedback: Page 1 of 1
|
|||