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

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

@@ -0,0 +1,12 @@
+## When To Use
+
+- When a resource needs a long time to load (big API call)
+- When the component contains lots of information, such as a List or Card.
+- Only works when loading data for the first time.
+- Could be replaced by Spin in any situation, but can provide a better user experience.
+
+Lazy loading is a technique where images or other content on a page are loaded only when they become visible to the user, rather than loading all the content at once when the page first loads. This helps to reduce the amount of data that needs to be loaded and can make the page load faster and feel more responsive.
+
+A skeleton screen, also known as a "loading placeholder", is a UI element that is displayed while the content of a page is loading. The skeleton screen typically uses shapes and patterns that simulate the layout of the content, giving the user a visual indication of what the page will look like when it's fully loaded.
+
+When used together, lazy loading and skeleton screens can provide a seamless user experience, by keeping the user engaged and informed while the content is being loaded. This can help to reduce frustration and improve the overall perception of the website or app.

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

@@ -0,0 +1 @@
+

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

@@ -0,0 +1,44 @@
+### Button label
+
+| Do | Don't |
+| Use a clear verb or noun that describes the action group | Use vague labels like "Options" or "More" without context |
+| Keep it to 1–2 words when possible | Write full sentences |
+| Match the specificity to the actions inside | Overpromise what's in the dropdown |
+**Examples:**
+
+- Do: “Share”, “Download”, “Save”
+- Don’t: “Actions”, “Click here”, “Menu”
+
+### Menu items
+
+- **Be concise.** Use 1–3 words per item.Start with the verb or key term.
+- **Be consistent.** Start each item the same way: all verbs or all nouns.
+
+- Do: “Edit”, “Copy”, “Save”
+- Don’t: “Changes”, “Make a copy”, “Saved files”
+- **Be specific.** Tell users exactly what will happen.
+
+- Do: “Export in PDF”
+- Don’t: “Export”
+- **Use sentence case.** Use sentence case, only at the first word.
+
+### Destructive actions
+
+- Place destructive actions (delete, remove, revoke) last in the list.
+- Use the usual visual treatment (red + icon) to signal.
+- Consider adding a confirmation step.
+
+### Icons
+
+- Use icons to aid scannability, not decoration.
+- Don’t mix: pair every item with an icon, use icons only or use none.
+- Ensure icons are meaningful and recognisable.
+
+### Accessibility
+
+- Avoid using too diverse icons as their meaning might differ from a person to another, and from a culture to another. Keep the usual
+
+- pen or pencil for edit pattern
+- bin for destructive actions
+- arrow down for download
+- If you are relying on icon-only, add its meaning on hover.

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

@@ -0,0 +1 @@
+A dropdown button is a trigger that reveals a list of related actions when clicked, allowing users to choose from multiple options without cluttering the interface.

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

@@ -0,0 +1,10 @@
+## Anatomy
+
+## Behaviour
+
+- Same type as the [button component](https://zeroheight.com/6bf479565/p/75500d-button) or[ icon button](https://zeroheight.com/6bf479565/p/08acf7-icon-button) component
+- Same type as for the [dropdown](https://zeroheight.com/6bf479565/p/22a9b7-dropdown)
+
+### Main
+
+## Related

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

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

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

@@ -0,0 +1,14 @@
+### When to use
+
+- **Multiple related actions on a single object.** Use when you need to group 3–7 actions that apply to the same item (ex: “Share” > “Copy link”, “Send email”, “Invite”).
+- **Secondary or infrequent actions.** Tuck away actions users need occasionally but that would clutter the interface if always visible.
+- **Space is limited.** Use to consolidate actions in toolbars, tables, or cards where horizontal space is constrained.
+- **Hierarchical action sets.** When one primary action has logical sub-options (ex: "Save" with options "Save draft," "Save and publish," "Save as template").
+
+### When not to use
+
+- **Fewer than 3 options.** Display individual buttons instead. Dropdowns add unnecessary clicks.
+- **Critical or frequent actions.** Don't hide primary actions users need constantly. Keep those visible.
+- **Instead of the navigation.** Use proper navigation components (menus, tabs, links) rather than dropdown buttons for moving between pages or sections.
+- **Form inputs.** Use a select field when users are choosing a value to submit, not triggering an action.
+- **More than 7 options.** Consider a different pattern (modal, panel, or search-enabled menu) to prevent cognitive overload.

package/dist/doc/zeroheight/guidelines/6559814/change-logs.md

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

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

@@ -0,0 +1,11 @@
+## Anatomy
+
+## States
+
+### Usage
+
+The `.Base/InputDigit `have the same behavior and usage as the input text
+
+## Behavior
+
+## Related

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

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

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

@@ -0,0 +1 @@
+Here are templates of clothing we produce at Malt. Please use them to create every goodie.

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

@@ -0,0 +1 @@
+

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

@@ -0,0 +1,13 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Clothing",
+  "slug": "clothing",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 6637374,
+  "pageUid": "6637374",
+  "fetchedAt": "2026-07-15T08:24:45.718Z",
+  "tabs": [],
+  "imagesPath": "packages/core-vue/static/zeroheight/clothing/",
+  "extraction": "zeroheight-api"
+}

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

@@ -0,0 +1 @@
+Here are templates of desk tools we produce at Malt. Please use them to create every goodie.

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

@@ -0,0 +1 @@
+

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

@@ -0,0 +1,13 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Desk tools",
+  "slug": "desk-tools",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 6637397,
+  "pageUid": "6637397",
+  "fetchedAt": "2026-07-15T08:24:45.732Z",
+  "tabs": [],
+  "imagesPath": "packages/core-vue/static/zeroheight/desk-tools/",
+  "extraction": "zeroheight-api"
+}

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

