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

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"
+}

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

@@ -0,0 +1,49 @@
+![Illustration example empty state](/uploads/ZLRnhdIZaqBPtSouGPwxDQ.png)
+
+## Key UX Context
+
+Empty states are moments in a user’s experience with a product where there is nothing to display.
+
+Empty states are typically used in SaaS products to guide users on what to do next or to provide helpful information or actions when there is no data to show.
+
+### Empty-state UX design principles
+
+1. Understand the context
+2. Communicate the reason
+3. Provide guidance
+4. Use visual cues
+5. Evolve with the user's journey
+
+#### Types of Empty States
+
+- **First use** – Occurs with a new product or service when there is still nothing to show, such as a new Evernote or Dropbox account.
+- **User cleared** – This occurs when users complete actions such as clearing their inbox or task list, and the result is an empty screen.
+- **Errors** – These occur when something goes wrong, or when there are issues such as a mobile phone going offline due to network problems.
+- **No results/No data** – No data found UI design occurs when there is nothing to show. This can happen if someone performs a search and the query is empty or there isn’t data available to show (when filtering for a date range that has no data for example).
+
+Here are a few empty-state examples at Malt:
+
+- An empty chat box.
+- The search results page without a freelancer profile
+- First-time user dashboard
+- Statistic page without any data
+- Empty project table
+- Error pages
+
+## General guidelines
+
+- Do: Always provide an action. Having no recourse creates confusion and prevents users from moving forward. If no action can be provided, include a link in the description to navigate users to the page where they can complete the action.
+- Don't: 
+- Do: 
+- Don't: 
+
+- Do: Always display a resource counter to reflect the number of resources.
+- Don't: Don’t use empty states for errors. Use the snackbar for displaying errors.
+
+## Writing guidelines
+
+- Keep labels and descriptions clear and concise.
+- Use sentence case for all text. Don’t use title case.
+- Use terminal punctuation (periods, exclamation points, question marks).
+- Use present-tense verbs and active voice wherever possible.
+- Don't use "please," "thank you," or Latinisms such as "e.g.," "i.e.," or "etc."

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

@@ -0,0 +1,24 @@
+Empty states are used to communicate the absence of content within a page or section. They often appear when:
+
+- The user hasn't performed an action yet (ex: first use, zero state)
+- Previously available content has been deleted or removed
+- An action has been completed and there’s no content to show
+- Filters or search return no results
+- A temporary loading or data-fetching issue prevents content from displaying
+
+> Important note: Empty states are not error messages, loading spinners, or confirmation states.
+
+### ✅ Do’s
+
+Empty states are an opportunity to **educate**, **guide**, or **re-engage** users. Use them to maintain **momentum** and offer **clarity**.
+
+- **Explain** why the user is seeing an empty state
+- **Provide clear next steps** (ex: "Create your first project")
+- **Match tone and visuals** to the context and urgency
+- **Keep content minimal and scannable**
+
+### ❌ Don’ts
+
+- **Don’t leave it blank.** Even a friendly message is better than nothing
+- **Don’t over-explain** or crowd the space
+- **Don’t show a CTA** if no meaningful action can be taken

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

@@ -0,0 +1 @@
+Malt STRAGEGY is the community of **vetted** management consultants and interim executives.

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

