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

package/dist/doc/zeroheight/guidelines/5196627/spanish.md

@@ -0,0 +1,61 @@
+## General rules
+
+- In a sentence, only the first word is capitalized.
+- Capitalize all proper nouns.
+- Capitalize after a question mark or exclamation point to start the next sentence.
+
+✅ Haz accesibles los temas técnicos con contenidos de calidad.
+
+❌ Haz Accesibles los Temas técnicos con Contenidos de Calidad.
+
+## Capitalization after colons (:)
+
+- In Spanish, always use lowercase after a colon, except in specific cases.
+- Do not write a colon after "como" or a preposition.
+- Avoid using a colon more than once in the same sentence or phrase.
+
+### **Exception**
+
+- Use a capital letter after a colon when followed by proper nouns or direct literary quotes.
+
+✅ Malt es una plataforma digital en España, Francia y Alemania.
+
+✅ Utiliza Malt cuando necesites: ayuda con tu empresa o un experto freelance.
+
+❌ Malt es una plataforma digital en: España, Francia y Alemania.
+
+❌ Utiliza Malt cuando necesites: Ayuda con tu empresa o un experto freelance.
+
+## Titles
+
+- In Spanish, capitalize only the first letter of the first word in the title, except for proper nouns, which always begin with a capital letter.
+
+✅ Haz accesibles los términos técnicos.
+
+❌ Haz Accesibles Los Términos Técnicos.
+
+## Brand
+
+Use capitals
+
+✅ Malt
+
+❌ malt
+
+## Team names
+
+In Spanish, use capital letters only for the first word in a sentence.
+
+✅ Equipo de diseño de producto.
+
+❌ Equipo de Diseño de Producto.
+
+## Pages, products & features
+
+In Spanish, use "quotes" to indicate a page section or a product.
+
+Use the same term that appears on Malt's official website. Write it in the same way (capitalization, Anglicism, etc).
+
+✅ Podrás supervisar tus procesos de selección en la sección “Mis proyectos”.
+
+❌ Podrás supervisar tus procesos de selección en la sección mis proyectos.

package/dist/doc/zeroheight/guidelines/5196629/dutch.md

@@ -0,0 +1,15 @@
+### Abbreviations & acronyms
+
+Use the standard abbreviation when it is available.
+
+✅ URL
+
+✅ wifi
+
+If you're unsure whether your reader will understand the abbreviation or acronym, write it out the first time you mention it on a page and put the abbreviation in brackets directly after it. Only use the abbreviation or acronym afterwards on that page.
+
+✅ First mention: Midden-Europese Tijd (MET)
+
+✅ Next mentions: MET
+
+> Refrain from using Malt's own/internal abbreviations. They are unlikely to be understood. If you don't have a choice, refer to the second rule.

package/dist/doc/zeroheight/guidelines/5196629/english.md

@@ -0,0 +1,15 @@
+### **Abbreviations & acronyms**.
+
+- Use the standard abbreviation when it is available
+
+✅ URL
+
+✅ wifi
+
+- If you're **unsure whether your reader will understand the abbreviation or acronym**, **write it out the first time** you mention it on a page and put the **abbreviation in brackets** directly after it. Only use the abbreviation or acronym afterward on that page.
+
+✅ First mention: *Central European Time (CET)*
+
+✅ Next mentions: *CET*
+
+- Refrain from using Malt's own abbreviations. They are unlikely to be understood. If you don't have a choice, refer to the second rule!

package/dist/doc/zeroheight/guidelines/5196629/french.md

@@ -0,0 +1,15 @@
+Use the standard abbreviation when it is available.
+
+**DO**
+
+- Mettez à jour votre CV
+
+**DON’T**
+
+- Mettez à jour votre Curriculum Vitae
+
+If you're unsure whether your reader will understand the abbreviation or acronym, write it out the first time you mention it on a page and put the abbreviation in brackets directly after it. Only use the abbreviation or acronym afterward on that page.
+
+For instance, as a first mention on a page, write “Pour notre webinar, rendez-vous à 20h heure d’Europe centrale (CET)”. For the next mentions, simply use the acronym (e.g. “N’oubliez pas : rendez-vous le 9 mai à 20h CET”)
+
+Refrain from using Malt's own/internal abbreviations. They are unlikely to be understood.

