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

package/dist/doc/zeroheight/foundations/4055467/usage.md

@@ -0,0 +1,11 @@
+## Text
+
+Our default text font is **Moderat**, its default size is **16px **to be easily readable on desktop and mobile. Depending on the context, we can also use 2px variations size:
+
+- ***18px – Text 1***. If folks are reading for long periods of time, be nice: don’t make them strain their eyes. ;-) You’re not printing out a single-spaced Word document; you’re writing for people sitting a couple of feet from their decade-old monitors.
+- ***16px – Text 2***. This is the most common font size on our pages and should be used for all body text.
+- ***14px – Text 3***. The absolute minimum for text-heavy pages. This is a secondary font size that you can use for less-important details of the site, supporting information and stats, sometimes captions, etc.
+
+## Character per line
+
+## Alignement

package/dist/doc/zeroheight/foundations/4845111/description.md

@@ -0,0 +1 @@
+Functional and emotional side.

package/dist/doc/zeroheight/foundations/4845111/fonts.md

@@ -0,0 +1,37 @@
+Typography plays an important role in our brand. We use two hardworking typefaces that bring nuance to our communication, helping us dial up or down our functional and emotional side.
+
+## Headline
+
+![image](/uploads/cX45wiwsZl_rcBKvOA1bZw.png)
+
+We use Agrandir Tight Medium for headlines at large sizes. We use it throughout all communications as it draws people’s attention and helps our messaging stand out.
+
+Our headline typeface is Agrandir. It is bold and direct, just like us. We use it for short and long headings and subheadings in order to bring attention to our messaging.
+
+Our body typeface is Moderat. It is a highly legible and practical family with lots of weights we can use for detail and functional copy. It pairs with and supports our headline typeface seamlessly.
+
+## Body copy
+
+![image](/uploads/ugs3vfMDgyp-VF-pvprnrw.png)
+
+We use Moderat for communications where we have a lot of information to display, such as body copy paragraphs.
+
+We use Moderat Bold for sub-headers, and Regular for body copy.
+
+## Google Slide fonts
+
+In instances where our typefaces aren’t available we use these substitute Google fonts. This is specifically for Google Slides. We only use them when we unable to use our brand typefaces.
+
+## Headline
+
+![image](/uploads/B0r50hSQ7NjM7YXSjwfBfA.png)
+
+## Body copy
+
+![image](/uploads/cEw8vFoNyreo5J3y_jRNgA.png)
+
+## Email font
+
+For email body copy we vary the typeface depending on the operating system it is being sent to. For Apple devices we use San Francisco, and for Google devices we use Roboto.
+
+![image](/uploads/TFSy8y_5kgJ81WkDm6UAkQ.png)

package/dist/doc/zeroheight/foundations/4845111/meta.json

@@ -0,0 +1,16 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Fonts",
+  "slug": "fonts",
+  "category": "foundations",
+  "component": null,
+  "pageId": 4845111,
+  "pageUid": "4845111",
+  "fetchedAt": "2026-07-15T08:24:45.759Z",
+  "tabs": [
+    "Fonts",
+    "Usage"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/fonts/",
+  "extraction": "zeroheight-api"
+}

package/dist/doc/zeroheight/foundations/4845111/usage.md

@@ -0,0 +1,9 @@
+- Don't: Do not mix fontweights in the same headline or sentence.
+- Don't: Do not condense headline and body copy.
+- Don't: Do not separate words too far in headlines.
+- Don't: Do not use off-brand colours. Typography should either use white or UI grey five.
+- Don't: Do not make typography illegible.
+- Don't: Do not use wide tracking.
+- Do: Do use white font on colored background.
+- Do: Do use grey 5 font on white and yellow background.
+- Do: Do use pink malt font on light greys and white background.

package/dist/doc/zeroheight/foundations/4845112/description.md

@@ -0,0 +1 @@
+Bright, bold and modern.

package/dist/doc/zeroheight/foundations/4845112/malt-colors-usage.md

@@ -0,0 +1,9 @@
+- Don't: Do not create new or alter the
+existing colours.
+- Don't: Do not use gradients.
+- Don't: Do not use black and white.
+- Don't: Do not use more than three colours
+at once (excluding high or lowlights).
+- Don't: Do not create transparency.
+- Do: Examples of color combinations.
+- Do: Examples of secondary color combinations.

package/dist/doc/zeroheight/foundations/4845112/malt-colors.md

