Documentation Center

node

This topic describes the node element.

Description

The <node> element can be used to configure a node, element or attribute in different ways, such as role, pretty name, placeholder and templates.

<x:node match="td">
  <x:role>tablecell</x:role>
  <x:name xml:lang="en">Cell</x:name>
  <x:name xml:lang="nl">Cel</x:name>
  <x:placeholder>{name}</x:placeholder>
  <x:templates>
    <x:template class="red">
      <p><?start?></p>
    </x:template>
  </x:templates>
</x:node>

Namespace

http://www.xopus.com/xmlns/config

Attributes

NameDescription and useType
matchAn element name that selects elements and/or attributes that you want to configure. The match attribute does not work like XPath in XSL. It has a few restrictions, which are detailed here.
ignoreMixed

Optional.

This attribute can be used to work around an issue that arises out of the use of block level elements, such as lists (<ol>, <ul>), tables (<table>), and paragraphs (<p>) inside mixed complexType elements (mixed="true"). See the mixed content page for more information. Setting the attribute to false can be used to override a previous setting when working with multiple configurations, or configuration that can be overridden.

Boolean
preferElementsOnlyParent

Optional.

This attribute can be used to guide Content Editor in the creation of new elements. Some schemas define mixed content elements that have the intention that the author uses either text with "inline" markup or a sequence of "block"-like elements. By setting this attribute to true on elements that should be kept out of mixed content, Content Editor will try to insert such elements in an ancestor that is not mixed (i.e. an ancestor that has an elements-only model.)

Boolean
preferText

Optional.

This attribute helps Content Editor give text content priority over element content in the node it is specified for, when that node is defined as mixed content in the schema. It's useful for actions such as toggling between paragraph(s) and lists. eg: When a listitem node has set the preferText attribute it prevents Content Editor from creating listitems with paragraphs inside when converting a paragraph to a list. More information with example on using two attributes for this desired result at this developers topic.

Boolean

Parent element

nodeconfig

Child elements and related topics