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

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

@@ -0,0 +1,17 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Bottom Sheet",
+  "slug": "bottom-sheet",
+  "category": "components",
+  "component": "VJoyBottomSheet",
+  "pageId": 2564356,
+  "pageUid": "2564356",
+  "fetchedAt": "2026-07-15T08:24:45.705Z",
+  "tabs": [
+    "Introduction",
+    "Usage",
+    "Code"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/bottom-sheet/",
+  "extraction": "zeroheight-api"
+}

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

@@ -0,0 +1,14 @@
+## Occurrences
+
+| Composent | Size | Product | Page |
+| Header |  | Transversal | Transversal |
+| Profil Cards |  | Freelance | Search |
+## Title
+
+- Do: null
+- Don't: null
+
+## Title
+
+- Do: null
+- Don't: null

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

@@ -0,0 +1,114 @@
+## Information architecture
+
+Use this structure:
+
+- **WHAT** – What is this? What’s happening?
+- **SO WHAT** – Why should I care?
+- **WHAT NOW** – What action should I take?
+
+Apply this flow across labels, bodies, and CTAs to ensure a smooth, logical experience.
+
+- Do: WHAT: Use a clear statement to promote the new feature
+- Don't: Avoid detailling the feature's value proposition in the label
+- Do: WHAT: Use a clear statement to promote the new feature - variation with a bit more Joy.
+- Don't: Avoid detailling the feature's value proposition in the label
+
+## Content guidelines
+
+### Media
+
+**Optional**.
+
+Media should support the message, not overshadow it. Match screenshots to the content.
+
+**Format:**
+
+- Avoid iconstrations.
+- Use meaningful, relevant screenshots.
+- For video: use short clips or GIFs, no voiceover.
+
+**Localisation tip:** ⚠️ Avoid embedded text in media. If unavoidable, localise for all languages. Localise visible content, currencies, dates, and fees across all countries.
+
+### Tags
+
+**Optional**.
+
+Only use a tag on the first step; don’t repeat it.
+
+Use the pink **“New”** tag for major feature launches. Use “New” in all languages; do not localise it as “Nouveau”, “Neu”, etc.
+
+Stick to one tag whenever possible. Exceptions:
+
+- **Advanced feature**
+- **AI branding**
+
+If using the **Advanced feature**, show the tour to Starter users only if the feature supports an upsell. Include an upsell option early in the CTAs.
+
+- Do: Use the right colour code for each tag.
+- Don't: Avoid using the neutral tag for specific needs (Advanced feature, AI Search).
+
+### Label
+
+**Mandatory.**
+
+- Do: Always start with a label to emphasise the main information.
+- Don't: Be mindful of the visual hierarchy of information.
+
+- The label is your **WHAT**. It should be clear, slightly joyful at first, but never cryptic. Prioritise clarity over creativity; this is the primary piece of information users will read and remember.
+
+- Do: Write clear, straight-forward labels. Clarity is key!
+- Don't: Avoid phrases, figure of speech or humour that could be misunderstood by the users.
+
+- Try sticking to a maximum of 40 characters in English (≈50 in other languages). Always run Pseudoloc checks to ensure you won't exceed the character limitations in other languages, such as French or German.
+
+- Do: Write short, straight to the point labels.
+- Don't: Avoid adding unnecessary details in the labels. 
+
+- Avoid repetition.
+
+- Do: undefined
+- Don't: undefined
+
+### Body
+
+**Optional.**
+
+- Try not to exceed 2 to 3 lines (≈150 characters).
+- Expands on the **SO WHAT**: how this helps the user and why it matters. State the value proposition clearly. You may add a slight touch of joy to support your statement and boost conversion.
+- Avoid repetition. The body completes the label, it doesn't replicate it.
+
+### Link
+
+**Optional. Use sparingly.**
+
+- Product Tours are, by essence, very contextual. They should keep users focused. Avoid redirecting elsewhere.
+- **If necessary**, include links only to the Help Centre or FAQ, following usual guidelines.
+
+- Do: Leverage the label and body to provide users with just the necessary and relevant level of information.
+- Don't: Avoid redirecting the users to other parts of the product or website, as it will damage the feature conversion.
+
+### CTAs
+
+**Mandatory.**
+
+1. **Main**
+
+- In the first dialog, use joyful, action-driven CTAs like: “Try now”, “Show me”, “Take a look”.
+- Tailor CTAs to the feature: e.g. “Find freelancers with AI”.
+
+- Do: Add some joy and rhythm through engaging CTAs.
+- Don't: Avoid generic, neutral CTAs in the first and last steps of your product tour.
+- Do: If you're promoting an Advanced feature to a Starter user, announce clearly the need to change of service level.
+
+- In following dialogs, keep it concise, prefer “Next”.
+- The final step CTA should drive engagement with the feature.
+
+- Do: undefined
+- Don't: undefined
+
+1. **Secondary**
+
+After step one, the secondary CTA must be “Previous” or “Back”. You may also use it to link to Help or FAQs if relevant.
+
+- Do: undefined
+- Don't: undefined

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

