nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Aspects in Content Modelling

ashwinis

Hi,

Everywhere in the online it has been mentioned like, Aspect is the closest equivalent in the object-oriented
world is the notion of multiple inheritance.
Can anyone please explain how the multiple inheritance is supported by Aspects in content modelling with example?

Find more posts tagged with

Comments

mlagneaux

Hello,

An aspect represents a set of properties and associations that can be added to a node. Aspects can be "technical" or "functional". For example, adding "versionable" aspect on a node activates versioning on this node and provides all properties to manage versioning. That's what I call a technical aspect.
An example of "functional" aspect is "EXIF" aspect that adds metadata related to images to a node.

On a node, you can add several aspects in order to extend node metadata.