@@ -0,0 +1,14 @@
+| Color helps us convey our energetic, optimistic personality. Our bold, confident use of color means we can stand out in any environment. And by embracing the full range of brand colors within the system we ensure that we always use combinations that complement the content of our communications.  The Malt Pink, our lead color, is supported by six colors, which together form our brand color palette. |
+## Main Brand Colors
+
+## Dark
+
+## Light
+
+## Text
+
+## UI colors
+
+Limited use of UI colors to UI illustrations, except if you are a designer.
+
+You can find them [here ](https://zeroheight.com/6bf479565/p/027b08-colors/b/266e61)

package/dist/doc/zeroheight/foundations/4845112/meta.json

@@ -0,0 +1,16 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Colors",
+  "slug": "colors",
+  "category": "foundations",
+  "component": null,
+  "pageId": 4845112,
+  "pageUid": "4845112",
+  "fetchedAt": "2026-07-15T08:24:45.723Z",
+  "tabs": [
+    "Malt colors",
+    "Malt colors usage"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/colors/",
+  "extraction": "zeroheight-api"
+}

package/dist/doc/zeroheight/foundations/7486175/introduction.md

@@ -0,0 +1,3 @@
+![Font hierarchy illustration](/uploads/u86Zc0dU3GHr3lVuyG1T8A.png)
+
+## Template - Font hierarchy (With sidebar)

package/dist/doc/zeroheight/foundations/7486175/meta.json

@@ -0,0 +1,13 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Font hierarchy",
+  "slug": "font-hierarchy",
+  "category": "foundations",
+  "component": null,
+  "pageId": 7486175,
+  "pageUid": "7486175",
+  "fetchedAt": "2026-07-15T08:24:45.758Z",
+  "tabs": [],
+  "imagesPath": "packages/core-vue/static/zeroheight/font-hierarchy/",
+  "extraction": "zeroheight-api"
+}

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

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

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

@@ -0,0 +1 @@
+**Icons** are used to manage a consistent set of icons for all interfaces. They define the size, color, and style properties to ensure a cohesive and readable visual language.

package/dist/doc/zeroheight/guidelines/1398442/library.md

@@ -0,0 +1,18 @@
+## Figma Link
+
+## Specification
+
+| Size | Stroke | Default color | Hover color |
+| 16px | 1.5 | `$-joy-color-neutral-gray-50` | `$joy-secondary-30` |
+| 24px | 2.0 | `$-joy-color-neutral-gray-50` | `$joy-secondary-30` |
+## Library
+
+### 16px - Stroke 1.5
+
+### 24px - Stroke 2
+
+## Payments
+
+### Provider
+
+## Flag

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

@@ -0,0 +1,19 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Iconography",
+  "slug": "iconography",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 1398442,
+  "pageUid": "1398442",
+  "fetchedAt": "2026-07-15T08:24:45.788Z",
+  "tabs": [
+    "Overview",
+    "Usage",
+    "Library",
+    "Request an icon?",
+    "🔄 Change log"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/iconography/",
+  "extraction": "zeroheight-api"
+}

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

