@maltjoy/mcp-server 0.3.2 → 0.5.0-beta.0

package/dist/doc/zeroheight/guidelines/1423650/content.md

@@ -0,0 +1,72 @@
+Placeholders should offer **useful and specific guidance** about the expected input. They serve as **hints** to indicate input format or suggest example content, but should not replace labels.
+
+## Placeholder general guidelines
+
+- Keep placeholder text short and concise,** ideally between 3–5 words **(more for free text).
+- Use **simple, familiar language** that is easy to understand.
+- Avoid jargon, full sentences, or overly detailed explanations.
+- Do not overload the placeholder with too much information—keep it focused and clear.
+- **Do not repeat the field label** in the placeholder. Redundancy can confuse users and reduce clarity.
+
+### Accessibility
+
+Avoid truncating placeholder content, as this can negatively impact usability.
+
+- Do: Keep the placeholder within the frame of the field.
+- Don't: Avoid unnecessary lengths.
+
+**Make sure key information to fill the field is accessible outside of the placeholder, as they disappear when users begin typing.**
+
+- Do: Leverage helper text to convey secondary information.
+- Don't: Do not include required instructions solely within the placeholder.
+
+### Types of input
+
+Adapt placeholder content based on the type of input:
+
+- For **action-based fields,** describe the expected written text using **clear and direct verbs ("Search", "Add", "Upload", etc.).**
+
+- Do: Be specific about the action to take.
+- Don't: Avoid generic placeholders.
+
+- Do: Provide additional information about the type of input.
+- Don't: Avoid vague instructions, which offer no contextual guidance.
+
+- For **guidance-based placeholders**, use **examples** (e.g., for dates, emails, phone numbers). However, examples should never replace the label.
+
+- If an example may be misinterpreted as actual input, consider placing it as **helper text below** the input field instead.
+- When using examples within a placeholder, **clearly indicate them by using “Ex:”.**
+
+- Do: Use obvious false or random inputs on top of adding "Ex:".
+- Don't: Avoid confusing the user with seemingly prefilled data.
+
+- Do: Remember to localise placeholder inputs whenever relevant.
+- Don't: Avoid using the same placeholders for all countries.
+
+#### Examples of placeholder usage
+
+| Input Type | Example Placeholder |
+| Name | "First name" |
+| Email | "e.g., [name@domain.com](mailto:name@domain.com)" |
+| Phone Number | "+1 123 456 7890" |
+| Date of Birth | "DD/MM/YYYY" |
+| Username | "Choose a username" |
+| Search Bar | "Search..." |
+## Label usage
+
+- **Always include a label** alongside your input field.
+
+- If a visual label is not present, the placeholder will temporarily act as one. In such cases, a floating or persistent label must appear when the user interacts with the field.
+
+- Do: undefined
+- Don't: undefined
+
+## Placeholder vs. helper text
+
+- **Placeholders** provide short, temporary hints **inside** the input field.
+
+✅ Example: `"e.g., +44 123 4567"`
+- **Helper Text** offers additional instructions and persists **below** the input field.
+
+✅ Example: `"Include country code for international numbers."`
+- If the guidance requires more detail, use **helper text instead of a long placeholder**.

package/dist/doc/zeroheight/guidelines/1423650/introduction.md

@@ -0,0 +1,17 @@
+## Anatomy
+
+## Size
+
+## Components
+
+### Close
+
+### Open
+
+When the dropdown is open, we display the Phone input with the **Focus** state
+
+### Elevation
+
+When the dropdown is open we apply the Medium elevation
+
+## Related

package/dist/doc/zeroheight/guidelines/1423650/meta.json

@@ -0,0 +1,17 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Input Phone",
+  "slug": "input-phone",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 1423650,
+  "pageUid": "1423650",
+  "fetchedAt": "2026-07-15T08:24:45.808Z",
+  "tabs": [
+    "Introduction",
+    "Content",
+    "Change log 🔄"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/input-phone/",
+  "extraction": "zeroheight-api"
+}

package/dist/doc/zeroheight/guidelines/1465972/code.md

@@ -0,0 +1 @@
+

package/dist/doc/zeroheight/guidelines/1465972/content.md