@@ -0,0 +1 @@
+A promotional and educational component to raise awareness on a newly released feature.

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

@@ -0,0 +1,17 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Product tour",
+  "slug": "product-tour",
+  "category": "components",
+  "component": "VJoyProductTour",
+  "pageId": 2849141,
+  "pageUid": "2849141",
+  "fetchedAt": "2026-07-15T08:24:45.860Z",
+  "tabs": [
+    "Overview",
+    "Usage",
+    "Content"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/product-tour/",
+  "extraction": "zeroheight-api"
+}

package/dist/doc/zeroheight/components/2849141/overview.md

@@ -0,0 +1,19 @@
+![Product tour on side navigation](/uploads/reD9vfo_qgBVPwgTB0wbbQ.png)
+
+## Anatomy
+
+## Specifications
+
+## Type
+
+## Responsive
+
+## Components
+
+### Desktop
+
+### Mobile
+
+## Example
+
+## Related

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

@@ -0,0 +1,22 @@
+## When to use
+
+Use the Product Tour to announce important new features, only if they’re significant to the business.
+
+Trigger it automatically, centred on the screen, to highlight features that may be hard to discover.
+
+**Optionally**, follow with a series of steps to further educate the user. Each dialog appears on “Next” click.
+
+**Try not** to navigate away from the current page.
+
+Users must be able to exit the tour at any time—and ideally resume it later.
+
+Keep it short: maximum of 5 steps to avoid confusion and drop-off.
+
+Design for progressive disclosure. Plan the full narrative first, then split into clear, actionable chunks—each self-contained and meaningful.
+
+## Overlay
+
+Depending on your context you can use the product tour:
+
+- With overlay
+- Without overlay

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

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

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

@@ -0,0 +1,35 @@
+## Writing for the group as a whole
+
+- Each ButtonCard in a group must feel meaningfully distinct. If two labels could be confused or swapped, rewrite them.
+- The options should feel exhaustive: users should never feel like their situation isn't covered. If needed, include a catch-all option such as "Create" or "Other".
+- Avoid overlapping subtitles. If two cards say almost the same thing in their subtitle, the options themselves may be too similar.
+- Never write labels or subtitles that imply a hierarchy or a "right answer" unless one genuinely exists. Users should feel confident choosing the option that fits them, not the one that sounds most appealing.
+
+## Anatomy
+
+### **Group label** *(optional)*
+
+- Use when the set of ButtonCards needs a framing question or context that isn't self-evident from the cards alone. Refer to label or titles guidelines.
+- Write as a short, direct question or noun phrase. Example: "What type of account are you creating?" or "Account type", not "Please select one of the following options."
+- Use sentence case. End a question with the appropriate punctuation.
+
+### **Icon**
+
+- The icon should reinforce the label, not decorate it. If the icon doesn't add meaning, omit it.
+- Never use the icon as a substitute for a clear label.
+
+### **Label**
+
+- This is the first thing users read: make it immediately distinguishable from the other options in the group.
+- Write as a short noun phrase that names the path or option. Example: "(ProjectName)"
+- All labels in a group must follow the same grammatical structure.
+- Two to four words is the target. Do not exceed a single line.
+- Use sentence case. Do not end with punctuation.
+
+### **Subtitle**
+
+- Use to clarify or expand on the label, not to restate it.
+- Write as a short complete sentence or a tight noun phrase, depending on what the content requires. Be consistent across all cards in the group.
+- If you're using a sentence, end with a period. If you're using a noun phrase, don't.
+- Keep to one or two lines. If you need more, the option itself may need to be redesigned or split.
+- The subtitle should help users self-select. It answers "is this the right option for me?", not "what happens next."

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

