If not, they should be applied via the default modifier, such as. cmp-teaser as the default style’s CSS classes, since all variations should implicitly inherit them, assuming BEM-like conventions are followed. If the default style rules apply more often than not to all variation, it is best to use. cmp-teaser (without any modifiers) or on a. The default style is often the most commonly used style of the component, and the default, un-styled view of the teaser when added to a page.ĭepending on the commonality of the default style, the CSS may be applied directly on the.
![violated heroine translation progress violated heroine translation progress](https://attachments.f95zone.to/2019/12/491791_trl.png)
Note the Style Grpi names, as well as the Style names, are all exposed to the author. The image below displays the Style menu authors interact with to select the appropriate styles for the component. The Style Group names and the number of Style Groups should be tailored to the component use case and project-specific component styling conventions.įor example, the Display style group name could have been named Colors.
The Style Group names, Layout, and Display, by happenstance match to the general concepts of Display styles and Layout styles used to conceptually categorize types of styles in this article. The following image shows the Styles configuration for the Teaser component for the variations discussed in the use case. This will explore how Style names (exposed to authors) and how the backing CSS classes are organized. The following is an example use case of styling a Teaser component to have several different Layout an Display styles. The Teaser component as an example use case cmp-component-secondary-color, and the Style names. If the company’s brand color change in the future, all that needs to be changed is the single implementations of. cmp-component-primary-color, and Yellow to. cmp-component-secondary-color to define the actual style implementation in CSS. The AEM Style System can expose these coloring Display styles using author-friendly labels Green and Yellow, while allowing the CSS developers to use semantic naming of. For example:Ī component must have the options to be colored with the brand’s primary and secondary colors, however, the AEM authors know the colors as green and yellow, rather than the the design language of primary and secondary. This allows Style options to be labeled in a vocabulary clear and understood by the AEM authors, but lets CSS developers name the CSS classes in a future-proof, semantic manner. Style names, or the options presented to AEM authors, and the implementing CSS class names are decoupled in AEM. Too many options can also confuse authors as it may become unclear which option or combination is required to produce the desired effect.
#VIOLATED HEROINE TRANSLATION PROGRESS HOW TO#
Please review the content at Understanding how to code for the Style System, to ensure an understanding of the BEM-like conventions used by AEM Style System.