@@ -0,0 +1 @@
+

package/dist/doc/zeroheight/guidelines/1465972/description.md

@@ -0,0 +1 @@
+A tag is a small, labeled element used for categorizing, labeling, or organizing content with key terms or keywords.

package/dist/doc/zeroheight/guidelines/1465972/introduction.md

@@ -0,0 +1,36 @@
+## Anatomy
+
+## Size
+
+| **Size** | **Dimension** |
+| Xsmall | Height : 20px |
+| Small | Height : 24px |
+| Medium | Height : 32px |
+| Large | Height : 40px |
+### Primary
+
+### Primary with Action
+
+#### Removable (draggable)
+
+#### Clickable
+
+### Secondary
+
+### Secondary with icon
+
+#### Removable (draggable)
+
+### Empty
+
+### AI
+
+#### Primary
+
+#### Secondary
+
+### Others
+
+### Strikethrough
+
+## Related

package/dist/doc/zeroheight/guidelines/1465972/meta.json

@@ -0,0 +1,18 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Tags",
+  "slug": "tags",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 1465972,
+  "pageUid": "1465972",
+  "fetchedAt": "2026-07-15T08:24:45.902Z",
+  "tabs": [
+    "Introduction",
+    "Usage",
+    "Content",
+    "Code"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/tags/",
+  "extraction": "zeroheight-api"
+}

package/dist/doc/zeroheight/guidelines/1465972/usage.md

@@ -0,0 +1 @@
+

package/dist/doc/zeroheight/guidelines/1476144/change-log.md

@@ -0,0 +1 @@
+## Change log

package/dist/doc/zeroheight/guidelines/1476144/content.md

@@ -0,0 +1,114 @@
+## Tone and voice
+
+- **Be direct:** Minimise the friction and interruption as much as possible.
+- **Be supportive:** Even for error and warnings, stay calm and do not use alarming words.
+- **Be helpful**: If something went wrong, clearly explain what to do next.
+- **Be respectful**: Acknowledge the user's time and autonomy throughout the process.
+
+## **Dialog anatomy**
+
+A dialog typically contains:
+
+1. **Title:** What this dialog is about
+2. **Body:** Context, consequences, or input fields
+3. **Actions:** Primary and optional secondary buttons
+
+### **Title**
+
+Write titles that clearly state the purpose or action.
+
+| **✓ Do** | **✗ Do not** |
+| Delete this proposal? | Are you sure? |
+| Add payment method | Payment |
+| Send Jane a proposal | Send |
+| Withdraw application | Warning |
+**Guidelines:**
+
+- Use sentence case, start with a capital letter.
+- Lead with a verb for action dialogs (Delete, Remove, Cancel).
+- Frame confirmations as questions.
+- Keep titles under 50 characters **in all languages.**
+- Avoid generic titles like “Error” or “Confirmation”.
+- Prefer a matter-of-fact tone most of the time; do not be overly joyful or alarming.
+
+### **Body**
+
+Provide just enough context for users to make an informed decision.
+
+**Guidelines:**
+
+- Avoid adding highlights, links or tooltips within the dialog to divert the user’s attention.
+- Keep body text to 1–3 sentences when possible.
+- Avoid jargon and technical terms.
+- Use a neutral, matter-of-fact tone.
+- Address the user directly, using “you” - when relevant.
+
+#### **For confirmation dialogs:**
+
+Remind the user about the context and the action they’ve just performed. Inform them about the potential consequences of their actions. Follow up with the actions.
+
+*Example: “You are about to delete your quote for 'E-commerce Website Redesign.' This action cannot be undone, and the client will no longer see your submission.”*
+
+#### **For informational dialogs:**
+
+Clarify the context, what has led to the dialog’s display. Inform the users of the next steps.
+
+*Example: “Your identity has been verified. You can now send your quote.”*
+
+#### **For warning and error dialogs:**
+
+Be upfront about the error state - yet reassuring. Explain what is the cause of the situation and how to fix it.
+
+*Example*: “*Your profile isn’t compliant yet. Your quote was saved in the drafts. Upload your proof of identity to get compliant and send out quotes.”*
+
+### **Action buttons**
+
+**Overall guidelines:**
+
+- Never use “Yes”/”No” or “OK”/”Cancel” for destructive actions.
+- Match the button label to the dialog title when possible.
+
+**Primary action (mandatory):**
+
+- Follow the usual guidelines for buttons: “Verb + subject” structure.
+- Use a specific verb that describes the action.
+
+- Examples “Delete proposal”, “Accept quote”, “Submit application”.
+- For destructive actions, use explicit language.
+
+- Example: use “Delete”, “Remove” instead of “Ok”, “Yes”.
+
+**Secondary action (optional):**
+
+- Provide a clear way out: “Cancel”, “Go back”, “Not now”.
+- Or provide a clear alternative to the primary action.
+
+- Example: “Accept application” (primary), “Decline application” (secondary).
+- Use the same terminology as in the rest of the dialog.
+
+- Example: “Delete proposal” (primary), “Keep proposal” (secondary).
+
+### **Accessibility**
+
+**Use clear, descriptive titles**
+
+- Screen readers announce the dialog title first; make it meaningful.
+- Avoid titles that only make sense with visual context.
+
+**Write for cognitive accessibility**
+
+- Use plain language (aim for an 7th-grade reading level).
+- Break complex information into short sentences.
+- Avoid double negatives
+
+- Example: Don’t say “Do not cancel”; instead say “Keep subscription”
+
+**Do not rely on visuals alone**
+
+- Pair colour and illustrations with text labels and written content.
+- Error states should include the word “error” or describe the problem explicitly.
+
+**Provide text alternatives**
+
+- If using icons in buttons, include visible text labels.
+- Decorative images in dialogs should have empty alt text; meaningful images need descriptions.

