In OpenCms contents are stored as XML files. Thus, the structure of a content of specific type, but also much of its behavior, is specified in an XML schema definition (XSD). Those XSDs themselves must comply with a special structure. ...
The XSD choice element extends the XML Schema definition. It provides a single or multiple choices of content elements in an arbitrary order. ...
One of the most important aspects of building a website is the creation of the required templates. Sites generated by OpenCms are built by using one or more templates that define a uniform layout of the content presented. ...
Content publication on websites often works with the idea of teasers and detail pages. Teasers present a content such as a news in a compact form and with a link that targets to a detail page. ...
Element settings change the formatting of a content with a formatter without changing the content or the formatter itself. ...
Element settings allow editors to change how contents are displayed. If a content is dropped directly to the page, a dialog for the element settings is available. ...
It is not necessary to configure frequently used element settings in every formatter which they are used in. Once described in one configuration file, all element settings are accessible by calling their setting names. ...
The structure of a content type and its behaviour are specified in an XSD. Field settings allow to adjust the behavior of a single editor field. ...
OpenCms has an inline editor that allows you to edit content inline without opening the form-based content editor. The inline editor has to be configured in a content's formatter to make parts of the content inline editable. ...
The task of formatters is to present contents in a nice layout and to offer layout configuration possibilities to the content editors. ...
The containers in a container page template are dynamically filled up with content. To render such content or enrich it with special JavaScript functionality, certain formatter specific CSS styles or JavaScript sources may be necessary. ...
In OpenCms content and layout are strictly separated. To render content of a special content type, several formatters can be provided. Each formatter can be configured to be used according to the container where the content is placed. ...
With the introduction of nested containers it becomes possible to build up a website from layout elements and "real" content elements, that render text or images. ...
Meta mappings allow you to export information specified in a content to any formatter of a page or the template of your site. ...
OpenCms allows you to nest containers. You can use the tag in formatter JSPs. Then content elements placed on your webpage add new containers. Here is what you should know when using nested containers. ...
OpenCms integrates a server-side image processing library that is able to apply transformations and filters to images on demand. ...
This feature allows to generate JSON output in JSPs for use by frontend applications. JSON support This following assumes that in your JSPs, you include the OpenCms tag library as follows: <%@ taglib prefix="cms" uri="http://www.opencms. ...
Besides splitting large JSP code blocks into smaller parts by means of the tag, there is the possibility of encapsulating code redundancies into custom reusable JSP tag files. ...
OpenCms comes with several Java beans to provide access to OpenCms-specific functionality in JSPs. The variable cms is present in the page scope for each JSP. It makes an object of type org.opencms.jsp.util.CmsJspStandardContextBean available. ...
OpenCms ships with its own taglib. It allows to invoke OpenCms functionality from JSPs. Whenever you write a template or a formatter, you will use tags from the OpenCms taglib. ...