Overview
Layout component not only helps in structuring the user interface but also allows you to embed one layout within another. This feature, known as a layout within a layout, facilitates more complex and organized designs by enabling the nesting of layouts.
For example, In a application for a customer relationship management (CRM) system, you might have a main layout for displaying customer profiles. Within this main layout, you can embed additional layouts for sections like contact details, activity history, and related opportunities. By using nested layouts, you ensure that each section is well-organized and that data is dynamically passed between layouts, providing a cohesive user experience.
Basic Attributes:
Attributes are the options available for each component, allowing you to customize its appearance and functionality. They help you tailor the look and behavior of your components to fit your needs.
Attribute Name | Description |
---|---|
Layout | Here, users have the option to add a previously created layout. This feature allows you to select from layouts that have already been designed and saved, |
UI Attributes:
Attribute Name | Description |
---|---|
Padding Location | Padding Location typically refers to the configuration of spacing around elements. |
Padding Size | Padding Size refers to the amount of space added inside an element, between the element's content and its border or edge. |
Margin Location | Margin Location refers to the spacing around the outside edge of an element. |
Margin Size | Margin Size refers to the amount of space around the outside edges of an element. |
Style |
|
Classes | It is used to apply SLDS classes to component, if needed. |
Flow Type | It specifies the arrangement of content within the section, allowing users to choose between different layout flows as ‘Fit to content’ or ‘Equally distributed’. |
Show Border | It is used to simply add border surrounding the section. Note: Currently, noKodr supports only black borders. |
Visibility and Component Attribute:
Attribute Group | Attribute Name | Description |
---|---|---|
Visibility | Visibility Type | It determines whether a component is visible on the layout. It offers the following visibility types:
Reference: |
Component | Component Label | It simply shows the name of the component. |
Events
Events available for any component is of onload type.
Onload Events:
onload event occurs when the component has been loaded.
Here, only onload event actions are available for components.
Actions are basically workflow actions, which you can explore in Workflow here.
Add Comment