Enterprise Web Content Management

• Product
  • Enterprise Web Content Management
  • Platform
  • Key Features
  • Editions
• Services
  • Customer services
  • Professional services
  • Training
• Partners
  • Ecosystem
  • Implementation Partners
  • Technology partners
  • Become a partner
• Customers
  • Customer Quotes
  • Success stories
• Themes
  • Marketing & E-business
  • IT Management
  • Software Development
• About
  • The company
  • News
  • Vision & Strategy
  • Contact
  • Event Calender

Development & SDK

GX WebManager is an open product, supported not only by GX but also by an open community of developers. Enhancing and extending the product using open standards and common Java technologies is easy, even without the help of GX. Several APIs are available for developing new features.

Presentation API

This API allows you to build and maintain a new website presentation. With this API, the new presentation can be added and/or deleted live as a whole.

Media Item API

The GX WebManager Media Repository is a central storage for different media formats (images, articles, downloads, Flash files, multimedia objects, and web pages). The media item and its meta data are directly maintained in the Media Repository. The Media Item API allows you to define new types for the Media Repository. In most cases, the new type will be based on a standard Media Repository format with added entry options for additional specific (meta) data.

Panel API

A GX WebManager operating panel allows editors and website administrators to maintain and/or configure new GX WebManager features. The Panel API allows a developer to develop a control panel as an integrated component and add it to the environment. It offers organizations a wide variety of functional options to expand GX WebManager so they can respond to specific website needs and demands. For example, you can configure external application connections, generate reports about specific website activity and centrally maintain settings and element content that can be added locally.

Caching (Reverse Proxy)

This functionality is particularly relevant for frequently visited or highly interactive websites. Websites using a Content Management System CMS generate pages dynamically. With the Caching module, a reverse proxy is used to deliver the Website content. Caching has the advantage of precluding the need to re-generate pages or parts of pages that don’t change frequently. The server load is thereby decreased considerably, reducing (hardware) costs while at the same time allowing content to be delivered quickly to the visitors, even if it is personalized content. GX WebManager provides an intelligent granular delivery layer that caches when possible but delivers dynamically when needed.

Queries

Through the use of queries it is possible to display data from a database on a page. A query is a (parameterized) search question posed to a database in a uniquely defined language (SQL or Structured Query Language). The result can then be shown on the website. In GX WebManager, queries are maintained centrally and can be requested with a query element or from a database page.

Best combined with: External Databases

Element API

GX WebManager comes standard with a large set of functionality which provides an editor with a wide variety of content element options. Content elements are used to fill a page with content such as images, lists and overviews, download, Flash objects, and FAQs. Sometimes a new content element type is needed because of new trends and/or customer-specific needs and demands. The Element API allows a developer to develop a new content element and add it to the platform. This resulting WCB gives an editor the option of adding the desired content to a website.

Service API

A service component offers functionality for supporting other components and is not be visible in the
GX WebManager editorial environment. A service component can, for example, support the access of stored data and/or a connection to an external application for a new module. The service component is the only component that has direct access to the data storage or the external application. Other components, such as a panel or an element, gain access through the service. With the Service API, a service component can be developed and added live.

Form API

GX WebManager offers a powerful forms module for setting up advanced form flows. In a form flow, actions can be taken based on the data entered. Checks can be performed (validators), data can be saved (handlers), and form flow routings can be executed (routers). With the Form API, a form component can be developed. In the form component, one of the three aforementioned actions can be implemented. Once a WCB with a form component is activated, the forms module will be enriched with the new validator, handler, and/or router. The Form API is an extension of the Advanced Forms module.

Extend content API

The content Application Programming Interface (API) provides read and write access to a large number of operations on WebManager content. The basic content API will be extended with more functions to create and update content such as pages, articles and elements from WCBs and form handlers. This results in more ways to benefit from Web 2.0 functionality such as tagging/tag clouds, discussions and user ratings. Creating automatic content and feed imports will be easier and can benefit from more features.

Personalization API

With the personalization Application Programming Interface (API) it is possible to use the extensive personalization features of GX WebManager in self-developed components (WCB’s) and in the presentation templates. This creates more ways to work with personalization and exciting new ways to implement features like behavioral targeting.