[Feat]: How to copy or import a Query or Component from one app to another.

[Just1nWang]

Is your feature request related to a problem? Please describe.
We currently export JSON only at the app and module levels as the smallest units. Is it possible to export Queries or Components (or Component Groups) as JSON individually? This way, we could select and export Queries and Components (or Component Groups) in bulk.

Describe the solution you'd like
I hope we can support this feature, as we want to provide templates for application development Queries and Components (or Component Groups). By importing templates, we can quickly modify and build new applications. This would greatly accelerate our development efficiency and ensure that applications adhere to certain standards, without having to repeatedly modify each component's properties every time.

[Just1nWang]

Can I edit a component's properties to create a customized version of the component, and then import this customized component into the component library as a new custom component?
For example, with a button, can I modify its properties to create a "primary button," "success button," or "danger button"?
Supporting this feature would indeed maximize low-code development efficiency and ensure that applications adhere to consistent standards.

[FalkWolsky]

We think in this Issue multiple different great ideas are mentioned. But in the current way "all in one text", we may loose the focus. Could we kindly ask you to separate it into individual feature issues?

[rjamesnw]

I need this feature also. I keep wanting to move components into modules as I'm designing, and this system is making me start over from scratch every time due to lack of ability to copy and paste components between apps and modules, or even export them as JSON.

[Just1nWang]

@FalkWolsky ok, I'll split this into 2 distinct feature requests following the "Problem > Solution > Benefits" format:

---

Feature Request #1: Granular JSON Export for Individual Elements
Title: Allow Exporting Individual Queries/Components/Component Groups as JSON
Problem:
Currently developers must export entire apps/modules to share elements, forcing recipients to sort through irrelevant content when they only need specific components/queries. This creates inefficiency in template sharing and standardization efforts.

Requested Solution:
Add ability to:

1. Select multiple individual components/component groups/queries in UI
2. Export selected elements as portable JSON templates
3. Maintain all properties and configurations in exports
4. Allow imports to preserve relationships between exported elements

Benefits:

• Create focused templates for common UI patterns (e.g., auth flows, data tables)
• Faster onboarding with standardized elements
• Simplify cross-team collaboration

---

Feature Request #2: Component Variant Creation & Library Management
Title: Enable Saving Customized Components as Library Variants
Problem:
Developers currently cannot create official variants of base components (e.g., different button styles), leading to inconsistent implementations and duplicated effort when recreating similar components.

Requested Solution:

1. Allow modifying component properties/stylesheet to create variants
2. Add "Save as New Component" option in component settings
3. Store variants in organized component library with:
   • Custom naming (e.g., "Button-Primary", "Button-Danger")
   • Version history
   • Tagging system
4. Enable importing/exporting variant libraries

Benefits:

• Enforce UI consistency through approved variants
• Reduce repetitive property configuration
• Streamline design system adoption
• Facilitate sharing of component theme packs

---

This separation helps developers by:

1. Keeping scope focused for each implementation
2. Allowing independent prioritization (exporting might be simpler first step)
3. Enabling clearer progress tracking