@@ -0,0 +1 @@
+Here are templates of tote bags we produce at Malt. Please use them to create every goodie.

package/dist/doc/zeroheight/guidelines/6637403/design-1.md

@@ -0,0 +1,7 @@
+### Tote bag design 1
+
+![This is what it should look like once printed.](/uploads/d3f2ArtrhyN-cX1qERzQyg.png)
+
+### Source file for printing
+
+**26x27cm**

package/dist/doc/zeroheight/guidelines/6637403/design-2.md

@@ -0,0 +1,7 @@
+### Tote bag design 2
+
+![This is what it should look like once printed.](/uploads/jGi6DdUGEJfv5GoNFdN4ug.png)
+
+### Source file for printing
+
+**26x27cm**

package/dist/doc/zeroheight/guidelines/6637403/design-3.md

@@ -0,0 +1,7 @@
+### Tote bag design 3
+
+![This is what it should look like once printed.](/uploads/KVnxaVK6GCgL8VvGFcNXVA.png)
+
+### Source file for printing
+
+**26x27cm**

package/dist/doc/zeroheight/guidelines/6637403/design-4.md

@@ -0,0 +1,7 @@
+### Tote bag design 4
+
+![This is what it should look like once printed.](/uploads/7ilvOsyXkTMbXrrpq3RIBw.png)
+
+### Source file for printing
+
+**26x27cm**

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

@@ -0,0 +1,18 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Tote bag",
+  "slug": "tote-bag",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 6637403,
+  "pageUid": "6637403",
+  "fetchedAt": "2026-07-15T08:24:45.912Z",
+  "tabs": [
+    "DESIGN 1",
+    "DESIGN 2",
+    "DESIGN 3",
+    "DESIGN 4"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/tote-bag/",
+  "extraction": "zeroheight-api"
+}

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

@@ -0,0 +1 @@
+Here are templates of water bottles and openers we produce at Malt. Please use them to create every goodie.

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

@@ -0,0 +1 @@
+

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

@@ -0,0 +1,13 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Water bottle & opener",
+  "slug": "water-bottle-opener",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 6637410,
+  "pageUid": "6637410",
+  "fetchedAt": "2026-07-15T08:24:45.922Z",
+  "tabs": [],
+  "imagesPath": "packages/core-vue/static/zeroheight/water-bottle-opener/",
+  "extraction": "zeroheight-api"
+}

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

@@ -0,0 +1 @@
+You will find all of Malt's stickers on this page.

package/dist/doc/zeroheight/guidelines/6637415/employer-brand.md

@@ -0,0 +1,3 @@
+### Employer Brand
+
+### Brand Embassador

package/dist/doc/zeroheight/guidelines/6637415/malt-strategy.md

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

package/dist/doc/zeroheight/guidelines/6637415/malt.md

@@ -0,0 +1 @@
+### Logo

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

@@ -0,0 +1,19 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Stickers",
+  "slug": "stickers",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 6637415,
+  "pageUid": "6637415",
+  "fetchedAt": "2026-07-15T08:24:45.896Z",
+  "tabs": [
+    "Seasonal",
+    "Malt",
+    "Malt Strategy",
+    "Employer brand",
+    "Random"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/stickers/",
+  "extraction": "zeroheight-api"
+}

package/dist/doc/zeroheight/guidelines/6637415/random.md

@@ -0,0 +1 @@
+### Random

package/dist/doc/zeroheight/guidelines/6637415/seasonal.md

@@ -0,0 +1,9 @@
+### Back to school
+
+### Summer
+
+### Spring
+
+### Winter
+
+### Halloween

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

@@ -0,0 +1 @@
+Joy is our secret sauce that keeps the user's attention, conveys enthusiasm, and helps us reach our goals. Follow these guidelines to choose the component that suits your situation best.

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

