Search the documentation
 Show GitHub edit links  Hide GitHub edit links
Documented since: 9.0 Latest revision for: 9.0 Valid for OpenCms: 10.5.3

How a content of a type behaves is highly configurable with respect to various facets. In the content type definition (the XSD) you can configure

  • default values of elements,
  • mappings from elements to properties or attributes,
  • the layout of the content editor for an element,
  • the allowed values for an element,
  • relations between elements on deletion,
  • the visibility of elements in the content editor,
  • how contents are treated by the search engine
  • localized element names and default values,
  • dependencies between values of different elements,
  • ...

We survey the various configuration options that are handled in depth in separate topics.

Many of the configurations are only available in the schema for the root content, but not in schemas defining nested contents.
Various ways to change the content editors behavior
  • Each value has a comfortable way to specify it. Say "true" by clicking a checkbox, refer to an image by chosing it from a gallery and so on. Widgets provide various ways to enter a value. Check out which widgets are available, how to configure them for your content type and how to write your own widgets.

  • Not everyone should edit everything - learn how to hide editor fields in the content editors.

  • Large content? - Display the editor fields grouped in tabs!

  • The value entered in one editor field should influence the value of another field? No problem - make the fields dependent.

  • The values of content elements can differ for different languages by default. But you can force the same value for each language. Here you learn how.

  • You can adjust how contents of a type are indexed. If they should be found by themselves, only on a container page or not at all. You can configure which fields should not be indexed and also specify additional index fields.

You can improve this page

Please contribute your suggestions or comments regarding this topic on our wiki. For support questions, please use the OpenCms mailing list or go for professional support.