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

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

@@ -0,0 +1,27 @@
+### **Currency (€ £ $)**
+
+- Place the currency symbol before the amount.
+- Don't add a space between the symbol and the amount.
+
+- Do: €300
+£300
+$300
+- Don't: € 300
+£ 300
+$ 300
+300€
+300£
+300$
+
+### **Numbers**
+
+- **Use digits** instead of writing the word.
+- Use English format with a comma to separate thousands and hundreds and a full stop before decimals.
+- One to nine are written as words, 10 and up as digits.
+- If in a visual, stick to digits.
+
+### **Phone numbers**
+
+- Use the plus sign (*+*) then the country code and drop the first *0*.
+
+✅  +33 6 2 34 56 78

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

@@ -0,0 +1,55 @@
+### Currency (€ £ $)
+
+- Always write the amount, then a non-breaking space, then the currency symbol.
+
+**DO**
+
+300 €
+
+300 £
+
+300 $
+
+**DON’T**
+
+300€
+
+300£
+
+300$
+
+€ 300
+
+€300
+
+$ 300
+
+### Numbers
+
+- One to nine are written as words, 10 and up as digits.
+- If in a visual, stick to digits.
+- Use French format with a non-breaking space to separate thousands and hundreds and a comma before decimals.
+
+**DO**
+
+Vous recevrez votre paiement d’ici deux jours.
+
+Nous avons trouvé 1 524 profils de freelances correspondant à cette recherche.
+
+**DON’T**
+
+Vous recevrez votre paiement d’ici 2 jours.
+
+Nous avons trouvé 1524 profils de freelances correspondant à cette recherche.
+
+### Phone numbers
+
+Use the plus sign (+) then the country code and drop the first 0.
+
+**DO**
+
++33 6 21 34 56 78
+
+**DON’T**
+
+0621345678

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

@@ -0,0 +1,36 @@
+### Currency (€ £ $)
+
+- Place the currency symbol AFTER the amount.
+- Add a space between the symbol and the amount
+
+✅ Do
+
+- 300 €
+- 300 £
+- 300 $
+
+❌ **Don't**
+
+- € 300
+- £300
+- 300$
+
+### Numbers
+
+- Use digits instead of writing the word.
+- Thousands are separated by a dot.
+- One to nine are written as words, 10 and up as digits.
+- In visuals, stick to digits.
+- In connection with unit symbols, for example % or €, write numbers as digits.
+- 
+- ✅ 1.000
+- ✅ 123.456.000
+- ✅ Zehn Teammitglieder
+
+✅ 10 %
+
+### Phone numbers
+
+Use the plus sign (+), then the country code and leave out the first 0.
+
+✅ +49 172 12345678

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

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

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

@@ -0,0 +1,40 @@
+### Currency (€ £ $)
+
+- Symbol’s position: Place the currency symbol after the number and separated by a space. This is a common practice in many formal texts in Spanish.
+- Add a space between the currency symbol and the amount.
+
+✅ 300 €
+
+✅ 300 £
+
+✅ 300 $
+
+❌ €300
+
+❌ £300
+
+❌ $300
+
+❌ € 300
+
+❌ £ 300
+
+❌ $ 300
+
+### Numbers
+
+- Use figures instead of words for numbers.
+- Use the Spanish format for numbers, with a period to separate thousands and a comma for decimals.
+- For visual material (infographic, ads, etc.), always use figures.
+
+✅ 1, 2, 3, 10, 100, 1.000, 1.500,50
+
+❌ uno, dos, tres, diez, cien, mil, mil quinientos y cincuenta
+
+### Phone numbers
+
+- Use the plus sign (+) followed by the country code and remove the first two zeros.
+
+✅ +34 912 345 678
+
+❌+0034 9 1 2 34 5 6 78

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