@@ -0,0 +1,9 @@
+## Introduction
+
+This documentation aims to explain the rules of use and the integration of the elements representing Malt Strategy within the product.
+
+Some of the rules may differ from the Marketing section, what you will find here only concerns the product
+
+For more info about Marketing :
+
+- [Malt Strategy Product Guidelines_New version 25.04](https://docs.google.com/presentation/d/1JWxmob0bS0bNOkThlTsWsOYKiD8fiDuWwfCFuWydW10/edit#slide=id.g22a87d5047e_0_0)

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

@@ -0,0 +1,16 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Malt Strategy branding",
+  "slug": "malt-strategy-branding",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 4544263,
+  "pageUid": "4544263",
+  "fetchedAt": "2026-07-15T08:24:45.828Z",
+  "tabs": [
+    "Introduction",
+    "🎨 UI Guidelines"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/malt-strategy-branding/",
+  "extraction": "zeroheight-api"
+}

package/dist/doc/zeroheight/guidelines/4544263/ui-guidelines.md

@@ -0,0 +1,75 @@
+## How integrate Malt strategy in the product
+
+### Logo
+
+The Malt Strategy logo replaces the classic Malt logo on the product pages, which are intended for Strategy profiles only. It can be found in the header during the registration funnel (vetting...) or when a strategy profile is created.
+
+#### Profil page
+
+![image](/uploads/Nk2NWhmcDn8bF3gRk4AQ0A.png)
+
+#### **Usage**
+
+- Do: - The logo must always be in the same color.
+- Don't: - Use the "powered by comatch"
+- Change the color
+- Change the position in the header
+- Use it without the brew
+
+#### Color of the logo
+
+## Shapes
+
+In addition to the logo and content, we use a "Shapes" component in the funnels to accentuate the differentiation.
+
+The shapes are integrated into the funnel template provided by the design system joy.
+
+It can also be added in the visual type dialog but in a subtle way and always in the same place.
+
+It is not a matter of weighing down our interfaces but of subtly dressing them up
+
+#### Entry points
+
+| **Flow** |
+| Malt Strategy sign-up |
+| Vetting Process |
+| Setting profiles |
+![image](/uploads/8CsV-3j7NWbbIpoigeh96w.png)
+
+#### **Usage**
+
+#### 
+
+📱 <1024px screen size we don't display shape
+
+- Don't: Change the size
+Color order
+Position
+
+## Avatar Strat
+
+Avatar are used to display the profile picture of the user.
+
+#### **Usage :**
+
+The Malt Strat avatar component is used when it is necessary to differentiate between a "Strat" profile and a classic profile on the same page
+
+![image](/uploads/bP84Zaf3qUsJNw4a0i-lTQ.png)
+
+- Do: Here we have both classic and strat profiles. Strat profile are highlighted with the avatar components
+- Don't: Here, the (S) badge is not needed since only 1 profile is visible. 
+
+## Illustration
+
+The illustrations are used to add dynamism to our product pages. They can be used to illustrate an error, an action or an empty status
+
+![image](/uploads/a3VGSoxDx2-w7x2gGwCJkQ.png)
+
+- Do: - Mono chrome illustration 
+- Only Gray-7 and white colors
+- Remove small details
+- Don't: Use custom colors
+
+#### **Related information :**
+
+- [Malt Strategy Product Guidelines_New version 25.04](https://docs.google.com/presentation/d/1JWxmob0bS0bNOkThlTsWsOYKiD8fiDuWwfCFuWydW10/edit#slide=id.g22a87d5047e_0_0)

package/dist/doc/zeroheight/guidelines/4565202/definition.md

@@ -0,0 +1,29 @@
+## Introduction
+
+Modality is a design technique that presents content separately, preventing interaction with the parent's view and requiring **explicit action to dismiss it.** While a Non-Modal Screen allows users to simply go back to the parent screen, the Modal Screen requires users to complete an action before returning to the main window (“save”, “cancel”, “close”...)
+
+**Modal screens** require people to focus on a single, self-contained task, in the context of their free movement within the information architecture of an application before continuing.
+
+| **Type of components** | Position | Occurrences |
+| Dialog / Window | Overlay | Sign-in, product tour, onboarding |
+| Dialog / Full page | Overlay | Funnel |
+| Side panel / Overlay panel | Overlay | Edit Profil, Edit mission preferences |
+| Side panel / Split Panel | Side by Side | ❌ |
+| Side panel / Elevated | Overlay |  |
+## Type of components
+
+### Example
+
+#### Dialog
+
+#### Sidepanel
+
+Example :
+
+![image](/uploads/eJ1K0BJvbBV0clfaUak7_Q.png)
+
+#### Alert dialog
+
+#### Product Tour
+
+![image](/uploads/l9FWEjSEUfdebARO2LNztQ.png)

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

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

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

@@ -0,0 +1,27 @@
+### General Guidelines
+
+#### When to use dialog? :
+
+- Focus on small information.
+- If user has fewer than 2 actions
+- To show / onboard a new feature/announcement
+- Quick validation (alert dialog)
+
+- Do: Small information and only one action required
+Focus for the user
+- Don't: Here, the use of tj
+- Do: To onboard with illustration and content
+- Don't: 
+
+#### When to use a Full dialog vs overlay dialog
+
+#### When to use Sidepanel
+
+- If the user has more than 3 actions to do (Ex : edit profil)
+- Compare information on the same screen (Ex : ATS)
+- Display a complement of information
+
+The size is limited to a maximum of 70% coverage of the main screen
+
+- Do: Numerous actions needed
+- Don't: Not adapted for Dialog, too many action

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

@@ -0,0 +1 @@
+Welcome to the Malt Brand Center: Joy!