package/dist/doc/zeroheight/guidelines/5196629/german.md

@@ -0,0 +1,38 @@
+Due to space restrictions, we use word abbreviations such as “z. B.”, “Bsp.”, “d. h.” or “usw.” in the product. When using abbreviations, always pay attention to the correct placement of spaces and punctuation.
+
+- There is NO comma before usw.
+- D. h., z. B. und u. a. are separated by spaces
+
+✅ Bsp.: "Agile Methodik", "Konfliktlösung" usw.
+
+✅ Einsatzort (z. B. Berlin, London, Paris, Amsterdam, Brüssel, ...)
+
+### Abbreviations & acronyms
+
+- **Use standard abbreviations if available.**
+
+✅ URL
+
+✅ WLAN
+
+- **Ensure readability.**
+
+If you're unsure whether your reader will understand the abbreviation or acronym, write it out the first time you mention it on a page and put the abbreviation in brackets directly after it. Only use the abbreviation or acronym afterward on that page.
+
+✅ First mention: Mitteleuropäische Zeit (MEZ)
+
+✅ Next mentions: MEZ
+
+- **Don’t use Malt-internal abbreviations.**
+
+Refrain from using Malt's own/internal abbreviations. They are unlikely to be understood. If you don't have a choice, refer to the second rule.
+
+### Shortened words
+
+Avoid merging articles with prepositions and other stylistic shortening of words. Exceptions are possible, e.g. in marketing slogans and headlines.
+
+**Examples: **
+
+- “Auf dem” instead of “aufm”
+- “War es” instead of “wars”
+- “Mache es Dir leicht” instead of “mach’s Dir leicht”

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

@@ -0,0 +1,19 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Abbreviations",
+  "slug": "abbreviations",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 5196629,
+  "pageUid": "5196629",
+  "fetchedAt": "2026-07-15T08:24:45.694Z",
+  "tabs": [
+    "English",
+    "French",
+    "German",
+    "Spanish",
+    "Dutch"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/abbreviations/",
+  "extraction": "zeroheight-api"
+}

package/dist/doc/zeroheight/guidelines/5196629/spanish.md

@@ -0,0 +1,14 @@
+- In Spanish, use the standard abbreviation when available.
+- Consistency: Once you introduce an abbreviation or acronym, use it consistently throughout the text to maintain coherence and reduce redundancy.
+
+✅ URL
+
+✅ wifi
+
+- If you cannot confirm whether readers will understand the abbreviation or acronym, write it out in full the first time you mention it on the page and place the abbreviation in parentheses immediately afterward. Use only the abbreviation or acronym in subsequent mentions on that same page.
+
+✅ Primera mención: Hora Central Europea (HCE)
+
+✅ Menciones siguientes: HCE
+
+- Refrain from using Malt's own/internal abbreviations. They are unlikely to be understood. If you don't have a choice, refer to the second rule.

package/dist/doc/zeroheight/guidelines/5196630/dutch.md

@@ -0,0 +1,37 @@
+### Talking about Malt
+
+Use “we” or “wij” when writing as Malter speaking about Malt.
+
+### Talking about the users
+
+Use the preferred "they/them/their" when talking indirectly about the users as a group. Unlike in English, in Dutch you can’t use “they/them/their” to talk about a single person you don’t know the gender of.
+
+✅ Freelancers hebben je sollicitaties gestuurd. Je kunt nu contact met ze opnemen.
+
+✅ De freelancer heeft het activiteitenrapport ingevuld.
+
+❌ De freelancer heeft hun activiteitenrapport ingevuld.
+
+As much as possible address the users directly with "je/jij/jou/jouw".
+
+### Formal or informal address?
+
+On Malt, we generally address users (both clients and freelancers) with the informal je/jij/jou/jouw. U/uw can be perceived as old fashioned or distant, and this is not the effect we want to create when addressing our users.
+
+We chose not to differentiate between clients and freelancers, both because we as translators could easily mix things up and use the wrong address, but also to not give the impression that we have more respect for one more than the other.
+
+✅ De offerte is goedgekeurd. Je kunt aan de opdracht beginnen.
+
+❌ De offerte is goedgekeurd. U kunt aan de opdracht beginnen.
+
+✅ Je factuur is betaald.
+
+❌ Uw factuur is betaald.
+
+#### Exception: formal emails
+
+There is one case where we prefer to use the formal address u/uw. Sometimes Malt sends out emails that deal with more serious matters, such as payment delays, a breach of the rules, etc. These emails might give the user a formal warning, or might inform them that they have been banned from the platform.
+
+In these cases, the formal address may be more appropriate and may underline the severity of the situation.
+
+This is something to be decided upon case per case. Just use your common sense ;)

