![]() ![]() CSS formatting should be kept separate from the component definitions.Will your component need CSS formatting?.HTL is designed to help ensure this happens. Logic should be kept separate from the user interface layer.Will your component require logic to select/manipulate the content?.There are several mechanisms provided by AEM to allow you to inherit and extend details from another component definition including override, overlay, and the Sling Resource Merger.There is no need to reinvent the wheel.Do you need to create your component from scratch, or can you inherit the basics from an existing component?.Details may change over time, but the specification can be updated (though changes should be documented too). A clear specification helps at all stages of development, testing and handover.What exactly do you need the new component to do?. ![]() Planningīefore starting to actually configure or code your component you should ask: This section covers key concepts and issues as an introduction to the details needed when developing your own components. This latter approach is slightly complicated by the fact that although AEM has shifted to a new standard, modern, touch-enabled UI, it continues to support the classic UI. This process involves reading the theory and looking at the wide range of component implementations in a standard AEM instance. When you start to develop new components you need to understand the basics of their structure and configuration. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |