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.