package/dist/doc/zeroheight/guidelines/5196630/english.md

@@ -0,0 +1,9 @@
+### Talking about Malt
+
+Use “we” when writing as Malter speaking about Malt.
+
+### Talking about the users
+
+Use the preferred "they/them/their" when talking indirectly about the users.
+
+As much as possible address the users directly with "you/your/yours".

package/dist/doc/zeroheight/guidelines/5196630/french.md

@@ -0,0 +1,11 @@
+### **"Vouvoiement" **
+
+Use the formal "vous" pronoun when addressing people of all ages. The informal "tu" pronoun can be perceived as impolite by some. This rule is true for both clients and freelancers.
+
+### “On"
+
+Avoid using the pronoun “on” which sounds very informal.
+
+If you want to talk about the users in general, you can use the pronoun “vous” in order to replace “les utilisateurs”.
+
+Depending on the context, if you want to talk about members of the Malt team, you can use the pronoun “nous”.

package/dist/doc/zeroheight/guidelines/5196630/german.md

@@ -0,0 +1,40 @@
+### Talking about Malt
+
+Use “wir” when writing as Malter speaking *about* Malt or *as* Malt.
+
+### Talking about users
+
+Use "sie/ihnen/ihr" (they/them/their), when talking indirectly about users.
+
+#### Talking to users: “Du” or “Sie”
+
+We communicate differently with different German-speaking user groups:
+
+- Freelancers (both on the marketplace and at Malt Strategy) are addressed *informally*
+- Clients are addressed *formally*
+
+#### **Why do we address freelancers and clients differently?**
+
+At Malt, we meet freelancers at eye level. That's why we use the informal form of address (“**Du**”) when communicating with our **freelancer** community.
+
+To best adapt to the corporate culture in German-speaking countries, we use the formal form of address (“**Sie**") when communicating with **clients and companies.**
+
+[👉](https://emojipedia.org/backhand-index-pointing-right) "Du/Dich/Dir/Dein" (Freelancer/Consultant)
+
+[👉](https://emojipedia.org/backhand-index-pointing-right) “Sie/Ihnen/Ihr” (Client)
+
+💡 Both “Sie” and “Du” (and all associated grammatical variants) are written with capital letters at Malt.
+
+**Examples (freelancers):**
+
+✅ Schön, dass Du da bist!
+
+✅ Registriere Dich oder melde Dich an, um die Erstellung Deines Profils abzuschließen
+
+✅ Hol Dir Dein Stück vom Kuchen
+
+**Examples (clients):**
+
+✅ Bitte wählen Sie Freelancer aus, um ihnen ein Projekt anzubieten
+
+✅ Verwalten Sie Ihre Einstellungen und laden Sie Ihr Team ein, Ihrem Unternehmenskonto auf Malt beizutreten.

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

@@ -0,0 +1,19 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Pronouns",
+  "slug": "pronouns",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 5196630,
+  "pageUid": "5196630",
+  "fetchedAt": "2026-07-15T08:24:45.867Z",
+  "tabs": [
+    "English",
+    "French",
+    "German",
+    "Spanish",
+    "Dutch"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/pronouns/",
+  "extraction": "zeroheight-api"
+}

package/dist/doc/zeroheight/guidelines/5196630/spanish.md

@@ -0,0 +1,21 @@
+### Talking about Malt
+
+In Spanish, use "nosotros" or "nuestro(a) + noun" to write as part of Malt when talking about the company.
+
+### Talking about users
+
+When speaking indirectly about users, use the pronoun "ellos/ellas" to refer to them generically.
+
+Whenever possible, address users directly using "vosotros/vosotras/vuestro/tu/tus." This approach creates a more direct and personal connection with the audience.
+
+Avoid using “usted/ustedes” in the Spanish market.
+
+✅Nuestro soporte técnico resolverá cualquier incidencia"
+
+✅ Personaliza tu experiencia en la plataforma.
+
+❌ El usuario puede experimentar problemas si no actualiza la aplicación.
+
+❌ Ha sido (usted) contactado por nuestro servicio técnico.
+
+❌ Su (usted) cuenta ha sido modificada con éxito.

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

@@ -0,0 +1,11 @@
+## Sourcing
+
+## Malt Open
+
+## Projects
+
+## Compliance
+
+## Payment
+
+## Insights

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

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

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

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

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

@@ -0,0 +1,7 @@
+### You will find :
+
+- Stickers
+- Clothing
+- Desk tools
+- Tote bag
+- Water bottle & opener

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

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

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

@@ -0,0 +1,15 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "MALTERIE HQ 2024",
+  "slug": "malterie-hq-2024",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 5596206,
+  "pageUid": "5596206",
+  "fetchedAt": "2026-07-15T08:24:45.828Z",
+  "tabs": [
+    "Paris office pictures"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/malterie-hq-2024/",
+  "extraction": "zeroheight-api"
+}

package/dist/doc/zeroheight/guidelines/5596206/paris-office-pictures.md

@@ -0,0 +1 @@
+

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

@@ -0,0 +1 @@
+Layout funnel is a set of UI components and pages designed to guide a user through a specific, multi-step process.

package/dist/doc/zeroheight/guidelines/5961423/desktop.md

@@ -0,0 +1,51 @@
+## Funnel
+
+#### When should I use a funnel layout?
+
+The funnel layout is used when you want to push the user in a step-by-step action.
+
+The main navigation is not displayed and the user cannot leave the page via the header
+
+### 💻 Desktop funnel - With Sidebar
+
+### 💻 Desktop Medium funnel - Full centered
+
+#### Size
+
+| Name of slot | Device | Size of container |
+| Main content | Desktop | **672 px** |
+### 💻 Desktop Large funnel - Full centered
+
+#### Size
+
+| Name of slot | Device | Size of container |
+| Main content | Desktop | **1024 px** |
+### 💻 Desktop M funnel Full centered - One CTA
+
+## Full-Width Dialog
+
+| Name of slot | Device | Size of container | Max width |
+| Main content | Desktop | **672 px** |  |
+### 💻 Full Width Dialog - Sidebar Dialog
+
+### 💻 Full Width Dialog - Full Dialog
+
+## Layout Fluid - 100%
+
+### Type of content
+
+| Name of container | Device | Size of container | Margin type |
+| Fluid | Desktop | 100% | 32px |
+### ➡️  Layout Fluid 100%
+
+## Layout Fixed - 100%
+
+### Type of content
+
+| Name of container | Device | Size of container | Margin type |
+| Fixed | Desktop | 1024px | % |
+### 💻 Layout with Right side bar
+
+### 💻 Layout with Center Content
+
+## Related

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

@@ -0,0 +1,18 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Funnels",
+  "slug": "funnels",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 5961423,
+  "pageUid": "5961423",
+  "fetchedAt": "2026-07-15T08:24:45.763Z",
+  "tabs": [
+    "Overview",
+    "Usage",
+    "Desktop",
+    "Tablet & Mobile"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/funnels/",
+  "extraction": "zeroheight-api"
+}

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

@@ -0,0 +1,54 @@
+![Funnel example](/uploads/QbS99ehAw58JeDOOl2FNOw.png)
+
+## Definition
+
+A funnel layout is a design pattern that is used to guide users through a series of steps or stages, with the goal of converting them into customers or users. The layout typically consists of a series of screens or pages that are arranged in a linear or step-by-step fashion, with each screen or page representing a different stage in the user's journey. The layout is typically used to guide users through a process such as signing up for a service, making a purchase, or completing a registration form.
+
+Is important to consistently add the appropriate level of Joy in your funnels, and choose the right component for it.
+
+For that you can use the success education documentation
+
+## Funnel composition
+
+### Header
+
+Here are 4 different type of headers for the funnel :
+
+- Save and quit
+- Quit
+- With Logo
+- With CTA
+
+## Stepper
+
+### Scrolling
+
+#### Usage
+
+If the user need to scroll, the header and the time stay sticky
+
+### Footer
+
+#### States
+
+### Behavior
+
+#### First Step
+
+In the first step of the funnel, we do not display the back button
+
+#### Mandatory
+
+During a mandatory step, the next button is disabled.
+
+The button becomes active only if the user has filled in all the required fields
+
+#### Optional
+
+When a step is optional, the Next button is replaced by the "skip this step" action
+
+Once the user has filled in at least one of the fields (input, card, dropdown...), the button changes to "Next".
+
+## Example
+
+## Related

package/dist/doc/zeroheight/guidelines/5961423/tablet-mobile.md

@@ -0,0 +1,17 @@
+## Mobile
+
+### Type of content
+
+| Name of container | Device | Size of container | Margin type |
+| Fluid | Mobile | 100% | 16px |
+### CTA examples
+
+## Tablet
+
+### Type of content
+
+| Name of container | Device | Size of container | Margin type |
+| Fluid | Tablet | 100% | 24px |
+### Navigation
+
+### Funnel

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

@@ -0,0 +1,25 @@
+## Funnel header
+
+A focused navigation bar designed to guide users through a multi-step process by minimizing distractions and providing clear exit or progression paths.
+
+### Usage
+
+**The Funnel Header is used specifically when:**
+
+- **Conversion is the goal:** Standard site navigation is removed to prevent users from accidentally leaving the funnel.
+- **Progress is non-linear:** Users need the ability to go back to previous steps or save their progress for later.
+- **Exit intent is managed:** Specific exit points (Cross or "Save and Quit") are provided to ensure data is handled correctly when a user leaves.
+
+Manage the header's visibility by toggling the following elements based on the funnel stage:
+
+| **Variant** | Components | Recommended for |
+| Minimal | Logo alone | Splash screens or the very first step of a funnel |
+| Standard Exit | Logo + Cross | Middle steps where the user needs a quick "cancel" option |
+| Progressive | Back + Cross | Multi-step forms where users may need to correct previous input |
+| Actionable | Back + CTA + Cross | Advanced steps requiring a specific secondary action (e.g., "Skip" or "Help") |
+| Safe Exit | Save and Quit | Long funnels where user data retention is a high priority |
+## Do/don't
+
+- Do: Use the Cross for "Close": The Cross should represent a "discard" or "close" action, whereas "Save and Quit" should explicitly imply data is stored.
+- Don't: Don't include a Search bar: Any element that leads the user away from the funnel steps should be omitted.
+- Do: Don't overstuff the CTA: Use only one primary or ghost button in the header. If you need more actions, they belong in the page footer.

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

@@ -0,0 +1 @@
+In addition to our main brand identity, we have developped some secondary ones dedicated to specific topics.

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

@@ -0,0 +1,9 @@
+## Super Malters
+
+We use 3 colors when it's about Super Malters: Malt red, yellow and blue.
+
+### Main
+
+### Dark
+
+### Light

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

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

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

@@ -0,0 +1 @@
+## Components

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

@@ -0,0 +1,20 @@
+## Components
+
+## How to use it
+
+If your need fits with all the recommendations listed above then specify it during the design phase.
+
+Check the playground directly in the storybook
+
+## Style
+
+| Element | Border-Radius | Color |
+| Background | 8px | `$-joy-color-neutral-gray-2` |
+| composant | 8px | `$-joy-color-neutral-gray-3` |
+## Animation
+
+![Skeleton in production](/uploads/hAuZpvN-7oeqwwuurc39mg.gif)
+
+![image](/uploads/bT-4IoRSW3RyLhV4nCHOSw.gif)
+
+## Related

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

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