@@ -0,0 +1,33 @@
+Use everyday words. Be professional, but use modern day language. Don’t be overly formal.
+
+It goes without saying that translations need to be free from spelling and grammar mistakes. Some great resources to help with this are:
+
+- [https://woordenlijst.org/](https://woordenlijst.org/)
+- [https://www.onzetaal.nl/](https://www.onzetaal.nl/)
+- [https://taaladvies.net/](https://taaladvies.net/)
+- [https://www.vandale.nl/](https://www.vandale.nl/)
+- [https://www.vlaanderen.be/team-taaladvies/taaladviezen](https://www.vlaanderen.be/team-taaladvies/taaladviezen)
+
+### Key terminology
+
+Listed below are examples of Malt’s key Dutch terms as well as words we do not use at Malt. For a full overview of all Malt-specific terminology, please refer to the [Malt glossary](https://docs.google.com/spreadsheets/d/1ixntyNBsjhXJrXdjAOR9_5UA4KUipnZpaGTmawk-0eY/edit#gid=0).
+
+✅ Opdracht
+
+❌ Project, missie, taak
+
+✅ Opdrachtgever
+
+❌ Klant
+
+✅ Freelancer
+
+❌ ZZP’er, zelfstandige, eigen baas
+
+✅ Sollicitatie
+
+❌ Kandidatuur, aanvraag
+
+✅ E-mailadres
+
+❌ E-mail, email

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

@@ -0,0 +1,82 @@
+#### Centre
+
+Malt prefers the U.K. spelling.
+
+Do not use "Center".
+
+#### Connection
+
+Malt prefers the U.K. spelling.
+
+**Do not use "Connexion".**
+
+#### E.g.
+
+**Do not use: eg, eg., i.e., ie**
+
+#### Email
+
+**Do not use: e-mail, e mail, mail, etc.**
+
+#### Enrol
+
+Malt prefers the U.K. spelling.
+
+**Do not use "enroll".**
+
+#### Etc.
+
+**Do not use "etc" (without the period).**
+
+#### Internet
+
+Use "internet" - without capital letters - as per EN-UK guidelines.
+
+#### Labour
+
+Malt prefers the U.K. spelling.
+
+**Do not use "labor".**
+
+#### Last name
+
+**Do not use "surname" or "family name".**
+
+#### Log in
+
+When spelled as 2 words, "log in" serves as a verb.
+
+#### Login
+
+When spelled as a single word, "login" serves as a noun or an adjective.
+
+#### Onsite
+
+Not "on site" or "on-site".
+
+- Do: null
+- Don't: null
+
+#### Programme
+
+Use the UK preferred spelling "programme" - unless it's used in a computing context, then use "program".
+
+#### Sign in
+
+When spelled as 2 words, "sign in" serves as a verb.
+
+#### Sign-in
+
+When spelled as a single word, "sign-in" serves as a noun.
+
+#### Sign up
+
+When spelled as 2 words, "sign up" serves as a verb.
+
+#### Sign-up
+
+When spelled as a single word, "sign-up" serves as a noun or an adjective.
+
+#### Web
+
+Use "web" - without capital letters - as per EN-UK guidelines.

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

@@ -0,0 +1,15 @@
+#### Email
+
+Write “email”
+
+Do not use: e-mail, e mail, mail, courriel, etc.
+
+#### Etc.
+
+Write “etc.”
+
+Do not use "etc" (without the period).
+
+#### Web
+
+Write "web" without capital letters.

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

@@ -0,0 +1,39 @@
+### Alltagssprache verwenden
+
+Use everyday language
+
+Examples:
+
+- ❌zusätzlich 		→ ✅ extra, weitere
+- ❌empfehlen 		→ ✅ mitteilen
+- ❌beginnen 		→ ✅ starten
+- ❌gewährleisten 	→ ✅ einhalten
+- ❌folglich 		→ ✅ also
+- ❌in Bezug auf 	→ ✅ für / wegen
+- ❌im Falle von 	→ ✅ wenn
+- ❌etcetera (etc.) 	→ ✅ und so weiter (usw.)
+- ❌einloggen 		→ ✅ anmelden
+
+### Key terminology
+
+Listed below are examples of Malt’s key German terms as well as words we do not use at Malt. For a full overview of all Malt-specific terminology, please refer to the [Malt glossary](https://docs.google.com/spreadsheets/d/1ixntyNBsjhXJrXdjAOR9_5UA4KUipnZpaGTmawk-0eY/edit#gid=0).
+
+✅ Freelancer
+
+❌ Freiberufler, Malt-Nutzer
+
+✅ Auftraggeber
+
+❌ Kunde
+
+✅ Projekt
+
+❌ Mission, Auftrag
+
+✅ Angebot
+
+❌ Kostenvoranschlag
+
+✅ Leistungsbericht
+
+❌ Tätigkeitsbericht, Aktivitätsbericht

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

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

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

@@ -0,0 +1,102 @@
+### Anglicism
+
+- Orthographic adaptation in Spanish: If the anglicism has been adapted to Spanish, it should be written according to Spanish spelling rules.
+- Italic: When using an anglicism that has not been fully adapted to Spanish, it is recommended to write it in italics to highlight it from the rest of the text.
+- Avoiding redundancies: For most cases, an anglicism should not be used when there is an equivalent term in Spanish that is widely known and used.
+- Consistency: Consistency should be maintained in the use of anglicisms within the same text, avoiding mixing adapted forms with original forms that are not adapted.
+
+✅ Usaremos un *software* especializado para el proyecto.
+
+✅ El *marketing* digital es esencial para el éxito de cualquier negocio hoy en día.
+
+❌ Necesitamos comprar más mouses para las computadoras.
+
+❌ El meeting se pospuso para mañana.
+
+### Controversial terms
+
+Find below a list of Spanish terms that might present doubts in use.
+
+**Acerca de**
+
+✅ Hablaremos acerca de los nuevos proyectos de la empresa.
+
+❌ Hablaremos a cerca de los nuevos proyectos de la empresa.
+
+**Basado** **en**
+
+✅ El informe está basado en datos recopilados durante el último trimestre.
+
+❌ El informe está en base a datos recopilados durante el último trimestre.
+
+**De acuerdo**
+
+✅ Estoy de acuerdo con las conclusiones de la reunión.
+
+❌ Estoy deacuerdo con las conclusiones de la reunión.
+
+**Dónde**
+
+✅ ¿Dónde podemos encontrar esa información?
+
+❌ ¿Donde podemos encontrar esa información?
+
+**Por qué**
+
+✅ No entiendo por qué tomaste esa decisión.
+
+❌ No entiendo porque tomaste esa decisión.
+
+**Haber**
+
+✅ Deberías haber llegado temprano.
+
+❌ Deberías abe llegado temprano.
+
+**Ahí**
+
+✅ El libro está ahí, en la mesa.
+
+❌ El libro está ahi, en la mesa.
+
+**Bien**
+
+✅ La presentación salió muy bien.
+
+❌ La presentación salió muy bién.
+
+**Hubiera**
+
+✅ Si hubiera sabido antes, habría tomado otra decisión.
+
+❌ Si ubiera sabido antes, habría tomado otra decisión.
+
+**Vaya**
+
+✅ Vaya, qué sorpresa verte aquí.
+
+❌ Baya, qué sorpresa verte aquí.
+
+**Haya**
+
+✅ Espero que haya suficiente comida para todos.
+
+❌ Espero que halla suficiente comida para todos.
+
+**Hecho**
+
+✅ Ya está hecho, no te preocupes más por eso.
+
+❌ Ya está echo, no te preocupes más por eso.
+
+### Lenguaje directo y positivo
+
+Whenever possible, use direct and positive language to communicate with users. Employing clear and affirmative language can enhance the user experience and facilitate understanding of instructions or messages.
+
+✅ Haz clic aquí para continuar.
+
+❌ Para continuar, sería ideal que le des clic aquí.
+
+✅ Envíanos tu solicitud para empezar.
+
+❌ Si quieres, puedes enviarnos tu solicitud para empezar.

package/dist/doc/zeroheight/guidelines/5193537/adding-joy.md

@@ -0,0 +1,124 @@
+### Where to add Joy?
+
+There are 3 steps to adding the right level of Joy at the right time in your content.
+
+🧚🏻 **JOY = PERSONA + USER JOURNEY + USER EMOTION + CONTENT TYPE.**
+
+#### 1/ Persona
+
+Depending on your persona (Client or Freelancer), you can afford to be more or less bold and ambitious with your *Joy-ful* content.
+
+- Client: Use a slightly more sober, straight-forward tone.
+- Freelancer: Tone it up a little.
+
+#### 2/ User journey & emotions
+
+How your users are feeling when they encounter your copy matters!
+
+Leverage your OBSERVE and UNFOLD user research activities to understand their emotions throughout your journey to determine what level of Joy is appropriate at each step.
+
+- **Step 1 - Map out the user journey**
+
+Consult or build a user journey map based on your user research. Make sure it includes: the main steps of the journey, the actions taken by the user, and the main touch points with the product.
+
+This will help you identify precisely what the user experienced before coming across your content.
+
+![Ex: (Simplified) Service level upgrade funnel](/uploads/PAP_cmZ8TgDibzRvJ9Ko0Q.png)
+
+💡 Different formats of user journey maps exist. Feel free to use Miro’s or [La Grande Ourse](https://lagrandeourse.design/ressources/)’ free templates.
+
+- **Step 2 - Understand the user's emotions**
+
+Through surveys, interviews or CC feedback, connect what the user *does* and *says* to what they *feel*. Add a section “Emotions” or “User feelings” to your journey map.
+
+You can also leverage the user’s Needs and Pains to identify their actual feelings rather than projecting your own expectations.
+
+![Ex: (Simplified) Service level upgrade funnel + users verbatim and emotions recovered during UR.](/uploads/f5TX91PXwUBU5Hf3f2877w.png)
+
+💡 Use [Plutchik’s wheel of emotions](https://www.6seconds.org/2022/03/13/plutchik-wheel-emotions/) to connect the user’s emotional state to the emotions we want them to feel.
+
+![image](/uploads/kW4-5trxifGHoCyWkny2cQ.png)
+
+- **Step 3 - Assess the level of Joy**
+
+Now that you have a better understanding of your user's feelings and your objectives are clear, identify the key moments in your experience.
+
+Then, depending on the intensity of the emotion and the gap between the actual emotion and the expected emotion, you can choose to add more or less Joy to your content.
+
+☝️ In the previous example, we identified 3 negative and 1 potentially negative emotions toward the product:
+
+- annoyance/boredom
+- surprise/annoyance
+- anger
+- apprehension.
+
+We want to turn these into positive emotions:
+
+- trust
+- interest/anticipation
+- acceptance/joy
+- interest/serenity
+
+![Ex: (Simplified) Service level upgrade funnel + target emotions and joy opportunities](/uploads/2G0kwsNwW410mDh5DeEDFA.png)
+
+💡 Notice that to obtain the same type of emotion twice, we may not necessarily use the same level of Joy. It depends on the initial emotion and the stage of the user journey.
+
+#### 3/ Content types
+
+Different types of content call for different levels of Joy. The number of 🔥 indicates the level of Joy you can add. ☝️ Each of these types must be considered on a case-by-case basis.
+
+**Confirmation & success** 🔥🔥🔥
+
+Empower your users, acknowledge their efforts, and congratulate them on achieving important milestones (account creation, new opportunity, etc.).
+
+- **Title:** Acknowledge and show enthusiasm for the task that has just been completed.
+- **Subtitle (optional):** Adopt a more neutral tone to add further detail or describe a possible next step.
+- **CTA (optional):** Keep it simple and straightforward.
+
+![image](/uploads/pODRcuQrlCSiU9MiOb-2Ig.png)
+
+**Onboarding** 🔥🔥
+
+Onboardings offer an opportunity to convert or engage our users. Be inspiring.
+
+- **Title**: Use creative titles to get your users hooked. Find the right balance between catchy and informative.
+- **Subtitle**: Explain the feature in the subtitle or body. Focus on the main value proposition for this type of user, in this very context. 💡Customise your product tours to your user’s interest if possible.
+- **CTA**: Be enticing and clear about the next step to take. Use Malt’s specific terminology.
+
+![image](/uploads/StWE57hu0_2ftHD2bVr79w.png)
+
+- **Empty states** 🔥🔥
+
+Whether for first-time use or a cleared task list, make sure to leverage empty states to highlight a feature’s value proposition and promote its usage.
+
+- **Title:** Be bold and make this screen more lively and conversational. Feel free to add a touch of humour. Pair up with a cool illustration for extra Joy.
+- **Subtitle (optional):** Tone down the Joy a little to ensure that the information is properly communicated.
+- **CTA (optional):** Whenever possible, avoid neutral and generic CTA. Once again, try to highlight the benefits of moving on to the next step.
+
+![image](/uploads/5oB7Z0_BGEWhpytqdIwHZA.png)
+
+![image](/uploads/VXIWM8hRBRg5fi96Ek0NyQ.png)
+
+- **Loaders** 🔥
+
+Identify any waiting points where **you can't afford to lose your users' attention** and invest some time to ditch the generic loader. This little detail can matter in times of uncertainty.
+
+Be informative and reassuring about the situation. Keep the tone light and conversational.
+
+![image](/uploads/eEkSxfWoW5t5080a5qrmFA.png)
+
+![image](/uploads/kLH_12-Kk-zHJtCT8w62jg.png)
+
+![image](/uploads/W3adid4cMQZM1_BhC9tB5Q.jpg)
+
+- **Non-critical errors & interruptions** 🔥
+
+⚠️ The following guidelines do not apply to critical errors damaging the user exp.
+
+Some interruptions or errors don’t need to be dramatic. Seize this opportunity to improve the experience and the product’s reputation. While helping the user solve their issue, be informative and reassuring about the situation.
+
+- **Title**: Be clear about the situation without adding unnecessary or technical details.
+- **Subtitle**: Provide the user with an explanation of what went wrong (if possible) and redirect them to a solution. Keep the tone light and conversational.
+- **CTA:** Remain clear and straight-forward.
+
+![image](/uploads/NMdA4JY_-CgneGLofLAPsQ.png)

package/dist/doc/zeroheight/guidelines/5193537/additional-resources.md

@@ -0,0 +1,5 @@
+### Unfold
+
+### Steal
+
+### Execute

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

@@ -0,0 +1 @@
+Practical guidelines to help you identify, structure and create joyful content opportunities.

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

@@ -0,0 +1,16 @@
+### What is Joy?
+
+Welcome to the realm of impactful UX content!
+
+Here, the art of writing with emotions plays a key role in engaging and [priming the users](https://thedecisionlab.com/biases/priming), facilitating goal completion - at the screen level, the funnel level, and beyond.
+
+Within this landscape, Joy emerges as a significant factor, defined by four pillars that shape the emotional tone of the content. Understanding when and where to infuse Joy, and determining the appropriate level, involves considering essential factors:
+
+- the persona of the audience
+- the user journey
+- the user's emotional state
+- the nature of the content - including its components.
+
+🧚🏻 **JOY = PERSONA + USER JOURNEY + USER EMOTION + CONTENT TYPE.**
+
+Let’s see how it’s done 🔍

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

@@ -0,0 +1,18 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Joyful content",
+  "slug": "joyful-content",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 5193537,
+  "pageUid": "5193537",
+  "fetchedAt": "2026-07-15T08:24:45.816Z",
+  "tabs": [
+    "Introduction",
+    "Pillars",
+    "Adding Joy",
+    "Additional resources"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/joyful-content/",
+  "extraction": "zeroheight-api"
+}