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

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

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

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

@@ -0,0 +1 @@
+

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

@@ -0,0 +1 @@
+The information helper allows you to add additional information or explanation by clicking on an icon.

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

@@ -0,0 +1,38 @@
+![Information helper in a dialog](/uploads/zWBXnhzYr9p95HmjU2zvEA.png)
+
+## Anatomy
+
+## Usage
+
+By clicking on the (?) icon we will display extra information following theses rules :
+
+| Type of component | Size | Action | Content |
+| Tooltips | 16px | While hovering | - Text |
+| Product Tour | 16px | On Click | - Text - Badge |
+| Dialogs | 16px | On Click | - Text - Image - Hight light |
+## Components
+
+### Desktop
+
+### Animation
+
+| **Token** | Components | **Behavior** |
+| `$transition-duration--Default: 200ms;` | Helper | While hovering the (?) |
+| `$transition-duration--Default: 200ms;` | Tooltips | How the tooltip appear |
+| `$transition-duration--Default: 200ms;` | Product Tour | How the product tour appear |
+| `$transition-duration--slow: 400ms;` | Dialogs | How the dialog appear |
+## Example
+
+#### Tooltips
+
+![image](/uploads/cLACTk4r3LdA42vD-PRukg.gif)
+
+#### Dialog
+
+![image](/uploads/oP3vI9eX0K3OSCa2rBgMsg.gif)
+
+#### Product tour
+
+![image](/uploads/Rws1jA_xV-4XWp18GYYaWA.gif)
+
+## Related

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

@@ -0,0 +1,17 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Information helper",
+  "slug": "information-helper",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 3781391,
+  "pageUid": "3781391",
+  "fetchedAt": "2026-07-15T08:24:45.798Z",
+  "tabs": [
+    "Introduction",
+    "Usage",
+    "Code"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/information-helper/",
+  "extraction": "zeroheight-api"
+}

package/dist/doc/zeroheight/guidelines/3781391/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/guidelines/3782376/code.md

@@ -0,0 +1 @@
+

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

@@ -0,0 +1 @@
+The title page component allows us to standardize the way we use titles within a page

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

@@ -0,0 +1,11 @@
+## Type
+
+### Sidebar
+
+## Demo
+
+#### Example :
+
+![image](/uploads/ANlI0wAA7HYlAcpn-HGJCg.svg)
+
+## Related

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

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

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

@@ -0,0 +1,11 @@
+## Occurrences
+
+| Composent | Size | Product | Page |
+| Header |  | Transversal | Transversal |
+| Profil Cards |  | Freelance | Search |
+## Do/don't
+
+- Do: Use the componant with the good typogrphy (Moderat)
+- Don't: Don't use Agrandir typo for the title
+- Do: Use the good size for subtitle (Primary-400 : 16px)
+- Don't: Don't use other size for subtitle

package/dist/doc/zeroheight/guidelines/3992574/create-a-jira-ticket-for-development.md