@@ -0,0 +1 @@
+High-impact navigational element used at strategic intersections to branch a user's flow and reconfigure the subsequent product experience.

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

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

package/dist/doc/zeroheight/components/3079912/overview.md

@@ -0,0 +1,11 @@
+![Button card navigation example](/uploads/Jr3hpDKUmIKUiRkk7T53vQ.png)
+
+## Anatomy
+
+## Specifications
+
+## Variants
+
+## Example
+
+## Related

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

@@ -0,0 +1,16 @@
+## How to replace the selectable item component?
+
+## Usage
+
+- **Navigation vs. Data:** Use Card Buttons when the choice changes the **user's path** (e.g., choosing a profile type). Use Radio Buttons when the choice merely changes a **data attribute** (e.g., selecting a shipping method).
+- **Interaction Feedback:** The entire card surface must be interactive. To ensure discoverability, use **hover elevations** and a **prominent "Selected" state** (e.g., brand-colored border) to confirm the active path.
+- **Visual Hierarchy:** Card Buttons act as the primary focus of the page. Avoid placing competing Primary CTAs in close proximity; any "Continue" or "Next" actions should be clearly subordinated or placed below the card group.
+- **No Nested Actions:** To maintain click-target clarity, never place secondary links, tooltips, or buttons *inside* a Card Button.
+- **Mandatory Nature:** Because they define the flow's direction, Card Buttons are typically **mandatory**. A selection is required to resolve the intersection and move to the next state.
+
+## Do/don't
+
+- Do: Do use for "Branching" choices that change the layout or flow of the next steps.
+- Don't: Don't use for simple form data (like "A/B") where a Radio button is more efficient.
+- Do: Do make the entire card area clickable 
+- Don't: Don't put a "Submit" or "Continue" button inside the card itself.

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

@@ -0,0 +1 @@
+

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

@@ -0,0 +1 @@
+

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

@@ -0,0 +1 @@
+A panel is an element designed to contain page elements to a reasonable maximum width based on the size of a user's screen.

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

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

package/dist/doc/zeroheight/components/3095627/overview.md

@@ -0,0 +1,33 @@
+![Panels in project vue](/uploads/BlbEnXd-XmcdWYPwyaz_-g.png)
+
+## Anatomy
+
+## Type of panels
+
+| Name | Radius | Border | Style |
+| Main Container | 8px | Solid 1px | `$-joy-color-neutral-gray-3` |
+| Side Container | 8px | Solid 1px | `$-joy-color-neutral-gray-3` |
+| Table Container | 8px | Solid 1px | `$-joy-color-neutral-gray-3` |
+## Size of Panel
+
+| Size | Use | Label (Default size) | Padding |
+| S | Mobile | `--joy-font-size-primary-450` | 16px - `$joy-core-spacing-4` |
+| M | Tablet or unique case | `--joy-font-size-primary-650` | 24px - `$joy-core-spacing-6` |
+| L | Default | `--joy-font-size-primary-650` | 32px - `$joy-core-spacing-8` |
+## Components
+
+### Default
+
+### AI
+
+## Type of Panel
+
+### Main Container
+
+> Padding 32px
+
+### Side container
+
+> Padding 32px
+
+## Related

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