package/dist/doc/zeroheight/guidelines/1476144/introduction.md

@@ -0,0 +1,41 @@
+## Anatomy
+
+#### Overlay Dialog
+
+#### Full Dialog
+
+### Width
+
+| **Device** | Type | **Size** | **Inside Padding** |
+| Desktop | Overlay | Default - 580pxLarge - 780px | 32px |
+| Mobile | Overlay | Fixed - *Device screen size*- 24 padding | 16px |
+| Desktop | Full Dialog | Full Screen | [Layout page](https://zeroheight.com/6bf479565/p/62355e) |
+### Height
+
+> The heigh of the dialog should wrap the content of it. This means that the heigh of the modal should adapt to the heigh of the content that there is inside of it. Nevertheless, there are some rules for them: the minimum heigh should be 200px so it is easy to notice for the user, the maximum should be 800px so it never exceeds the heigh of the screen itself.
+
+### Multiple dialogs
+
+> If there are more than one dialog in a row (series of dialog, workflow) the size of all of them should be the size of the bigger dialog
+
+### Overlay
+
+## Dialogs Examples
+
+### Desktop
+
+### Mobile
+
+## Brand dialog
+
+⚠ The brand dialog pattern is use **only** for the *brand* or *marketing* related topic
+
+## Scrolling behavior
+
+The max-height is set to 580px max. If the content is bigger than the max-height we activate the scroll behavior.
+
+### Demo
+
+## Signup & login
+
+## Related

package/dist/doc/zeroheight/guidelines/1476144/meta.json

@@ -0,0 +1,18 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Dialogs",
+  "slug": "dialogs",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 1476144,
+  "pageUid": "1476144",
+  "fetchedAt": "2026-07-15T08:24:45.734Z",
+  "tabs": [
+    "Introduction",
+    "Usage",
+    "Content",
+    "🔄 Change log"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/dialogs/",
+  "extraction": "zeroheight-api"
+}

package/dist/doc/zeroheight/guidelines/1476144/usage.md

@@ -0,0 +1,74 @@
+## Alert dialog
+
+### Width
+
+| **Device** | **Size** | **Inside Padding** |
+| Desktop | Fixed - 580px | 32px |
+| Mobile | Fixed - *Device screen size*- 24 padding | 16px |
+### Height
+
+> The heigh of the dialog should wrap the content of it. This means that the heigh of the modal should adapt to the heigh of the content that there is inside of it. Nevertheless, there are some rules for them: the minimum heigh should be 200px so it is easy to notice for the user, the maximum should be 800px so it never exceeds the heigh of the screen itself.
+
+### 
+
+### Usage
+
+An alert dialog is a type of dialog box that is used to display important information or prompt the user for a decision.
+
+#### When to use
+
+1. Confirming a user's action: An alert dialog can be used to confirm that the user really wants to perform a certain action, such as deleting a file or making a purchase.
+2. Displaying an error message: An alert dialog can be used to display an error message if something goes wrong, such as a failed login attempt or a connection error.
+3. Providing information: An alert dialog can be used to provide important information to the user, such as a warning about a potentially dangerous action or a notification about a new feature.
+4. Requesting input: An alert dialog can be used to prompt the user for input, such as their email address or a password.
+
+#### When not to use
+
+Avoid dialogs when:
+
+- **The content is informational only:** Use highlights, helper texts or tooltips instead.
+- **The content is supplementary to the main information:** Prefer helper text, tooltips, highlights or expandable sections.
+- **The task is complex or multi-step:** Redirect users to a form or funnel; dialogs should not require scrolling or contain more than 2–3 input fields.
+- **The action is easily reversible:** For low-stakes actions (ex: adding a freelancer to the favorites’ list), prefer snackbar with actions.
+
+### Overlay
+
+## Desktop
+
+Dialogs need to be displayed at the center of the screen. If the height is more than the height of the page (including a top and bottom padding of 30px), then the inside content needs to be scrollable.
+
+### Button rules
+
+The main action is defined with a Primary button.
+
+For the second action, Ghost button should be used
+
+Button is aligned on the right side of the dialogs
+
+- Do: Use primary button
+- Don't: Use secondary button
+- Don't: Buttons separeted
+
+### Button Style
+
+- Do: 
+- Do: 
+
+### Image
+
+When we display an image in the modal, the close button should appear on the right top corner
+
+- Do: 
+- Don't: 
+
+## Mobile
+
+Concerning mobile dialogs, it needs to be displayed at full width and take the entire available space. If the content exceed the maximum size, it should become scrollable.
+
+Buttons should be in a fixed position while scrolling and remains above the content. We should use a medium shadow on the buttons to make them 
stand out in front of the content. If there is only one button it should be in full width and centered.
+
+### Desktop
+
+If dialogs goes above the content on desktop, they need to have a "**large shadow**" under them. The rest of the page should be have an overlay which is composed of a "**grey five**" solid with opacity set at 15%.
+
+Dialogs needs to be displayed at the center of the screen. If the height is more than the height of the page (including a top and bottom padding of 30px), then the inside content needs to be scrollable.

package/dist/doc/zeroheight/guidelines/1526588/description.md

@@ -0,0 +1 @@
+**Layout tokens and breakpoints** are used to create a responsive and consistent grid system. They define the structural foundation of a page by establishing consistent margins, columns, and gutters for different screen sizes.

package/dist/doc/zeroheight/guidelines/1526588/grid-system.md

@@ -0,0 +1,16 @@
+## Introduction
+
+Columns: they are vertical series within the grid. Column widths change with the size of the grid.
+
+Gutters: they correspond to spaces between columns. Gutter widths are fixed within each breakpoint range.
+
+Grid margins: they are the outer margins of the grid. Margin widths are fixed within each breakpoint range.
+
+## Grid system
+
+|  | **Breakpoints** | **Number of columns** | **Gutters** | **Margins** | Container |
+| Mobile |  | 8 | 16 | 16px | Fluid |
+| Tablet |  | 12 | 24 | 32px | Fluid |
+| Desktop M |  | 16 | 32 | 32px | Fluid |
+| Desktop L |  | 16 | 32 | Fluid | 1200px |
+| Desktop XL |  | 16 | 32 | Fluid | 1200px |

package/dist/doc/zeroheight/guidelines/1526588/meta.json

@@ -0,0 +1,16 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Layout",
+  "slug": "layout",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 1526588,
+  "pageUid": "1526588",
+  "fetchedAt": "2026-07-15T08:24:45.819Z",
+  "tabs": [
+    "Overview",
+    "Grid system"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/layout/",
+  "extraction": "zeroheight-api"
+}

package/dist/doc/zeroheight/guidelines/1526588/overview.md

@@ -0,0 +1,20 @@
+![Malt layout sizes](/uploads/MBxJnGg3CvbUGfjaVCBKIA.png)
+
+## Breakpoints
+
+| **Size** | **Variables** | **Values** |
+| **Tiny Mobile (Iphone 4)** | `$bp-screen-tiny_max` | 0 to 359px |
+| **XXS Mobile** | `$bp-screen-xxs_min` | 360px |
+|  | `$bp-screen-xxs_max` | 479px |
+| **XS Mobile (Default)** | `$bp-screen-xs_min` | 480px |
+|  | `$bp-screen-xs_max` | 767px |
+| **Tablet** | `$bp-screen-sm_min` | 768px |
+|  | `$bp-screen-sm_max` | 991px |
+| **Small desktop screen** | `$bp-screen-md_min` | 992px |
+|  | `$bp-screen-md_max` | 1199px |
+| **Common desktop screen** | `$bp-screen-lg_min` | 1200px |
+|  | `$bp-screen-lg_max` | 1599px |
+| **Large desktop screen** | `$bp_screen_xlg_min` | > 1600px |
+We are using the following rules for breakpoints in order to resize the main content based on the device.
+
+359px / 479px / 767px / 991px / 1199px / 1599px

package/dist/doc/zeroheight/guidelines/2126958/joy-major-release.md

@@ -0,0 +1,50 @@
+## V5.0 (Latest Release)
+
+#### What's updated:
+
+- [VJoyCompanyAvatar] merge it into [VJoyAvatar](https://zeroheight.com/6bf479565/p/52ceb2-avatar)
+- [VJoySelectableItem] [introduce error state](https://zeroheight.com/6bf479565/p/24f9a1-selectable-item)
+- [VJoyTooltip] [set enableClickInContent true by default](https://zeroheight.com/6bf479565/p/137c09-tooltip)
+- [VJoyMenu] [add a new slot for right side icon on each item](https://zeroheight.com/6bf479565/p/955426-menu)
+
+#### What's is removed:
+
+- [VJoyButton] deprecate white and white-ai variants
+- [icons] remove waving-hand
+- [VJoySelectableItem] remove AI variant
+- [VJoyTooltip] remove "variant" property
+- [VJoyDividerCta] Delete from the lib
+
+## V4.0
+
+#### Design
+
+- UI [snackbar](https://zeroheight.com/6bf479565/p/72e810-snackbar)
+- [Two icons added](https://zeroheight.com/6bf479565/p/5932a1-iconography/b/869ef7)
+
+#### Tech
+
+- **All the informations of the v4 directy in storybook (****[https://joy.malt.tech/joy-storybook/?path=/docs/design-system-v4--docs](https://joy.malt.tech/joy-storybook/?path=/docs/design-system-v4--docs)****)**
+
+## V0.11 (Latest Release)
+
+### V0.10
+
+**Added : **
+
+- [Spacings](https://zeroheight.com/6bf479565/p/175ef4)
+- [GET STARTED DESIGN](https://zeroheight.com/6bf479565/p/28b9ba)
+- [GET STARTED DEVELOP](https://zeroheight.com/6bf479565/p/999388)
+- [Shaping System](https://zeroheight.com/6bf479565/p/43c94f/t/04fe81)
+- New grayscale - [Neutral](https://zeroheight.com/6bf479565/p/027b08/t/911e37)
+- Update Hover state - [Date pickers](https://zeroheight.com/6bf479565/p/419803)
+- Update Hover state - [Input](https://zeroheight.com/6bf479565/p/89d9e2)
+- Update Hover state - [Textarea](https://zeroheight.com/6bf479565/p/80b38d)
+- Update Hover state - [Select](https://zeroheight.com/6bf479565/p/43746a)
+- Update Hover state - [Date pickers](https://zeroheight.com/6bf479565/p/419803)
+- Update Hover state - [Unit input](https://zeroheight.com/6bf479565/p/179399)
+- Update Hover state - [Phone input ](https://zeroheight.com/6bf479565/p/76b454)
+- Missing case for [Toggles](https://zeroheight.com/6bf479565/p/67497f)
+- Icons - International [Flag](https://zeroheight.com/6bf479565/p/5932a1/t/04d186)
+
+Fixed :

package/dist/doc/zeroheight/guidelines/2126958/last-updates.md

@@ -0,0 +1,3 @@
+## Release notes
+
+## Related

package/dist/doc/zeroheight/guidelines/2126958/meta.json

@@ -0,0 +1,17 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "🆕  Release Note",
+  "slug": "release-note",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 2126958,
+  "pageUid": "2126958",
+  "fetchedAt": "2026-07-15T08:24:45.833Z",
+  "tabs": [
+    "Last updates",
+    "Joy Major Release",
+    "Zeroheight"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/release-note/",
+  "extraction": "zeroheight-api"
+}

package/dist/doc/zeroheight/guidelines/2126958/zeroheight.md

@@ -0,0 +1,9 @@
+Release log about all the updates relating to the Zeroheight Organization
+
+## V 1.00 (Latest Release)
+
+27/10/21
+
+**Added : **
+
+- Figma - [UI Kits](https://zeroheight.com/6bf479565/p/20ebf0)

package/dist/doc/zeroheight/guidelines/2147712/description.md

@@ -0,0 +1 @@
+If you are on this page, you have probably joined the design team. If so, well done and welcome

package/dist/doc/zeroheight/guidelines/2147712/introduction.md

@@ -0,0 +1,5 @@
+## On Install your tools
+
+## Best Practices
+
+## Contribution

package/dist/doc/zeroheight/guidelines/2147712/meta.json

@@ -0,0 +1,13 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "GET STARTED DESIGN ",
+  "slug": "get-started-design",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 2147712,
+  "pageUid": "2147712",
+  "fetchedAt": "2026-07-15T08:24:45.763Z",
+  "tabs": [],
+  "imagesPath": "packages/core-vue/static/zeroheight/get-started-design/",
+  "extraction": "zeroheight-api"
+}

package/dist/doc/zeroheight/guidelines/2147713/introduction.md

@@ -0,0 +1,3 @@
+## Communication
+
+## Install

package/dist/doc/zeroheight/guidelines/2147713/meta.json

@@ -0,0 +1,13 @@
+{
+  "source": "https://zeroheight.com/6bf479565/p/999388-get-started-developers",
+  "title": "GET STARTED DEVELOPERS",
+  "slug": "get-started-developers",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 2147713,
+  "pageUid": "2147713",
+  "fetchedAt": "2026-07-15T08:24:45.764Z",
+  "tabs": [],
+  "imagesPath": "packages/core-vue/static/zeroheight/get-started-developers/",
+  "extraction": "zeroheight-api"
+}

package/dist/doc/zeroheight/guidelines/2147725/figma-libraries.md

@@ -0,0 +1 @@
+## Figma libraries

package/dist/doc/zeroheight/guidelines/2147725/malt-typographies.md

@@ -0,0 +1 @@
+## Malt typographies

package/dist/doc/zeroheight/guidelines/2147725/meta.json

@@ -0,0 +1,17 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "UI Kits",
+  "slug": "ui-kits",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 2147725,
+  "pageUid": "2147725",
+  "fetchedAt": "2026-07-15T08:24:45.917Z",
+  "tabs": [
+    "Figma libraries",
+    "Malt typographies",
+    "Structure"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/ui-kits/",
+  "extraction": "zeroheight-api"
+}

package/dist/doc/zeroheight/guidelines/2147725/structure.md

@@ -0,0 +1 @@
+## Structure

package/dist/doc/zeroheight/guidelines/2147866/description.md

@@ -0,0 +1 @@
+Joy is the Malt's design system use for all the digital product and front-end project

package/dist/doc/zeroheight/guidelines/2147866/introduction.md

@@ -0,0 +1,9 @@
+![image](/uploads/0bKaL6cEekbuCsPPK2JFZw.png)
+
+## GETTING STARTED
+
+## TEMPLATE
+
+## PROJECT STATUS
+
+## BRAND IDENTITY