When building sites with AEM, a practical distinction is made between authors and developers. An author’s role is to create content. A developer’s role is to add functionality. When developers build functionality into sets of components, authors can add, arrange, and configure these components with content directly onto user-facing site pages.
Multifield widgets are used to allow authors to enter a dynamic number of data points. By default, these data points are entered as simple textfield controls. How can that be changed to allow for other types of input?
One of CQ’s strongest assets is its ability to create and reuse custom components. A component’s reusability depends on how flexible and configurable it can be made. CQ is unlike other component-based frameworks like Adobe Flex because properties or options cannot be passed in in, say, places like the cq:include tag. Instead, CQ properties and options are configured on pages via dialog boxes. Here, we will discuss how to retrieve component properties set by these dialog boxes.