@@ -0,0 +1 @@
+

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

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

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

@@ -0,0 +1 @@
+

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

@@ -0,0 +1,3 @@
+Collapse can be used to hide and reveal information.
+
+When used correctly, they are a good way to make a higher amount of information easier to digest for the user.

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

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

package/dist/doc/zeroheight/components/4065429/overview.md

@@ -0,0 +1,34 @@
+![Collapse in the side panel](/uploads/OudAbj-NRmRdnyIxljrbCQ.png)
+
+## Anatomy
+
+### Default collapse
+
+### Outline collapse
+
+## Specifications
+
+## Type
+
+There are two type of outlines
+
+- Default
+- Outline
+
+## States
+
+We use 5 states for the collapse component; each state must convey a specific affordance.
+
+## Variants
+
+### Default
+
+### Outline
+
+## Animation
+
+| **Token** | Components | **Behavior** |
+| `$transition-duration--Default: 200ms;` | Collaps | When clicking |
+## Example
+
+## Related

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

@@ -0,0 +1,17 @@
+## Usage
+
+**Collapses are particularly useful when:**
+
+- **Content is non-essential for initial scanning:** Collapses are ideal when users need to scan high-level categories first without being overwhelmed by the specific details of every section.
+- **Vertical space is limited:** When a page contains a high volume of information (like a long FAQ or a complex settings page), collapses help reduce "scroll fatigue" by keeping the layout compact.
+- **The information is progressive:** If certain details are only relevant to a subset of users, collapses allow those users to "opt-in" to the content while keeping it hidden for everyone else.
+
+## Main rules
+
+- Do: Use clear, action-oriented headers: Ensure the title accurately describes the content hidden inside so users can decide if they need to open it.
+- Do: Group related content: Only use a Collapse when the information inside belongs together under a single, cohesive category.
+- Do: Maintain state on interaction: If a user expands a section, it should remain open until they manually close it or navigate away, unless your system specifically uses an "Accordion" style (where only one opens at a time).
+- Don't: Don't hide critical information: Never put essential instructions, primary call-to-actions (like "Buy Now"), or error messages inside a collapsed section where they might be missed.
+- Don't: Don't nest Collapses: Avoid placing a Collapse component inside another Collapse. This creates a "Russian Doll" effect that is frustrating to navigate and confusing for screen readers.
+- Don't: Don't use as a replacement for navigation: Don't use a Collapse to hide main website navigation links; use a Menu or Drawer component for that purpose.
+- Do: Don't forget the empty state: If a section has no content to display, the Collapse should either be hidden entirely or disabled to avoid leading the user into a "dead end."

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

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

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

