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

package/dist/doc/zeroheight/components/1423608/content.md

@@ -0,0 +1,49 @@
+## Anatomy
+
+The checkbox component comes in two forms:
+
+- **Checkbox group**: a titled group of selectable items. Use when presenting multiple related options. Requires a group label.
+- **Standalone checkbox**: a single checkbox without a group. Use for consent, confirmation, or a binary on/off choice.
+
+## Checkbox group
+
+### **Group label**
+
+- Write as a short noun phrase that describes the category of options.
+- One to four words is the target.
+- Use sentence case. Do not end with punctuation — unless the label ends with a colon to introduce the list, which is acceptable.
+- Do not write the group label as an instruction or question. Write *Required documents*, not *Select the required documents*.
+
+### 
+
+### **Item labels**
+
+- Order items by relevance to the user, not alphabetically. Alphabetical order is language-dependent and breaks during the localisation process.
+- Write as a noun or short noun phrase. Do not write entire sentences. Ex: "Fully remote", "Full-time"...
+- All labels in a group must follow the same grammatical structure. Do not mix noun phrases and verb phrases.
+- Item labels are not full sentences, so do not end with punctuation.
+- Start with a capital letter.
+- Keep to a single line. If a label wraps to a second line, it's too long; you need to simplify it.
+- Avoid negations: Describe what the item is or what selecting it enables, not what it prevents.
+
+### **Error message**
+
+- Write in plain language. Say what went wrong and, where relevant, how to fix it.
+- Be specific to the group. Example: write "Select at least one document type", not "This field is required"*.*
+- Use sentence case. End with a period.
+- Do not blame the user.
+
+### **Helper text** (optional)
+
+- Use only when the group label alone isn't enough for users to make a confident choice.
+- Write in complete sentences. End with a period.
+- Add context or explain the consequence of the selection. Do not restate the group label.
+- Keep to one sentence where possible. Two at most.
+
+## Standalone checkbox
+
+- Use for consent, agreement, or a single binary choice, not as a stripped-down version of a group.
+- Write the item label as a complete, self-explanatory statement. It has no group label to provide context.
+- Use the first person for consent and agreement. Write "I agree to the terms of service", not "Agree to the terms of service".
+- End with punctuation. Ex: ✅ "I agree to the terms of service"
+- Avoid negations. If a user has to select something for nothing to happen, the framing is wrong.

package/dist/doc/zeroheight/components/1423608/description.md

@@ -0,0 +1,3 @@
+**Checkboxes** are used when there is a list of options and the user may select multiple options, including all or none.
+
+Status : **✅**

package/dist/doc/zeroheight/components/1423608/introduction.md

@@ -0,0 +1,29 @@
+![Checkbox in sign up page](/uploads/ktaeSl_4NnXOaPObb6OSKA.png)
+
+## Anatomy
+
+## Specifications
+
+## Type
+
+## States
+
+### Single
+
+#### Selected
+
+#### Unselected
+
+#### Indeterminate
+
+### Multi checkbox
+
+#### Default
+
+#### Outline
+
+### Indeterminate
+
+## Example
+
+## Related

package/dist/doc/zeroheight/components/1423608/meta.json

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

package/dist/doc/zeroheight/components/1423608/usage.md

@@ -0,0 +1,18 @@
+## How to replace the selectable item component?
+
+## Usage
+
+Checkboxes are particularly useful when:
+
+1. Multiple options can be selected: Checkboxes are ideal when multiple options can be selected, as they allow users to select multiple options in a compact and easily understandable format.
+2. The options are independent: When the options are independent and don't affect each other, checkboxes are a great choice, as they allow users to select as many or as few options as they want.
+3. The options are infrequently changed: If the options are infrequently changed, checkboxes are a good choice because they allow users to easily view and change their selections.
+4. The options are not mutually exclusive: When the options are not mutually exclusive, checkboxes are a better choice than a toggle, as they allow users to select multiple options.
+5. The options are related: If the options are related and it makes sense for them to be grouped together, checkboxes are a good way to keep them together and easily accessible.
+
+## Do/don't
+
+- Do: Do use for "Yes/No" or "On/Off" choices that are independent of other settings.
+- Don't: Don't use a checkbox if the user can only choose one option from a list (use Radio).
+- Do: Do allow users to select multiple options simultaneously from a group.
+- Don't: Don't trigger an immediate page jump or "Intersection" change upon clicking.

package/dist/doc/zeroheight/components/1423634/change-log.md

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

package/dist/doc/zeroheight/components/1423634/content.md

@@ -0,0 +1 @@
+

package/dist/doc/zeroheight/components/1423634/description.md

@@ -0,0 +1 @@
+**Toggle** is a control component that is used to quickly switch between different possible states.

package/dist/doc/zeroheight/components/1423634/introduction.md

@@ -0,0 +1,27 @@
+![Toggle in a dialog ](/uploads/ayodPOiBbV1hRubpPdf6cw.png)
+
+## Anatomy
+
+## Specifications
+
+## Type
+
+## States
+
+We use 3 states for the toggle component; each state must convey a specific affordance.
+
+### States
+
+## Variants
+
+### Selected
+
+### Unselected
+
+### Animation
+
+| **Token** | Components | **Behavior** |
+| `$transition-duration--Default: 200ms;` | Toogle | While hovering and selected |
+## Example
+
+## Related

package/dist/doc/zeroheight/components/1423634/meta.json

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

package/dist/doc/zeroheight/components/1423634/usage.md

@@ -0,0 +1,11 @@
+## Usage
+
+Toggles are particularly useful when:
+
+1. There are only two options: Toggles are best used when there are only two options, as they are simple and easy to understand.
+2. The options are mutually exclusive: When the two options are mutually exclusive, a toggle is a great way to allow users to select one option without accidentally selecting both.
+3. The options are frequently changed: If the options are frequently changed, a toggle is a good choice because it allows users to quickly and easily switch between the options.
+4. The options are related: If the two options are closely related and it makes sense for them to be grouped together, a toggle is a good way to keep them together and easily accessible.
+5. Space is limited: Toggles take up minimal screen real estate, making them a good choice when space is limited.
+
+It's important to keep in mind that while toggles are a simple and intuitive interface element, they may not be suitable for all use cases. If there are more than two options, it may be better to use a different UI element, such as a radio button or drop-down menu.

package/dist/doc/zeroheight/components/1423653/change-log.md

@@ -0,0 +1,9 @@
+### No label
+
+<textarea data-textarea-container class="m-textarea" data-js="m-textarea" name="textarea" placeholder="This is an inactive textarea placeholder">
+</textarea>### Label
+
+<div class="m-textarea" data-js="m-textarea">
+    <span class="m-textarea__label">Description</span>
+    <textarea data-textarea-container name="textarea">Very long content in this textarea</textarea>
+</div>

package/dist/doc/zeroheight/components/1423653/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/components/1423653/introduction.md

@@ -0,0 +1,45 @@
+## Component states
+
+The states of the text input component are:
+
+a) **Default**. This is the state in which the component is on display, but the user is not interacting with it. Can be empty, or complete.
+
+c) **Hover**. Mouse over interaction to display feedback that the component can be interacted with. (Only Desktop)
+
+d) **Focus**. Keyboard based interaction to display feedback that the component can be interacted with.
+
+e) **Error state**. Displaying feedback that the content of the input is not correct by means of form, and message. Can be empty error, or content error. Usually supported by a en error notification or modal alert.
+
+f) **Disabled**. The component is not enabled to be used, yet it displays content.
+
+## Anatomy
+
+![image](/uploads/6FbJ9PCE_RDU2XxH4_e3VQ.svg)
+
+## Component
+
+### States
+
+### Label
+
+It is possible to have a label at the top of the text area, and it should match the current state.
+
+### Minimum characters
+
+In case of a **minimum** character limit, the text area will display a text showing how many characters are required. When the number of minimum characters is achieved by the user, the text will fade to a lighter shade of grey.
+
+### Maximum characters
+
+The text area will display a counter that increments every time the user enter a character (20/200 for example).
+
+In the case of a **maximum** character limit, if the user goes above the limit, the counter + the input will become red.
+
+### Counter visibility
+
+If there are no maximum limit AND no minimum limit then the counter must be hidden and the text area remains without any numbers or phrase below. Otherwise, the counter should always be displayed and be incremented every time the user enter a character.
+
+## Example
+
+![image](/uploads/KUe-I0Ca77Dt-FRiSl13uA.png)
+
+## Related

package/dist/doc/zeroheight/components/1423653/meta.json

@@ -0,0 +1,17 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Textarea  ",
+  "slug": "textarea",
+  "category": "components",
+  "component": "VJoyTextarea",
+  "pageId": 1423653,
+  "pageUid": "1423653",
+  "fetchedAt": "2026-07-15T08:24:45.904Z",
+  "tabs": [
+    "Introduction",
+    "Content",
+    "Change log 🔄"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/textarea/",
+  "extraction": "zeroheight-api"
+}

package/dist/doc/zeroheight/components/1423737/change-log.md

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

package/dist/doc/zeroheight/components/1423737/description.md

@@ -0,0 +1 @@
+Status : ✅

package/dist/doc/zeroheight/components/1423737/introduction.md

@@ -0,0 +1,17 @@
+## Anatomy
+
+![image](/uploads/FBkhshInTvNjith2EWmgTw.svg)
+
+## Component
+
+### No label
+
+### Icons
+
+### [Label](https://zeroheight.com/6bf479565/p/43746a-select/t/6652be)
+
+### Avatar
+
+## Example
+
+## Related

package/dist/doc/zeroheight/components/1423737/meta.json

@@ -0,0 +1,17 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Select ",
+  "slug": "select",
+  "category": "components",
+  "component": "VJoySelect",
+  "pageId": 1423737,
+  "pageUid": "1423737",
+  "fetchedAt": "2026-07-15T08:24:45.880Z",
+  "tabs": [
+    "Introduction",
+    "Usage",
+    "Change log 🔄"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/select/",
+  "extraction": "zeroheight-api"
+}

package/dist/doc/zeroheight/components/1423737/usage.md

@@ -0,0 +1 @@
+

package/dist/doc/zeroheight/components/1465673/code.md

@@ -0,0 +1 @@
+

package/dist/doc/zeroheight/components/1465673/content.md

@@ -0,0 +1 @@
+

package/dist/doc/zeroheight/components/1465673/description.md

@@ -0,0 +1 @@
+An **icon button** is a compact, interactive element that uses an icon to perform an action

package/dist/doc/zeroheight/components/1465673/introduction.md

@@ -0,0 +1,29 @@
+![image](/uploads/hRCh8GBLHhaEg4VKeVopaA.png)
+
+## Anatomy
+
+## Type of buttons
+
+## States
+
+## Size
+
+| **Size** | **Height** |
+| LARGE | 64px |
+| MEDIUM | 48px |
+| SMALL | 42px |
+| X-SMALL | 32px |
+| XX-SMALL | 24px |
+### Main
+
+### Primary
+
+### Secondary
+
+### White
+
+### Main AI
+
+### Admin
+
+## Related

package/dist/doc/zeroheight/components/1465673/meta.json

@@ -0,0 +1,18 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Icon button ",
+  "slug": "icon-button",
+  "category": "components",
+  "component": "VJoyIconButton",
+  "pageId": 1465673,
+  "pageUid": "1465673",
+  "fetchedAt": "2026-07-15T08:24:45.785Z",
+  "tabs": [
+    "Introduction",
+    "Usage",
+    "Content",
+    "Code"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/icon-button/",
+  "extraction": "zeroheight-api"
+}

package/dist/doc/zeroheight/components/1465673/usage.md

@@ -0,0 +1 @@
+

package/dist/doc/zeroheight/components/1475881/change-log.md

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

package/dist/doc/zeroheight/components/1475881/description.md

@@ -0,0 +1 @@
+Avatar are use to display the profil picture of the user

package/dist/doc/zeroheight/components/1475881/introduction.md

@@ -0,0 +1,42 @@
+![Avatar inside a client profile](/uploads/0_egwfV6M31ymoAxdaAubA.png)
+
+## Anatomy
+
+## Type of avatars
+
+| **Variant** | **Purpose** |
+| Picture | Use for a user profile photo |
+| Initials | Use of the user's initials only (two letters made up of the first name + surname) |
+| Empty | Empty when the is not picture loaded |
+| Company logo | Company logo in plain format (without details) |
+| Generic | Generic if the company does not have an up-to-date logo |
+| Placeholder | Placeholder which indicates that the location is empty of any elements |
+## Size
+
+| **Size** | **Dimension** |
+| XLARGE | 100x100 |
+| LARGE | 80x80 |
+| MEDIUM | 60x60 |
+| SMALL | 30x30 |
+| XSMALL | 24x24 |
+## Variants
+
+### Xsmall
+
+### Small
+
+### Medium
+
+#### Empty
+
+#### Picture
+
+#### Initials
+
+#### Logo
+
+#### Add picture
+
+## Large
+
+## Related

package/dist/doc/zeroheight/components/1475881/meta.json

@@ -0,0 +1,17 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Avatar ",
+  "slug": "avatar",
+  "category": "components",
+  "component": "VJoyAvatar",
+  "pageId": 1475881,
+  "pageUid": "1475881",
+  "fetchedAt": "2026-07-15T08:24:45.702Z",
+  "tabs": [
+    "Introduction",
+    "Usage",
+    "Change log 🔄 "
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/avatar/",
+  "extraction": "zeroheight-api"
+}

package/dist/doc/zeroheight/components/1475881/usage.md

@@ -0,0 +1,7 @@
+### Avatar list
+
+### Malt Strategy
+
+#### Usage :
+
+Malt Strategy avatar is use to differentiate a Malt Strategy consultant vs a Malt freelancer classic

package/dist/doc/zeroheight/components/2271816/change-log.md

@@ -0,0 +1 @@
+## Components

package/dist/doc/zeroheight/components/2271816/introduction.md

@@ -0,0 +1,19 @@
+![Progress bar in Freelancer Project View](/uploads/jXKmr1DAG6T5c304_aafGA.png)
+
+## Anatomy
+
+## Specifications
+
+## Type
+
+## Variants
+
+### Desktop
+
+### Mobile
+
+## Example
+
+![image](/uploads/xRR2_S9PK8STUXmEjSIiZw.png)
+
+## Related

