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

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

@@ -0,0 +1,94 @@
+## Email structure
+
+Be mindful of your email's information architecture to get your point across.
+
+![Overview of an email's information architecture](/uploads/6Y0fetQuOT_cRpmQVjThvA.png)
+
+Always put the most important information, as well as the main action above the fold line to increase actionability.
+
+## Email tiers
+
+Emails are structured within a three-tier framework. Each tier addresses a distinct purpose, with the level of design treatment increasing from minimal to more expressive.
+
+### Tier 1 - Account & system alerts
+
+Their purpose is to: communicate critical account or system state changes.
+
+| Content | UI | Actionability |
+| - Minimal load, concise. - Neutral, informative tone of voice. | - Very clean, sober, minimal UI. - Minimal to no branding emphasis. | - Extremely straight to the point. - No CTA to 1 button above the fold line. |
+- Do: Keep it straight to the point, with minimalist design.
+- Don't: Avoid cognitive overload.
+
+### Tier 2 - Transaction enablements
+
+their purpose is to: ensure users can and will complete mandatory, critical steps of their journey. Their nature can vary from notifications to alerts, errors, and success.
+
+| Content | UI | Actionability |
+| - 1 email = 1 core information - Reduced length - The tone may vary depending on the nature of the email  - **Notifications:** match message seriousness (neutral, serious, or celebratory). - **Alerts & errors:** direct, empathetic, informative. - **Success:** friendly, joyful, momentum-building. | Functional UI that can vary depending on the nature of the email:  - **Notifications**  - small content area - main button above the fold line. - **Alerts & errors:**  - mostly plain text - minimal visuals - **Success:**  - warmer UI - brand markers - optionally light visuals. | Emails should always redirect to the platform. However, the emphasis may differ whether the goal is  - *actionability* (the user MUST perform an action), or - *platform engagement* (action is not mandatory but is drives traffic).  - **Notifications:** CTA above fold if action needed. - **Alerts & errors:** CTA below the explanations, if applicable. - **Success:** reinforce achievement, offer next step CTA if relevant. |
+- Do: Communicate clearly the important information while fostering human connection and building momentum.
+- Don't: Avoid writing long email at the risk of missing the main information, or pushing the main CTA below the fold.
+
+### Tier 3 - Marketing levers
+
+*Out of transactional emails scope.*
+
+Their purpose is to: build relationship, promote engagement, upsell services.
+
+| Content | UI | Actionability |
+| - Highly branded. - Persuasive, engaging tone. | - Rich visuals - Stronger brand presence - Storytelling elements | - Multiple actions may appear (CTAs, links). - Less constrained. |
+## Email components
+
+### Subject and preview line
+
+Subject lines and previews are the first things (along with the sender) that the user will see. They give them context and enough information to assess how critical the email is.
+
+Subject line and preview complete each other:
+
+- The subject tells the WHAT. What is the general context and topic of the email. It’s straight-forward and clear, while also carrying hints of the tone of the email.
+- The preview tells the WHY or the HOW, depending on your context. It either provides a second level of details about the current situation, or it gives a preview of the solution / the next step.
+
+💡 The preview = the first line of your email's body - most of the time, the main title.
+
+- Do: Contextualise the subject line. Make it actionable, especially for tier 1 emails. Then, leverage the preview to explain the value.
+- Don't: Avoid generic and repetitive subject and preview lines.
+
+#### Character limitations
+
+Both subject line and preview obey to strict character limitations that can vary depending on the email client. Over these limits, the content won’t be visible by the user. The longer the subject line, the less visible the preview.
+
+| Email client | Subject line (visible characters) | Preview line (visible characters) |
+| Gmail (desktop) | ~60 char | ~100–120 chars |
+| Gmail (mobile) | ~30–40 char | ~40–80 chars |
+| Outlook (desktop) | ~60 char | ~35–55 chars |
+| Outlook (mobile) | ~40 char | ~35–50 chars |
+| Apple Mail (desktop) | ~60–70 char | ~100–120 chars |
+| Apple Mail (mobile) | ~35–40 char | ~40–80 chars |
+| Yahoo Mail (desktop) | ~45–55 char | ~85–110 chars |
+| Yahoo Mail (mobile) | ~30–40 char | ~40–70 chars |
+⚠️ **Be mindful of translations and responsiveness. **To make the most of these components, remain as short as possible in the source text. Use a pseudo localisation plugin to assess the length in other languages.
+
+#### On using dynamic values
+
+Limit to one dynamic value per line. Since their length can be unpredictable (especially with project names) place them at the end of the sentence to keep the main message clear and readable.
+
+### Main title
+
+Always include a main title to reintroduce the main topic of the email in a few words, and educate the user on the next steps.
+
+💡 The preview will inherit from the H1, so think of the email subject and H1 as a unified whole.
+
+- Do: Create a sense of complementarity between the email subject and the main title.
+- Don't: Avoid repeating the same content in the subject, preview and main title.
+
+### Highlight
+
+Use highlight sparingly to highlight an important piece of information. Refer directly to the highlight guidelines for more details.
+
+### User card
+
+**Primarily used for sourcing scenarios, this component provides a concise overview of a freelancer’s key information. It can be customised by removing certain details, such as:**
+
+- **Location**
+- **Ratings**
+
+**Additionally, adjust the CTA's microcopy to fit the specific use case.**

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

@@ -0,0 +1 @@
+Automated emails sent to clients and freelancers in response to a specific action or event.

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

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

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

@@ -0,0 +1,11 @@
+![Email template example](/uploads/VL4FquSqZD6R8iWXOUAuFw.png)
+
+## Anatomy
+
+## Header
+
+## Body
+
+## Footer
+
+## Template

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

@@ -0,0 +1,41 @@
+## Definition
+
+Transactional emails are automated messages sent to clients and freelancers **in response to specific actions or events.** They fit seamlessly into the user experience as they support key actions along their journey.
+
+**They differ from marketing emails.**
+
+|  | When to use | Primary focus | Trigger |
+| **Transactionalemails** | To confirm, notify, or enable a user’s action (ex: password renewal, new quote notification, etc.) | **Functional**: deliver essential information, ensure task completion. | - Timed event based (reminders) - Action-based** **(following a user’s interaction with the product or their account activity). |
+| **Marketing emails** | To promote, inform or engage users proactively (ex: newsletter, invitations to events, etc.) | Promotional: drive engagement, conversion and brand awareness. | - Scheduled - Campaign-based - Sent to a user segment (audience) or list. |
+💡 Because transactional emails are essential to the user experience and fall under **legitimate interest**, they don’t require opt-in or opt-out options - unlike marketing emails.
+
+## Planning communication
+
+Build a solid content strategy by thinking early on of all levers of communication - whether in- or out-of-product.
+
+![Decision tree for transactional email usage.](/uploads/qod73mutSWUHXKi7QqRWbA.png)
+
+💡 Be mindful of the average number of visits and time spent on the product of the target audience while choosing the best communication lever.
+
+### Transactional emails
+
+Transactional emails are key in the experience and must not be an afterthought. Introduce them early on in your design process.
+
+#### Designing  transactional emails
+
+- Add them to your flow, not on the side, to visualise the whole journey
+- Be mindful of potential other communications sent to your audience
+- Define the exact trigger with your PM
+- Be mindful of the sender name
+
+#### Sending transactional emails
+
+- Send immediately after the trigger
+- Make sure to define business metrics associated to your emails, on top of usual metrics
+- For timed event-based emails: be mindful on the time. Email sent to clients on the evenings will most likely not be read. Be mindful of time difference too. To improve visibility, send emails at the **start of the workday** or around **2 p.m.**, when users are more likely to check their inbox.
+
+Identify the right trigger for your email:
+
+|  | Definition | Examples |
+| **Action-based emails** | Triggered by a specific user action that requires acknowledgment or follow-up. These emails either:  - Confirm an action just taken by the user - Notify another user that they now need to take action | - New application received - Notification of quote accepted |
+| **Timed event-based emails** | Sent to a group of users on a scheduled date or recurring basis.  They often serve as reminders to complete an action and may depend on the status of a project. | - Weekly reminder to validate timesheets - Reminder to update availability |

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

@@ -0,0 +1 @@
+Illustration is a vital asset to our identity. It helps to add lighter touches to communications and explain more complex areas of our product offering in a playful and human manner.

package/dist/doc/zeroheight/guidelines/7291529/examples.md

@@ -0,0 +1,85 @@
+## Empty states
+
+### What type of context?
+
+Illustration used in empty states
+
+- 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 used
+
+Illustration + [title](https://zeroheight.com/6bf479565/p/5543da-title-page) + text + [button](https://zeroheight.com/6bf479565/p/75500d-button)
+
+### Illustration usage
+
+→ Illustration in black or black/red
+
+→ Here you can use a detailed one because there is only one on the screen
+
+→ Choosing according to context
+
+→ Think about and check that the illustration isn't used elsewhere in the flow (think about the coherence of the overall experience).
+
+### Composition Illustration
+
+Centered on the middle of the page
+
+Title: Mandatory - Short
+
+## Illustration as a loader
+
+### What type of context?
+
+- Wait until next step
+
+- Have information about the loading process
+- Keep Joy during waiting
+
+- Keep Joy during all the time of the journey
+
+### Component used
+
+Illustration + title + subtitle
+
+### Illustration used
+
+→ Illustration in black or black/red
+
+→ Here you can use a detailed one because there is only one on the screen
+
+→ For now, we cannot animate the illustrations
+
+### Composition
+
+Illustration: centered on the middle of the page (TBD)
+
+Title: Mandatory - Short
+
+## Success screen
+
+### What type of context:
+
+Illustration as success screen
+
+- Deliver a celebratory feedback
+
+- Provide a seamless and consistent experience across all ways users can post a project.
+- Add Joy at a key moment
+
+- Highlight a key moment by adding Joy
+- Used for success education
+
+### Component used
+
+Illustration + title + subtitleCan be inside a full screen or a modal  (the order of icons depends of the component)
+
+### Illustration used
+
+→ Illustration in black or black/red
+
+### Composition
+
+You can have more flexibility regarding the composition of the screen depending of the component

package/dist/doc/zeroheight/guidelines/7291529/guidelines.md

@@ -0,0 +1,34 @@
+## Guidelines
+
+### Colors
+
+#### How to use colour
+
+#### Illustration color palette
+
+#### Do/don't
+
+- Do: Use the illustration colours defined by the brand 
+- Don't: Use other colours for illustrations
+- Do: Use illustrations on plain coloured backgrounds 
+- Don't: Use illustrations with background photos
+
+### Size
+
+| **Size** | **Height** |
+| MEDIUM | 260px |
+| LARGE | 330px |
+- Do: Use the illustration size specified in the use case
+- Don't: Use a smaller illustration
+- Do: Use an icon in a small space to illustrate text 
+- Don't: Use an illustration in a small space to illustrate text
+
+### Composition
+
+- Do: Keep a good proposition between illustration and content size
+- Do: Keep a good proposition between illustration and content size
+- Don't: Use a different alignement for illustration
+
+- Do: 
+- Do: 
+- Don't:

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

@@ -0,0 +1,17 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Illustrations",
+  "slug": "illustrations",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 7291529,
+  "pageUid": "7291529",
+  "fetchedAt": "2026-07-15T08:24:45.794Z",
+  "tabs": [
+    "Overview",
+    "Guidelines",
+    "Examples"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/illustrations/",
+  "extraction": "zeroheight-api"
+}

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

@@ -0,0 +1,37 @@
+![Malt illustration library](/uploads/dPjYjEZFZ6fSWDzYn5Hv-A.png)
+
+## Illustration, icon or product visuals ?
+
+We have a tree-tiered approach to illustrations and iconography based on both size and usage:
+
+## Illustration principles
+
+### Ensure **clarity** at every step
+
+Illustrations should not bring noise, use them only when they convey meaning. They should be in coherence with the message to convey.
+
+### Create **momentum** through uplifting interactions
+
+Illustrations can ignite purposeful moments of joy (examples in the use cases behind with the different use cases)
+
+## When to choose between illustrations or icons?
+
+This guide will help you determine the most effective type of visual asset for your design, ensuring every choice is intentional and purposeful.Ask Intentional QuestionsBefore you add a visual, ask yourself these questions. Answering them will guide you to a more purposeful decision.
+
+#### a. 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.
+
+#### b. 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.
+
+### How to pick the right illustration?
+
+1/ To select the right illustration, first define the **message and emotion**** **you want to communicate.2/ After that, consider the **context and space available** to ensure the illustration fits its environment.
+
+### More principles and examples
+
+Find more detail, concrete examples and guidelines in:

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

@@ -0,0 +1 @@
+A **component** is a modular, reusable building block of the user interface. It is a self-contained unit, such as a button, card, or navigation bar, with a defined purpose and set of properties.

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

@@ -0,0 +1,13 @@
+## Button
+
+## Form
+
+## Information
+
+## Overlay
+
+## Navigation
+
+## View
+
+## Table

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

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

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

@@ -0,0 +1 @@
+A **layout** is the "template" of a page, defining the arrangement and structure of "organisms" to solve a specific user flow (e.g., a dashboard layout or a content page layout).

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

@@ -0,0 +1 @@
+

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

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

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

@@ -0,0 +1 @@
+Unlock **immediate** user value.

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

@@ -0,0 +1,13 @@
+## Overview
+
+## Our users …
+
+- efficiently complete their tasks
+- get instant response to their actions
+- are reassured they are on the right track
+
+## Our design …
+
+- makes goals feel achievable to the user
+- signals meaningful outcomes with every interaction
+- provides instant feedback and an immediate outlook

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

@@ -0,0 +1,13 @@
+{
+  "source": "https://zeroheight.com/6bf479565/p/886e69--immediate",
+  "title": "✪ Immediate",
+  "slug": "immediate",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 7490163,
+  "pageUid": "7490163",
+  "fetchedAt": "2026-07-15T08:24:45.682Z",
+  "tabs": [],
+  "imagesPath": "packages/core-vue/static/zeroheight/immediate/",
+  "extraction": "zeroheight-api"
+}

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

@@ -0,0 +1 @@
+Craft **seamless** journeys.

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

@@ -0,0 +1,13 @@
+## Overview
+
+## Our users …
+
+- intuitively navigate different parts of the journey
+- never get stuck
+- can easily integrate Malt into their broader ecosystem
+
+## Our design …
+
+- removes friction between steps, systems and internal domain boundaries
+- follows a unified interface approach cross-platform
+- considers every touchpoint of Malt’s service, on and off the platform

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

@@ -0,0 +1,13 @@
+{
+  "source": "https://zeroheight.com/6bf479565/p/92b4a3--seamless",
+  "title": "✪ Seamless",
+  "slug": "seamless",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 7490164,
+  "pageUid": "7490164",
+  "fetchedAt": "2026-07-15T08:24:45.683Z",
+  "tabs": [],
+  "imagesPath": "packages/core-vue/static/zeroheight/seamless/",
+  "extraction": "zeroheight-api"
+}

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

@@ -0,0 +1 @@
+Foster genuine **human** connection.

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

@@ -0,0 +1,13 @@
+## Overview
+
+## Our users …
+
+- feel understood (personalization) and valued (trust markers, visibility)
+- confidently staff or join the next superteam
+- understand and connect with Malt’s mission
+
+## Our design …
+
+- creates visibility on people and their stories
+- enables direct and trusted relationships between people
+- is conversational and conveys a sense of human touch

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

@@ -0,0 +1,13 @@
+{
+  "source": "https://zeroheight.com/6bf479565/p/673c95--human",
+  "title": "✪ Human",
+  "slug": "human",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 7490166,
+  "pageUid": "7490166",
+  "fetchedAt": "2026-07-15T08:24:45.681Z",
+  "tabs": [],
+  "imagesPath": "packages/core-vue/static/zeroheight/human/",
+  "extraction": "zeroheight-api"
+}

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

@@ -0,0 +1 @@
+Create **momentum** through uplifting interactions.

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

@@ -0,0 +1,13 @@
+## Overview
+
+## Our users …
+
+- know they are succeeding at every step of the way
+- feel rewarded when (autonomously) achieving their goals
+- build a sense of belonging to Malt’s mission and community
+
+## Our design …
+
+- ignites purposeful moments of joy
+- conveys Malt’s mission and community through messaging and content
+- fosters meaningful interactions with Malt’s brand

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

@@ -0,0 +1,13 @@
+{
+  "source": "https://zeroheight.com/6bf479565/p/093f80--momentum",
+  "title": "✪ Momentum",
+  "slug": "momentum",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 7490167,
+  "pageUid": "7490167",
+  "fetchedAt": "2026-07-15T08:24:45.683Z",
+  "tabs": [],
+  "imagesPath": "packages/core-vue/static/zeroheight/momentum/",
+  "extraction": "zeroheight-api"
+}

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

@@ -0,0 +1 @@
+Figma branches provide a safe space for designers to experiment and make changes to the main Design System file. They allow for isolated work and collaboration, ensuring that new components and updates are reviewed and approved before being merged.

package/dist/doc/zeroheight/guidelines/7490191/how-to-use-branches.md

@@ -0,0 +1,3 @@
+## How to use branches?
+
+Full tutorial about the usage of branches on Figma:

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

@@ -0,0 +1,31 @@
+![Branches on Figma](/uploads/hZHjwJthLMk-9aTtfZksyA.png)
+
+## What is a branch ?
+
+It’s a functionality that allows you to create a copy of a project and modify it independently of the master version. When the work is finished, and you need to make changes to the master project — the branch merges with the master version. Everything is just like the developers.
+
+## Why using branch ?
+
+Branches are exploratory spaces that enable designers to safely try new ideas without making changes to the main, or existing, file.Rather than auto-saving to the main file, changes from branches are merged into the main file when you're ready.
+
+## When to consider branching ?
+
+### Maintaining and contributing to a design library
+
+- Adding or modifying shared styles
+- Modifying existing components and Variants
+- Creating new components for a library
+
+### Sharing with collaborators and stakeholders
+
+- Collaborate or share progress and get feedback from stakeholders
+- Share a file or prototype link directly to the branch.
+
+### Freezing feature work for development handoff
+
+- Gives them a clear view of any new assets and design work
+- Collaborators can have a back-and-forth conversation within the branch as the feature is being built
+
+### Isolated design experiments and user testing
+
+- Branches allow you to test prototypes of derivative design explorations

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

@@ -0,0 +1,17 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Figma Branches",
+  "slug": "figma-branches",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 7490191,
+  "pageUid": "7490191",
+  "fetchedAt": "2026-07-15T08:24:45.754Z",
+  "tabs": [
+    "Introduction",
+    "How to use branches",
+    "Resources"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/figma-branches/",
+  "extraction": "zeroheight-api"
+}

package/dist/doc/zeroheight/guidelines/7490191/resources.md

@@ -0,0 +1 @@
+### Figma Branches ressources

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

@@ -0,0 +1 @@
+This collaborative model outlines how teams and individuals contribute to and maintain the Design System. It establishes clear processes, roles, and responsibilities to ensure all contributions are consistent, high-quality, and align with the system's overall vision.

package/dist/doc/zeroheight/guidelines/7490209/full-process.md

@@ -0,0 +1 @@
+## Full collaborative model process

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

@@ -0,0 +1,9 @@
+### Why?
+
+**Malt decided to switch to collaborative contribution model for a ****faster**** ****& ****more adopted**** Design System**
+
+### **From a centralized to a collaborative model**
+
+Empower squad designers and engineers to directly contribute to the system, with the core Design System team providing review and validation.
+
+![Design System Collaboration Models](/uploads/nwcwPHecGxsbCFnHYrWkOA.png)

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

@@ -0,0 +1,18 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Collaborative model",
+  "slug": "collaborative-model",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 7490209,
+  "pageUid": "7490209",
+  "fetchedAt": "2026-07-15T08:24:45.719Z",
+  "tabs": [
+    "Introduction",
+    "Need identification",
+    "Roles and responsibilities",
+    "Full process"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/collaborative-model/",
+  "extraction": "zeroheight-api"
+}

package/dist/doc/zeroheight/guidelines/7490209/need-identification.md

@@ -0,0 +1,9 @@
+### How to identify the needs
+
+- Did other people have the same need
+- It’s that a need for a new component or an evolution
+- Is there already a component that can answer the need?
+
+### Resource decision tree
+
+![image](/uploads/LRwziJCVW2-k-0d37BxvlQ.png)