@@ -0,0 +1,87 @@
+## Principles
+
+| Principle | Definition |
+| **Recognisable and scannable** | Users should instantly understand what the button does, even when skimming. |
+| **Mobile-first** | Ensure buttons are easily tappable, readable, and clearly labelled on small screens. |
+| **Actionable** | Use active voice and verbs to prompt interaction. |
+| **Predictable** | Clicking a button should never surprise the user. The label must reflect the outcome. |
+| **Terminology alignment** | Use consistent terms across CTAs, page titles, section headers, and labels. |
+## Structure
+
+### General rules
+
+- Keep it short, **aim for approximatively 3 words**
+- Focus on **one idea** per link
+- Avoid **punctuation**, except for question marks (if phrased as a question)
+- When linking to external websites:
+
+- Use the **site name only** (not full URL)
+- **Add an external link icon** (↗) for clarity
+
+### Links within components
+
+Embedded in a component or pattern like highlight or edit pattern.
+
+Refer directly to the specific component’s guidelines
+
+- [Highlight](https://joy.malt.com/6bf479565/p/45f5ca)
+- [Snackbar](https://joy.malt.com/6bf479565/p/72e810)
+- [Product tour](https://joy.malt.com/6bf479565/p/7589d0)
+- etc
+
+### Standalone links
+
+Used independently, often after paragraphs or in footers.
+
+- Use a short, complete phrase or sentence
+- Start with a verb when possible
+- Example:
+
+- ✅ *View freelancer portfolio*
+- ✅ *Need help choosing a freelancer?*
+
+- Do: Do apply the link to the entire sentence.
+- Don't: Avoid putting the link on a single word if it can be a standalone sentence.
+
+### Links within text
+
+Embedded in a sentence to highlight a related action or topic.
+
+- Place at the **start or end** of the sentence for readability
+
+- Do: Make sure the link is accessible and easily scannable.
+- Don't: Avoid including the link mid-sentence.
+
+- **No punctuation inside the link**
+
+- Do: Only use punctuation in standalone links with an interrogative clause.
+- Don't: Do not include punctuation in the link within a sentence.
+
+- Follow sentence capitalisation rules:
+
+- Don’t capitalize the first word unless it’s a proper noun or product/feature name
+
+- Do: Only add a capital letter at the beginning of a sentence or for a specific feature like "Malt Strategy" or "Advanced plan".
+- Don't: Avoid unconventional capitalisation.
+
+## Terminology
+
+Avoid vague or generic labels like:
+
+- “Click here”
+- “Go to”
+- “See more”
+- “Know more”
+
+Instead, **use specific and contextual language**:
+
+- ❌ *Click here to update your profile*
+- ✅ *Update your freelancer profile*
+- ❌ *Know more about our pricing plans*
+- ✅ *Compare pricing plans*
+
+## Link or button?
+
+| **Component** | **Use when the user...** |
+| **Button** | ...needs to perform an action (submit, confirm, create, start, etc.) |
+| **Link** | ...is being redirected (navigating) to another page or resource |

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

@@ -0,0 +1 @@
+Underlined piece of text that allows users to navigate from one page to another.

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

@@ -0,0 +1,13 @@
+![Link example inside a snackbar](/uploads/SCTS8uD0gTxCGHQ3tdxy2w.png)
+
+## Anatomy
+
+## States
+
+## Animation
+
+| **Token** | Components | **Behavior** |
+| `$transition-duration--Default: 200ms;` | Link | When clicking |
+## Example
+
+## Related

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

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

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

@@ -0,0 +1,30 @@
+## Definition
+
+A **link** is an underlined piece of text that allows users to navigate from one page to another, either within the same page, across the platform, or to an external site.
+
+## Usage
+
+Use links when:
+
+- Redirecting to a third-party website, platform area, or documentation
+- Supplementing the user journey with additional (non-mandatory) information or actions
+- Highlighting related content or external resources
+
+Avoid links when:
+
+- Performing primary actions (use buttons for that)
+- Creating visual emphasis only (use text styling instead)
+- The link would confuse users due to unclear or generic labels
+
+### Link button
+
+There is a **specific case** in which we can use link as button.
+
+The primary purpose of this component is to provide a visually emphasized navigation path without violating the fundamental rules of the web.
+
+We style the ***Link Button*** to adopt the visual characteristics of our lowest-emphasis button variant (often called the Text or Tertiary button) to provide a clear, clickable target with less visual weight than our Primary or Secondary actions.
+
+- Use this component when there is a small space inside which you need to perform a secondary or contextual action
+- Use this component to create visual hierarchy where the primary action is already a high-contrast button.
+
+#### Example

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

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

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

@@ -0,0 +1 @@
+

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

@@ -0,0 +1 @@
+A visual element that is added to a product, service, or user interface to indicate status, achievement, or membership.

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

@@ -0,0 +1,18 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Badge",
+  "slug": "badge",
+  "category": "components",
+  "component": "VJoyBadge",
+  "pageId": 4273331,
+  "pageUid": "4273331",
+  "fetchedAt": "2026-07-15T08:24:45.704Z",
+  "tabs": [
+    "Overview",
+    "Usage",
+    "Content",
+    "🔄 Change Log"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/badge/",
+  "extraction": "zeroheight-api"
+}