package/dist/doc/zeroheight/components/2271816/meta.json

@@ -0,0 +1,17 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Progress Bar ",
+  "slug": "progress-bar",
+  "category": "components",
+  "component": "VJoyProgressBar",
+  "pageId": 2271816,
+  "pageUid": "2271816",
+  "fetchedAt": "2026-07-15T08:24:45.865Z",
+  "tabs": [
+    "Introduction",
+    "Usage",
+    "Change log"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/progress-bar/",
+  "extraction": "zeroheight-api"
+}

package/dist/doc/zeroheight/components/2271816/usage.md

@@ -0,0 +1 @@
+

package/dist/doc/zeroheight/components/2352087/change-log.md

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

package/dist/doc/zeroheight/components/2352087/content.md

@@ -0,0 +1,82 @@
+### General guidelines
+
+Dropdowns rely on the complentarity between specific text elements to function correctly:
+
+| **Elements** | **Purpose** | **Required** |
+| Label | Identifies what the dropdown controls | Yes |
+| Placeholder | Hint at the expected selection when empty | Yes |
+| Option text | Individual choices in the list | Yes |
+| Helper text | Additional context or instructions. | Optional |
+| Error message | Explain what went wrong. | Conditional and contextual |
+#### **Labels**
+
+Labels tell users what they are selecting and must be clear, concise, and consistent.
+
+- **Capitalisation**: Use sentence case (ex: "Payment method").
+- **Length:** Keep labels short, ideally **1–3 words**.
+- **Specificity:** Be specific (e.g., use "Ticket type" instead of "Type").
+- **Consistency:** Match labels to the options inside. Mostly noun-based.
+
+Avoid:
+
+- Ending labels with colons.
+- Using title case (ex: “Payment Method”).
+- Including instructions in the label (ex: “Select your payment method”).
+- Using vague terms like “Option” or “Selection”.
+
+#### **Placeholders**
+
+Placeholders appear when no option is selected and disappear once a selection is made. They should guide selection, not replace labels.
+
+- **Capitalisation**: Use sentence case.
+- **Length**: Keep it under 30 characters
+- **Format:** Use sentence case
+- Pattern
+
+- Default: {verb + noun}. Ex: “Select country”
+- Filters: {All + noun}. Ex: “All teams”
+
+#### **Options**
+
+Options are the core content of the dropdowns. They must be scannable and predictable in their form and nature.
+
+- **Capitalisation**: Use sentence case (ex: “Legal entity 1”), unless the option is a proper noun or acronym.
+- **Length**: Use 1 to 4 words per option. Do not use article whenever possible.
+- **Consistency:** Start all options with the same part of speech (all verbs or all nouns)
+- **Specificity**: Ensure every option is distinct and unambiguous.
+
+**Ordering options:**
+
+The order of options significantly impacts usability. Choose the strategy wisely.
+
+| **Strategy** | **When to use** | **Example** |
+| Logical | For sequences involving time, size, quantity, etc. | Project status |
+| Alphabetical | For long lists with no inherent order, with no prioritisation. | Freelancer names, Countries |
+| Frequency | When specific options are selected more often than others | Most popular first |
+| Chronological | For date or time-based options | “Today”, “Last month” etc. |
+| Severity | For status and priority levels | Critical, high, medium, low |
+**Specific options:**
+
+Certains options require consistent treatment across the platform.
+
+- **“None” options**: Use when “no selection” is valid. Label as “None”, “No preference”, or even “Not applicable”. Place consistently at the top or bottom.
+- **“All” options:** Use in filters. Label as “All {items}”. Always place first in the options. Example: “All countries”.
+- **“Other” options:** Use when the user’s desired value might not be listed. Label as “Other” or “Other” + Text field. Always place last.
+- “Add new” actions (see also “Other” + Text field): Allow creation of new options, specific to this user. Start with a verb (”Add new {item}”. Place last, separate visually (divider, different font, etc.)
+
+#### **Error messages**
+
+Error messages explain why a selection is invalid or missing.
+
+- **Required field empty:** "Select a [label]" (e.g., "Select a country").
+- **Invalid selection:** "[Selection] isn't available for [context]" (e.g., "Express shipping isn't available for PO boxes").
+- **Conflict:** "Can't use [selection] with [other]" (e.g., "Can't use 'Draft' with a published date").
+
+#### **Accessibility**
+
+To ensure accessibility for all users:
+
+- Every dropdown must have a visible label programmatically associated with it.
+- Do not use placeholder text as a substitute for a label.
+- Ensure options are text-based; do not rely on colors, emojis, or icons alone to convey meaning.
+- Include units in numeric options (e.g., write "30 days" rather than just "30").