Crafted components

Crafted components allow you to create reusable components by encapsulating existing components along with their styles, child components, event configurations, and qodlysource references.

info

Crafted components enable you to transform any component, except the Page component, into a reusable unit.

Crafting a Component

Suppose you're striving for uniform design elements across your website, ensuring compatibility with both light and dark modes. To accomplish this:

• Element Selection: Choose the component on the canvas that you wish to transform into a crafted component.
• Save as Craft: In the Tooltip menu, select the ellipsis icon and click Save as craft.

• Name and Icon: Name your crafted component and search for the desired icon in the predefined list using the search bar.
  
  
• Add: Click the Add button to complete the process.
  

Once completed, your crafted component will be available in the Components > Crafted section. You can then drag and drop it onto the canvas as needed.

CSS Class Behavior

Local CSS Classes

When a component is styled with a local CSS class, such as styled_checkBox for the checkBox component, and you save it as a crafted component for subsequent reuse in another Page, two scenarios emerge:

• First Scenario: If the target Page lacks a local CSS class matching the one in the crafted component, the crafted component's CSS class will be added as a local CSS class within the target Page.

• Second Scenario: In the case where the target Page already has a local CSS class of the same name, incorporating the crafted component will not override the existing local CSS class. Instead, the crafted component will use the local CSS class from the target Page. Should you delete the local CSS class in the target Page and subsequently attempt to re-add the crafted component, you will observe the addition of the local CSS class, accompanied by the appropriate styles.

Here's a glimpse of how it will look and behave in action:

Shared CSS Classes

When a component is styled with a shared CSS class and you save it as a crafted component for subsequent reuse in another Page, the shared CSS class is maintained across all Pages.

Qodly Source Reference

Crafted components come with references to qodlysources, however, the actual qodlysources themselves are not bundled. This leads to two distinct scenarios:

Shared Qodly Sources

When a shared qodlysource is used within a crafted component, it retains its connection across Pages. This ensures that the shared qodlysource remains linked, regardless of the Page in which the crafted component is employed.

Page Qodly Sources

With Page qodlysources, caution is needed. Page qodlysources linked to the crafted component from the originating Page will not be automatically imported into the target Page where you aim to implement it. To ensure the intended functionality, you must manually establish these qodlysource connections in the target Page or employ the shared qodlysources.

Event Configuration

The event configuration of a crafted component remains intact upon placement onto the canvas. If the crafted component holds specific event configurations from its original Page, these configurations persist when you position the crafted component on a new canvas.


However, it's important to note that while the event configuration is preserved, adjustments might be necessary to ensure alignment with the context of the new Page.

Potential adjustments could include:

• Event Targets: Ensure that the events are targeting the correct elements in the new Page.

• Event Actions: Verify that the actions triggered by events are appropriate for the new context. For example, an action that shows a specific message might need to be updated to display a different message relevant to the new Page.

• Event Conditions: Check if any conditions tied to events still hold true in the new Page.