A custom library provides the greatest value when you can quickly find the right appearance and apply it consistently.
What you will learn
- Organize skins by purpose.
- Apply a custom skin to another element.
- Edit details or remove a custom entry.
- Understand what happens to previously styled elements.
Build a concise visual vocabulary
Choose skin names that describe their purpose—for example, Card Soft, Header Dark, or Product Highlight. The library organizes skins by target module and category. Search and filter tools will assist you even in larger collections; as lists grow, skin cards load progressively in batches.
For a single website, a few well-named variations are usually sufficient. Dozens of nearly identical skins quickly lead to confusion regarding which one is current. When you need a minor variation in a single location, apply an existing skin and adjust the result directly in the inspector.
Reuse and maintenance workflow
- Select another compatible row, position, or module.
- Open Select skin, switch to My skins, and locate the item by name.
- Apply the skin and verify that its background, spacing, and contrast make sense in the new context.
- To edit the name or metadata of a saved entry, open its management options in the library and save the changes.
- You can delete unused custom skins. System entries cannot be deleted.
- After significant modifications, switch to a clean preview and compare all elements intended to share a unified look.
Previously styled elements remain independent
The library does not act as a centralized master stylesheet dynamically controlling all instances. Once a skin is applied, its settings become embedded directly into that specific element within the template. If you later rename or delete an entry in My skins, previously modified elements remain intact. Likewise, creating a new version of a skin will not automatically overwrite existing instances.
This behavior protects active designs: changes in the library will not break an established layout. However, it requires deliberate manual review if you intend to align older elements with a updated variant.
Recommended workflow
First perfect a single benchmark element, save its skin, and only then expand its use. For major design shifts, create a clearly named new variant, such as "Card Soft v2".
Regular library cleanup
Periodically review My skins to remove draft or duplicate entries. Before deleting an item, you can apply the skin to a temporary element to confirm whether it contains a variation you wish to retain. Deleting an item from the library is an isolated action that does not affect the content or styling of previously modified modules.
If working according to brand style guides on a project, maintain a concise list of approved skin names and purposes. This helps new team members quickly identify which appearance belongs on a standard card versus a key alert box. Although the library has a capacity limit for custom items, a smaller, well-documented set proves far more practical.