@@ -0,0 +1,47 @@
+### When do I need to create a Jira Ticket?
+
+The Jira ticket is created once all the validation steps by the DS manager have been completed and validated.
+
+See the rules -> [How to contribute  | Workflow](https://zeroheight.com/6bf479565/p/595691/b/549c89)
+
+- The components/guidelines are designed in Figma and documented here
+
+- The feasibility has been studied and discussed with the development team concerned
+
+### Step 1 - Go to Jira
+
+#### 🧑🏻‍💻 AS AN ENGINEER
+
+Go to the Front-end Jira board (Ask right to the IT team if needed)
+
+-> [https://malt-community.atlassian.net/jira/software/c/projects/FEP/boards/120](https://malt-community.atlassian.net/jira/software/c/projects/FEP/boards/120)
+
+[Check the previous tickets](https://malt-community.atlassian.net/jira/software/c/projects/FEP/boards/120?quickFilter=468)
+
+### Step 2 - Create the ticket
+
+#### 🧑🏻‍💻 AS AN ENGINEER
+
+![image](/uploads/X2RKULhH_qcA6GC5gJTUng.png)
+
+1. Select the type of ticket - **Task, bug...**
+2. Select the State - Selected for development
+3. Select a clear and understandable title  - 	[JOY] New icon pack 1.3
+4. Select the proper component - Design system
+5. Add a proper description
+
+Example of description
+
+- What: Add a new XS button
+- Why: To use on a small table
+- Impact: Need to fit all the different states and typology of buttons
+- Add the link to the documentation with all the specs
+- Add the Figma link
+- Add examples from other design systems if need
+
+![image](/uploads/l0L9znp4XtperdGfiZjauQ.png)
+
+1. Select the Responsable
+2. Create the Ticket
+
+![image](/uploads/bSj7wLtOVCBPYLOqJveX8w.png)

package/dist/doc/zeroheight/guidelines/3992574/create-a-notion-ticket.md

@@ -0,0 +1,51 @@
+### Step 1 : Create
+
+#### 🙅‍♀️ AS A DESIGNER
+
+- Go on the [Design system backlog 2024](https://www.notion.so/maltcommunity/9779b425d491475eb879d04c11a8ccd8?v=b71b30afda074736b6f3d655505e42c0)
+
+- Create a new task on the bottom of the colomn "`🗄️ BACKLOG`"
+
+- Select a clear and understandable title
+
+- ***[NEW] New input tags for Mobile***
+- ***[NEW] New size of button - XL***
+
+![image](/uploads/9QQB2PFGegIaXkdZTG7Oyg.png)
+
+### Step 2 : Select attributes
+
+#### 🙅‍♀️ AS A DESIGNER
+
+- Figma Link
+- Point of contact
+
+![image](/uploads/5EQ997G5w0RwybfScKOmQg.png)
+
+### Step 3 : Content
+
+#### 🙅‍♀️ AS A DESIGNER
+
+I try to explain briefly my need and as much as possible information and context
+
+- Figma file with your proposal
+- Any links or info that you think useful
+- Coded example (if it exists) from
+
+- [https://codepen.io/](https://codepen.io/) (account available in the last pass)
+- [https://material.io/](https://material.io/)
+- ...
+
+Explanation :
+
+- What
+- Why
+- How
+
+![image](/uploads/8uOC5OwjFKgtO--aaZfBLw.png)
+
+### Step 4 : Publish
+
+#### 🙅‍♀️ AS A DESIGNER
+
+- Publish the new task

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

@@ -0,0 +1 @@
+On this page you will the workflow to properly ask a new components or update a current one with the design system team

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

@@ -0,0 +1,17 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "How to contribute ",
+  "slug": "how-to-contribute",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 3992574,
+  "pageUid": "3992574",
+  "fetchedAt": "2026-07-15T08:24:45.782Z",
+  "tabs": [
+    "Workflow",
+    "Create a Notion Ticket",
+    "Create a Jira ticket for development"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/how-to-contribute/",
+  "extraction": "zeroheight-api"
+}

package/dist/doc/zeroheight/guidelines/3992574/workflow.md

@@ -0,0 +1,87 @@
+![image](/uploads/y0p4iKRrHd53m3jwYAcUPw.svg)
+
+### Step 1 : Need
+
+#### 🙅‍♀️ AS A DESIGNER
+
+What kind of reasons could push me to contribute to the design system :
+
+- I need to modify/update a core component regarding a  new need in my product
+- I need a new component from scratch regarding a need in my product
+- I want to propose a global contribution not specially related to my product need
+
+### Step 2 : Built & Test
+
+#### 🙅‍♀️ AS A DESIGNER
+
+In order to contribute and work with the design system :
+
+- I come up with a Figma file with the proposals of my components
+- I try to build all the use cases
+
+- *States: Hover, Focus, Error, Disabled*
+- *Behavior: Empty states, lazy loading*
+- *Wording : Title & text rules*
+- I test the UX of my component in the context of my mockups
+- I try to document the do / don't about how to use the components
+
+#### The component checklist
+
+### Step 3 : Proposal
+
+#### 🙅‍♀️ AS A DESIGNER
+
+- I create a [Notion Ticket](https://www.notion.so/maltcommunity/9779b425d491475eb879d04c11a8ccd8?v=b71b30afda074736b6f3d655505e42c0) in the "Backlog" with an explanation of my need and the Figma file where the components are located.
+- I'm contacting the design system team thought the slack channel [3-guild-design-system](https://maltcommunity.slack.com/archives/CR1LXCKLY)
+
+### Step 4 : Review
+
+#### 🧑‍🔬 AS A SYSTEM DESIGNER
+
+I process the ticket by checking the following elements:
+
+- Is it enough scalable ?
+- Is is enough reusable as a transversal core component?
+- Does it meet our criteria of in term of accessibility, craft design?
+- Does it respect our Core design ?
+
+I check with the technical team the feasibility and prioritization ([complexity vs usage)](https://www.figma.com/file/6uVmyxByk6c9B6ai25G52d/%5BJoy%5D-Design-System---Priorisation?node-id=0%3A1)
+
+I clean the component, add it to the figma library and publish it
+
+### Step 5 : Documentation
+
+#### 🧑‍🔬 AS A SYSTEM DESIGNER
+
+I create / update the page in [Joy.malt.com ](https://Joy.malt.com )(Zeroheight) and start to document the components
+
+- Introduction
+
+- Anatomy
+- Size (if needed)
+- Components
+- Examples
+- Related
+- Usage
+
+I add the new component in the [release log](https://joy.malt.com/6bf479565/p/65f355--release-note)
+
+I move the Jira Ticket from "To Design" to "To Dev"
+
+#### 🙅‍♀️ AS A DESIGNER
+
+I check the documentation and see if everything is ok (last quick review)
+
+### Step 6 : Publish
+
+#### 🧑‍🔬 AS A SYSTEM DESIGNER
+
+I push the components in Figma with the release not(Publish)
+
+#### 🙅‍♀️ AS A DESIGNER
+
+I replace the components of my models with the new components from the Joy library to ensure synchronization in case of future update
+
+## Workflow
+
+![image](/uploads/F3hR81VotyeJU0B3C9NSyg.png)

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

@@ -0,0 +1 @@
+

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

@@ -0,0 +1 @@
+Component description

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

@@ -0,0 +1 @@
+## 🚧 Under construction

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

@@ -0,0 +1,17 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Data Table",
+  "slug": "data-table",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 4083384,
+  "pageUid": "4083384",
+  "fetchedAt": "2026-07-15T08:24:45.730Z",
+  "tabs": [
+    "Introduction",
+    "Usage",
+    "Content"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/data-table/",
+  "extraction": "zeroheight-api"
+}

package/dist/doc/zeroheight/guidelines/4083384/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/guidelines/4328996/change-log.md

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

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

@@ -0,0 +1,13 @@
+## Anatomy
+
+## Size
+
+Same as [Input Text](https://zeroheight.com/6bf479565/p/89d9e2-input-text)
+
+## Components
+
+### Default
+
+### Range
+
+## Related

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

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

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

@@ -0,0 +1,5 @@
+## General
+
+### Default
+
+### Range

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

@@ -0,0 +1 @@
+Use the page edit pattern when you want users to edit data in page

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

@@ -0,0 +1,37 @@
+![Edit in a side panel](/uploads/B1K1VqLUdtAQ5xc9u2X8fw.png)
+
+## **Criteria**
+
+|  | Page Edit | Inline Edit |
+| Use-case | Editing multiple properties of one resource | Editing one property across multiple resources |
+## Page edit
+
+Use the page edit pattern when you want users to manage a service resource by editing its properties and configuration in bulk.
+
+### Edit entry point
+
+### Edit pattern type
+
+### One-click to save
+
+When we are in edit mode, we display a button that allows us to save all the changes made
+
+#### Action bar
+
+### **Communicating saved changes **
+
+#### **Saved changes **
+
+If the changes have been taken into account we display a notification via the snackbar component
+
+#### **Unsaved changes **
+
+**Snackbar**
+
+If it is impossible to save the changes for a technical reason, we display a snack bar
+
+**Alert dialog**
+
+Depending on the case (for example funnel, dynamique table) we can display an alert dialog component
+
+##

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

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

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

@@ -0,0 +1 @@
+This page centralises the status of each component.

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

@@ -0,0 +1,31 @@
+## Glossary
+
+**New: ****recently implemented in both in Figma and code**
+
+**Ready: ****Available and up-to-date both in Figma and code**
+
+**In progress:**** Documentation or code in progress**
+
+**Todo:**** Design, documentation, and code planned**
+
+**Depreciated:**** Not up-to-date and use in the design system**
+
+**To be developed:**** Design & Doc ready, waiting for technical implementation**
+
+## Patterns
+
+## Components
+
+#### Button
+
+#### View
+
+#### Form
+
+## Modules
+
+#### Information
+
+#### Navigation
+
+#### Overlay

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

@@ -0,0 +1,13 @@
+{
+  "source": "https://zeroheight.com/6bf479565/p/35489b--status-page",
+  "title": "🔄 Status Page",
+  "slug": "status-page",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 4406320,
+  "pageUid": "4406320",
+  "fetchedAt": "2026-07-15T08:24:45.691Z",
+  "tabs": [],
+  "imagesPath": "packages/core-vue/static/zeroheight/status-page/",
+  "extraction": "zeroheight-api"
+}

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

@@ -0,0 +1 @@
+

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

@@ -0,0 +1,89 @@
+## Purpose
+
+Empty states are a subtle yet powerful way to support users and maintain a productive, human-centred experience. When there's no data to show, they provide clarity, guidance, and a sense of purpose.
+
+More than just placeholders, empty states shape how users perceive a product’s value and tone. Keep them **purposeful**, **helpful**, and **human**.
+
+They should clearly convey:
+
+- The view’s purpose
+- Why it’s empty
+- What users can do next
+
+- Do: Seize any opportunity to educate and support our users.
+- Don't: Do not leave blank spaces without education or direction for users to take.
+
+**💡 Tips**
+
+Before designing an empty state, ask:
+
+- What will this view look like without content?
+- What actions can users take to change or improve this state?
+- Is there helpful contextual content to include?
+- How can this moment feel supportive, not disappointing?
+
+## Types of empty states
+
+| Use case | Description | Title | Subtitle | CTA |
+| First-time use | User has never populated the space | “No projects yet” | “Create your first project to get started” | “Create project” |
+| Action complete | Result of an action leaves nothing to display | 🚧 | 🚧 | 🚧 |
+| Filtered out | No matching results found | “No results found” | “Try adjusting your filters or keywords” | “Reset filters” |
+| Content removed | Content was intentionally or accidentally removed | 🚧 | 🚧 | 🚧 |
+| Temporary issue | Data couldn’t load or isn’t available due to a transient issue | 🚧 | 🚧 | 🚧 |
+## **Tone**
+
+Empty states are a great way to build **momentum** and a human connection with the user through a **light tone** to encourage key actions. Tone should be:
+
+- **Supportive** and lightly **joyful**
+- **Proactive** and **educational**
+- Clear and confidence-building, not overly casual or promotional
+
+- Do: Put the user's needs at the heart of your content, while boosting engagement.
+- Don't: Avoid promoting features; focus on the user's needs.
+
+| Element | Required | Tone | Notes |
+| Title | ✅ | Joyful, informative | Should stand alone; focus on the “what”. |
+| Subtitle | ✅ | Neutral, instructive | Explains the “why” and “what’s next”. |
+| CTA | Optional | Clear, action-based | Use only when an action is possible and relevant. |
+## Component breakdown
+
+### **Image**
+
+- Non-interactive, contextual illustration
+- Should be **universal** (no cultural specifics)
+- Enhance understanding, not decoration
+
+- Do: Add an illustration that supports or complements the content.
+
+### **Title**
+
+- Short, informative, **3–5 words max **(30-35 characters, including spaces)
+- Always mention the core of the matter
+- Avoid starting with the action, focus on the context or state
+- May have a hint of joy or momentum, but always clear
+- Avoid vague phrases (e.g., “No projects”) or technical jargon
+- Never blame the user
+
+- Do: Set up the context first in the title: why are users seeing this empty state.
+- Don't: Avoid starting with the solution.
+
+### **Subtitle**
+
+- Expand on the title with clarity
+- Explain why this state exists and what to do next
+- Be helpful, not overly detailed
+- Keep to about **two lines** max (mobile and desktop alike)
+
+- Do: Leverage the details of the subtitle to explain how to solve the current situation and populate the screen.
+- Don't: Avoid being just descriptive; educate the users too.
+
+### **CTA**
+
+- Only include if the user can realistically act on it
+- Follow standard button guidelines
+- Use **direct, simple actions** (e.g., “Create project”)
+- Avoid marketing language like “Try now” or “Discover more”; empty states may not be the right place to upsell.
+- Secondary CTAs can link to help content
+
+- Do: Focus on actionable, problem-solving CTAs.
+- Don't: Do not add buttons that don't bring values to the users.

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

@@ -0,0 +1 @@
+An empty state refers to the visual and functional state of a user interface when there is no data or content to display.

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

@@ -0,0 +1,18 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Empty state",
+  "slug": "empty-state",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 4408066,
+  "pageUid": "4408066",
+  "fetchedAt": "2026-07-15T08:24:45.750Z",
+  "tabs": [
+    "Overview",
+    "Usage",
+    "Content",
+    "🔄 Changelog"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/empty-state/",
+  "extraction": "zeroheight-api"
+}