@@ -0,0 +1,44 @@
+![Malt icon library](/uploads/WPlR1IaxoEJub7XxJKv3TA.png)
+
+## Illustration, icon or product visuals ?
+
+We have a tree-tiered approach to illustrations and iconography based on both size and usage:
+
+## Choosing the Right Illustration
+
+This guide will help you determine the most effective type of visual asset for your design, ensuring every choice is intentional and purposeful.
+
+### 1. Understand Our Visual Intentions
+
+Every visual element in our design system has a specific role. Your first step is to be intentional about the purpose of your design and choose the right tool for the job.
+
+- **Icons are for function: **Use them to make things scannable and clear. They're meant to help users complete tasks, not to decorate the page.
+- **Illustrations are for emotion:** Use them to tell a story, set a mood, or make a moment feel more human and welcoming. They should be used to transform an ordinary experience.
+
+### 2. Ask Intentional Questions
+
+Before you add a visual, ask yourself these questions. Answering them will guide you to a more purposeful decision.
+
+**What is the primary goal of this space?**
+
+- *To enable a user to complete a task quickly?* → Use a functional icon. Adding an illustration would be a distraction.
+- *To welcome a user, explain a new feature, or soften a blank state? *→ Use a storytelling illustration. The goal is to connect emotionally.
+
+**What is the emotional state of the user in this moment?**
+
+- *Are they trying to get something done? *→ Use simple icons to reduce friction.
+- *Are they encountering an empty space or a moment of waiting? *→ Use a warm, human illustration to add comfort and context.
+
+## Anatomy
+
+### A clean draw line
+
+![image](/uploads/m7pSBEm8bslzHca5i5sFjA.png)
+
+### Illustration complexity
+
+![image](/uploads/7MXMrNGWDai5wPIe_T0YzA.png)
+
+## Illustration principles
+
+Find more detail, concrete examples and guidelines in the [brand guidelines](https://zeroheight.com/6bf479565/p/6872c5-malt-guidelines)

package/dist/doc/zeroheight/guidelines/1398442/request-an-icon.md

@@ -0,0 +1,24 @@
+## I can't find an icon for my need
+
+1. **I can’t find an icon that fits my needs**
+2. Go on the DS System backlog and create a new task for the icon (+ fill all the elements needed)
+3. Create you icon by following the Malt icon design guide
+4. Push you change on validation in Figma
+5. **The design system team adds the icon to the lib and creates a new release (v1.1…)**
+6. **When the icon Figma lib is published, you are now able to use it in your design**
+
+## Malt icon design guidelines
+
+### To begin with
+
+### Use the grid
+
+### Stylistic rules
+
+### The detail
+
+### Finalizing the icon
+
+### Communication and merge
+
+### Congrats!

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

@@ -0,0 +1,51 @@
+## Usage
+
+When an icon is next to text, its main goal is adding extra information (the user can’t interact with this section).
+
+### Size
+
+❌ Can't be used another size than 16px or 24px
+
+❌ Do not scale Icons
+
+- Do: 
+- Don't: 
+
+## Joyfull icon principles
+
+Our icon joyfull principle is made to add you in small details of the product and add interaction with the user
+
+#### While hovering
+
+If the user have to interact with the icon (link or menu for example), we change the color to secondary-30 by default.
+
+#### Micro interaction
+
+![image](/uploads/jyo48N1ZHCI_B3T5PioTSQ.png)
+
+**When to use this micro animation? **You can use animation on icons on hover:- as long as the interaction adds joy without adding noise to the final composition- if the interaction is used at a moment when you want to create momentum in the production- if the type of icon allows it (you cannot change the nature of an icon to add this animation)
+
+- Do: Use the space to add visualy joy inside of the icon 
+- Don't: Not every icon can have this kind of hover state (because of their type)
+
+### Example
+
+#### Joyfull icons in navigation
+
+**What type of context: **
+
+- Navigation hover
+
+- Add Joy in micro-interactions
+- Be intentional as for the Malt Brand
+
+**Component used: **Icons**Illustration used: **→ Use only the interation while hovering → Keep in mid to not add too small detail in the icons (visiblity)
+
+### Link
+
+- Do: 
+- Don't: 
+
+#### Active state
+
+![image](/uploads/R5s5ic2k339MPJd1jUNHMw.gif)

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

@@ -0,0 +1 @@
+#### Joy is the Front-End design system For Malt

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

@@ -0,0 +1,16 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "___cover",
+  "slug": "___cover",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 1398447,
+  "pageUid": "1398447",
+  "fetchedAt": "2026-07-15T08:24:45.678Z",
+  "tabs": [
+    "Introduction",
+    "Team"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/___cover/",
+  "extraction": "zeroheight-api"
+}

package/dist/doc/zeroheight/guidelines/1398447/team.md

@@ -0,0 +1 @@
+

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

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

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

@@ -0,0 +1 @@
+Text input supports users inputing text into the system. This component is highly flexible to adapt to the needs of each application: with or without floating label, bottom cue, icons, or actions.

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

@@ -0,0 +1,29 @@
+![Input example in organization settings](/uploads/vBMDWxNLOSR3P3QtVXLEZg.png)
+
+## Anatomy
+
+Each input can be configured to work with Icons and helper message.
+
+## Type of inputs
+
+## Size
+
+| **Size** | **Height** |
+| LARGE | 64px |
+| MEDIUM | 48px |
+| SMALL | 40px |
+## States
+
+## Helper Text
+
+Helper text gives context about a field’s input, such as how the input will be used. It should be visible either persistently or only on focus.
+
+### Anatomy
+
+![image](/uploads/Q4trYlDXctp-o5jniO3bVQ.png)
+
+### States
+
+#### Error
+
+## Related

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

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

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

@@ -0,0 +1,14 @@
+## Usage
+
+The **Input Text** is the primary component for capturing short, single-line strings of data from a user. It is the workhorse of form design, providing a structured way to collect information like names, email addresses, or search queries.
+
+- **Single-Line Focus:** Use only for data that fits on one line. If the user needs to provide a paragraph or detailed feedback, use a **[Textarea](https://joy.malt.com/6bf479565/p/80b38d)** instead.
+- **Clear Labeling:** Every input must have a visible label. Placeholders are not a substitute for labels, as they disappear once the user starts typing.
+- **States & Feedback:** Provide immediate visual feedback for **Focus**, **Error**, and **Success** states to guide the user through the completion of the form.
+
+## Do/don't
+
+- Do: Do use Helper Text below the input to provide specific formatting rules (e.g., "Password must be 8+ characters").
+- Don't: Don't use Placeholder Text to explain complex instructions; it disappears as soon as the user types.
+- Do: Do match the Width of the Input to the expected length of the content (e.g., a shorter width for a Zip Code).
+- Don't: Don't use a text input for data that has a strictly limited set of known options (use a Select or Radio instead).

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

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

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

@@ -0,0 +1,36 @@
+### Labels
+
+- **Be concise.** Aim for 1–3 words when possible; avoid exceeding one line.
+- **Use sentence case.** Start with a capital letter.
+- **Use parallel structure.** All options in a group should follow the same grammatical pattern.
+- **Make each option distinct.** Users should immediately understand the difference between choices.
+- **Avoid negative phrasings.** An option shouldn’t be another’s negation.
+
+### Group labels
+
+- **Phrase as a statement or question.** Help users understand what they're choosing.
+- **Be specific.** "Payment method" is better than "Options."
+- **Don't end with a colon.** The visual grouping makes the relationship clear.
+
+| ❌ Don't | ✅ Do |
+| Options: | Invoicing method |
+| Select one | How would you like to pay? |
+### Defaults
+
+- **Pre-select an option when appropriate.** Choose the most common, recommended, or safest choice.
+- **Never pre-select options that could cost money or commit the user** without clear intent.
+- **If no logical default exists, leave unselected** and validate that a selection is made.
+
+### Ordering
+
+1. Place the **most common or recommended option first**
+2. Use a **logical sequence** (e.g., price low to high, frequency, size)
+3. If options have equal weight, use **alphabetical order**
+4. Place potentially risky or destructive options **last**
+
+### Accessibility
+
+- **Maintain sufficient color contrast.** Meet WCAG AA ratios.
+- **Never rely on colour alone.** Use a filled circle to show selection.
+- **Provide a visible focus state.** Use a clear outline distinct from the selected state.
+- **Labels must be descriptive on their own.** Users may navigate by form controls (screen readers)

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

@@ -0,0 +1 @@
+RadioButtons allow a user to select a single option from a list of predefined options

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

@@ -0,0 +1,27 @@
+![Radio button in setting page](/uploads/6oT5myC8aBJb1ehpPCNpDQ.png)
+
+## Anatomy
+
+## Specifications
+
+## Type
+
+## States
+
+### Selected
+
+### Unselected
+
+## Variants
+
+### Atoms radio
+
+### Radio group
+
+#### Horizontal
+
+#### Vertical
+
+## Example
+
+## Related

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

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

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

@@ -0,0 +1,19 @@
+## How to replace the selectable item component?
+
+## Usage
+
+Radio buttons are particularly useful when:
+
+1. Only one option can be selected: Radio buttons are ideal when only one option can be selected, as they force users to choose only one option from a list.
+2. The options are mutually exclusive: When the options are mutually exclusive, radio buttons are a great choice, as they clearly indicate to users which options are available and which option has been selected.
+3. The options are infrequently changed: If the options are infrequently changed, radio buttons are a good choice because they allow users to easily view and change their selections.
+4. The options are related: If the options are related and it makes sense for them to be grouped together, radio buttons are a good way to keep them together and easily accessible.
+5. Space is limited: Radio buttons take up minimal screen real estate, making them a good choice when space is limited.
+
+## Main rules
+
+- Do: Do use when the user must pick exactly one option from a list of two or more.
+- Don't: Don't use if the user needs to select "none"—Radio buttons should always have a default or be mandatory.
+- Do: Do list options in a logical order (e.g., simplest to complex, or cheapest to most expensive)
+- Don't: Don't use for high-impact navigation; it should only store a value within a form.
+- Do: Don't use more than 5-6 options; if the list is longer, consider a Select/Dropdown menu.

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

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