@@ -0,0 +1,91 @@
+![Success education matrice](/uploads/t2kjFeaWLP3I1LgdvQOD-Q.png)
+
+## Assess the level of success
+
+We define the level of success in a screen or a flow based on two key factors: success and information load.
+
+#### 👉🏼 Success
+
+- Is the screen key in the user journey?
+- Does the screen align with our business goals?
+
+#### 👉🏼 Information load
+
+- Do we share critical information?
+- Do we share several pieces of information?
+
+### Success level matrice
+
+So to use this graph:
+
+- Pick the two criteria related to your project
+- See in which area your project is
+- Then you can find just after the right way to assess your level of joy regarding your criteria.
+
+![Success education matrice](/uploads/zUpHLtqPwUsxRkqNR6HcNQ.png)
+
+## Choose the right component
+
+Some components will be more appropriate depending on where you land on the matrice.
+
+### Success level: Low success / Low information load
+
+**What type of context:**
+
+- User action done
+
+- This is an immediate feedback on a current action. For example, when you leave the screen/funnel on which you performed the action.
+- Feedback system
+
+- The feedback system is a direct, factual response provided by the software (*e.g. no more Internet*) that should lead the user to a possible solution.
+
+**Component:**
+
+#### Example: PO renewed
+
+![image](/uploads/lqhY8ZCcHik14Hf8sFTg5Q.png)
+
+### Success level:  Middle success / low information load
+
+**What type of context :**
+
+- User action who goes to another action or feedback for later
+
+- You can have a redirect (*e.g. here the project link, or the purchase order link...*) or you can also have the next step directly (*e.g. ‘you've received a quote, go and check it and validate...*)
+- Show the next steps inside the flow
+
+- It's also a way of marking an event or an element that you want to emphasize in a flow before continuing with the rest.
+
+**Component :**
+
+- Dialog
+- Interactions UI (gamification, animation, confetti etc.)
+
+#### Example: Send a project proposal
+
+![image](/uploads/kZihiQic2qQ8mavbobOKGA.png)
+
+#### Example: All client onboarding completed
+
+![image](/uploads/310j202pqrS9AeZyzEGzHQ.png)
+
+### Success level: High success / High information load
+
+**What type of context :**
+
+- Unlock action
+
+- Unlock an action that can only be performed under certain conditions
+- Begin a new flow
+
+- Marks the end of a particular flow to begin a new one
+
+**Component :**
+
+- Fullscreen, loaders, UI micro-animations, illustrations..
+
+#### Example: Account creation (client)
+
+![image](/uploads/9aF97uJlxDwCBD-ajqAouw.png)
+
+## Additional resources

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

@@ -0,0 +1,13 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Success education",
+  "slug": "success-education",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 6832117,
+  "pageUid": "6832117",
+  "fetchedAt": "2026-07-15T08:24:45.898Z",
+  "tabs": [],
+  "imagesPath": "packages/core-vue/static/zeroheight/success-education/",
+  "extraction": "zeroheight-api"
+}

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

@@ -0,0 +1 @@
+A common set of rules and a UI kit for creation and alignment

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

@@ -0,0 +1,16 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Admin",
+  "slug": "admin",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 6904773,
+  "pageUid": "6904773",
+  "fetchedAt": "2026-07-15T08:24:45.695Z",
+  "tabs": [
+    "Overview",
+    "UI Kit"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/admin/",
+  "extraction": "zeroheight-api"
+}

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

@@ -0,0 +1,33 @@
+![Admin Malt UI Kit](/uploads/0PNzsIKe8PwNCmCrlUg9iw.png)
+
+## Rules
+
+#### **1. Think about who the feature impacts. If it's the Malt Admin, design for them too**
+
+![image](/uploads/ByEsUWLRFWwWUDyKnv6Vpw.png)
+
+#### **2. Put Malt Admin features in the Malt product, not in Shake**
+
+![image](/uploads/dxzL6K_zajY1tLb3_VmI4w.png)
+
+![image](/uploads/i8kCoMRvMq0Js1dSkiAl_g.png)
+
+#### **3. Is this feature shared between the End User and Malt Admin? **
+
+![image](/uploads/4kOeCaj5vBhZ_YNUfrVB-A.png)
+
+### **How it works ? **
+
+*The way we build Admin features into Malt Product*
+
+**☝️Apply admin with care, remember *****Less is more***
+
+Because it is not systemised and manual rework case by case
+
+- Do: Group all call-to-actions in a dropdown button
+- Don't: Add separate actions in several places on the screen
+- Do: Use the banner at a single point in the interface to show the overall view of admin content 
+- Don't: Highlight elements individually to show that they are admin call-to-actions
+- Do: Remain consistent in the experiment, for example keep the banner in the slide panel 
+
+## Additional resources

package/dist/doc/zeroheight/guidelines/6904773/ui-kit.md

@@ -0,0 +1,27 @@
+## UI Kit
+
+*This is the v1 version of the UI Kit dedicated to admin*
+
+### Button admin
+
+#### Component variant
+
+#### Global component guidelines
+
+### Dropdown button admin
+
+#### Component variant
+
+#### Global component guidelines
+
+### Banner
+
+#### Component variant
+
+#### Global component guidelines
+
+### Toggle
+
+#### Component variant
+
+#### Global component guidelines

package/dist/doc/zeroheight/guidelines/7166343/changelog.md

@@ -0,0 +1 @@
+