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

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

@@ -0,0 +1,16 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "To display",
+  "slug": "to-display",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 4845145,
+  "pageUid": "4845145",
+  "fetchedAt": "2026-07-15T08:24:45.907Z",
+  "tabs": [
+    "Informative posters",
+    "Kitchen labels"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/to-display/",
+  "extraction": "zeroheight-api"
+}

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

@@ -0,0 +1,3 @@
+## Logo
+
+## Signage

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

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

package/dist/doc/zeroheight/guidelines/4845148/final-results.md

@@ -0,0 +1 @@
+

package/dist/doc/zeroheight/guidelines/4845148/graphic-materials.md

@@ -0,0 +1 @@
+

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

@@ -0,0 +1,16 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Vitro",
+  "slug": "vitro",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 4845148,
+  "pageUid": "4845148",
+  "fetchedAt": "2026-07-15T08:24:45.920Z",
+  "tabs": [
+    "Graphic materials",
+    "Final results"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/vitro/",
+  "extraction": "zeroheight-api"
+}

package/dist/doc/zeroheight/guidelines/4845149/business-cards.md

@@ -0,0 +1,3 @@
+You'll find the template to create your business cards [here.](https://www.canva.com/design/DAFklO087jQ/hQ5yiZWggMRMyVSjLB8wtg/view?utm_content=DAFklO087jQ&utm_campaign=designshare&utm_medium=link&utm_source=sharebutton&mode=preview)
+
+![image](/uploads/b9SUw2_geoCuPIkgi06NFA.png)

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

@@ -0,0 +1,16 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Office supplies",
+  "slug": "office-supplies",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 4845149,
+  "pageUid": "4845149",
+  "fetchedAt": "2026-07-15T08:24:45.837Z",
+  "tabs": [
+    "Mugs",
+    "Business cards"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/office-supplies/",
+  "extraction": "zeroheight-api"
+}

package/dist/doc/zeroheight/guidelines/4845149/mugs.md

@@ -0,0 +1 @@
+

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

@@ -0,0 +1 @@
+The purpose of the Figma "**master**" files is to centralize all projects that have been finalized and developed in production.

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

@@ -0,0 +1,28 @@
+## Introduction
+
+This ensures that figma models are always up to date and saves time when an improvement project is underway. We always start from an up-to-date base with the latest components and tokens.
+
+We have 2 master files :
+
+- Freelance - It includes all project related to the freelance tribes
+- Client - It includes all project related to the freelance tribes
+
+### When should I Updating the Master
+
+Once your project has been developed ✅ and put into production, take the main screens and add them to the masters file corresponding to your Tribe.
+
+### How should I update the master
+
+1. Select the masters file corresponding to your Tribe
+2. Duplicate the template page if your project does not exist yet or select the corresponding page
+3. Add the main flow screens and add the link to the original figma file for the project
+
+### Who is responsible to update the master ?
+
+#### **The Design system Manager** :
+
+He/She must ensure that my file is up to date and properly organised, and is responsible for the master file Transverse
+
+#### Designers :
+
+Designers are responsible for their own scope and must update the master themselves at the end of each project.

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

@@ -0,0 +1,13 @@
+{
+  "source": "https://zeroheight.com/6bf479565/p/811367-master-figma-files",
+  "title": "Master Figma Files",
+  "slug": "master-figma-files",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 4859603,
+  "pageUid": "4859603",
+  "fetchedAt": "2026-07-15T08:24:45.829Z",
+  "tabs": [],
+  "imagesPath": "packages/core-vue/static/zeroheight/master-figma-files/",
+  "extraction": "zeroheight-api"
+}

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

@@ -0,0 +1 @@
+

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

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

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

@@ -0,0 +1,3 @@
+On the following pages, we will explain how to apply the Malt look and feel across our brand collateral, following our brand update in 2023.
+
+It is very important to follow these guidelines concerning the application of brand assets, to ensure a consistent representation of the brand at all touch points.

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

@@ -0,0 +1,55 @@
+## The Malt Brand
+
+Malt is what you get when two entrepreneurs, Hugo and Vincent, passionate about the latest technological and digital developments, unite.
+
+Their ambition: to change the way we work by transforming the market for intellectual services with a transparent business platform and the emergence of a community of freelance experts.
+
+They met in 2012 to discuss a common issue that companies were facing: the difficulty to find freelancers to help them move their projects forward. The following year, they founded Malt together.
+
+Today, Malt counts 550,000 freelancers and 70,000 registered companies in Europe.
+
+Since 2013, we’ve been on a mission: to create a world where everyone is free to choose the best people to work with. A world of opportunities, giving people flexibility and freedom.
+
+Every day, we connect freelancers and organizations. We enable easier, better choices. Connecting fast with the right talent every time. Raising the bar on teamwork. Bringing new perspectives to the world of work.
+
+We also offer companies and freelancers a sense of community, great relationships and transparency, by enabling them to work directly together, in just a more natural and efficient way. We try to make the recruiting world more human, positive and empowering.
+
+At Malt, we claim to choose choice. We can choose to work the way we want to. With the people we want to. It’s time to bring more choice to work.
+
+**Choose Choice.**
+
+## Mission
+
+### "Give people the freedom to choose who they work with."
+
+Our mission is a breakdown of what we will do to achieve our vision. It captures the optimistic way we think about work and helps guide the decisions we make.
+
+## Vision
+
+### "To give everyone the power of choice."
+
+Our vision is an articulation of the future that we want to create. Reflecting our role in the world of work, it captures our passion for changing the way being ‘freelance’ is perceived. We use our vision to inspire action and drive every decision we make as a company.
+
+## Brand idea
+
+### "Choose Choice."
+
+Our brand idea is our shorthand to inform creative briefs and guide how we express ourselves visually and verbally. It sets our agenda for what the future of work should be.
+
+## Our Manifesto
+
+![image](/uploads/MW_YiF72QDquuMsDywjR4A.png)
+
+## Our Tone of voice
+
+### Take a stance.
+
+This principle is aimed at empowering our users and highlighting the benefits of temporary work. But this doesn’t mean we undermine the value of full-time work and long-term contracts. We never pit the options against one another or undermine different professional choices.
+
+### Keep it positive.
+
+Whether you’re a freelancer, a consultant or a client, working with Malt marks the starts of something new. As such, we build the excitement. Our messaging aims to uplift readers, demystifying the world of work and highlighting the positives.
+
+### Celebrate people.
+
+Malt wouldn’t be Malt without people. So that’s why we put them front and center, spotlighting their different stories and clearly laying out how we can help them along.

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

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

package/dist/doc/zeroheight/guidelines/4946782/cover-page.md

@@ -0,0 +1,15 @@
+## Cover page
+
+Covers/thumbnails are a good way of communicating key information about a project
+
+To help you, you can check the [Figma Cover](https://joy.malt.com/6bf479565/p/1365cd-start-a-new-project/b/35637f) page
+
+![image](/uploads/_-hiW1JTDI6XO4Y6ludZ6A.png)
+
+#### Examples
+
+![image](/uploads/lk2QeJTWek4eK_DzAOnofg.png)
+
+![image](/uploads/fNI20HJp0_4dOzAd1EtulA.png)
+
+## Name you layers

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

@@ -0,0 +1 @@
+This guide outlines a systematic approach to creating and delivering high-quality design files. Learn how to structure your files for clarity, consistency, and a seamless handoff to developers.

package/dist/doc/zeroheight/guidelines/4946782/file-annotation.md

@@ -0,0 +1,15 @@
+## Annote your design with the File Management Library
+
+Remember that not only use designer use Figma, we share our project to developpers, ux writter, localisation managers, pm etc…
+
+Comments are good but not enough visible for most ouf the users
+
+It’s important to add more context sometime and annotate mockups.
+
+That why we build a wonderfull dedicated library call " 🔀 Joy - File Management Library"
+
+#### Examples
+
+![image](/uploads/X_iT8DTc7VSbJI2nOUUNMQ.png)
+
+![image](/uploads/r1ydOmWYOn3VwPZRQjZ66Q.png)

package/dist/doc/zeroheight/guidelines/4946782/layerpage-name.md

@@ -0,0 +1,32 @@
+## Name your layers
+
+Naming your layer is the key, it's the most common bad habit. We just want to craft beautiful interfaces (we are artists huhu) and don't spend time on stuff like naming buuuut in fact it is not that hard or time consuming
+
+#### Examples
+
+- Do: A perfect and simple hierarchy with proper naming 
+- Don't: Useless groups with bad names like "Group 997" 
+
+**Suggestions**
+
+Use name like
+
+- Main container
+
+- Container
+
+- Content
+
+### Plugin : How to quicly fix this
+
+"Meh my design is finished, I've got other things to do than go over each of my artboards again"
+
+## Page Naming
+
+At malt we use page name to give information and visibilty regarding the project status.
+
+See [Figma page structure](https://joy.malt.com/6bf479565/p/1365cd-start-a-new-project/t/3556e5)
+
+#### Examples
+
+![image](/uploads/5vjlDpC6ISbF3WYcPR4b4Q.png)

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

@@ -0,0 +1,19 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Creating Flawless Design Files",
+  "slug": "creating-flawless-design-files",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 4946782,
+  "pageUid": "4946782",
+  "fetchedAt": "2026-07-15T08:24:45.729Z",
+  "tabs": [
+    "Cover page",
+    "Layer/page name",
+    "Unliked styles",
+    "Organize sections",
+    "File annotation"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/creating-flawless-design-files/",
+  "extraction": "zeroheight-api"
+}

package/dist/doc/zeroheight/guidelines/4946782/organize-sections.md

@@ -0,0 +1,11 @@
+## Organize with section
+
+[Sections](https://help.figma.com/hc/en-us/articles/9771500257687-Organize-your-canvas-with-sections) in Figma design are a top-level element on the canvas by default. Sections can contain all layer types, including other sections, but cannot be contained within frames or groups.
+
+At malt we don't have (yet) a specific convention about how to use section, but here is some very good examples
+
+#### Examples
+
+![image](/uploads/d_2IqYljRc6ymiygyZO3MQ.png)
+
+![image](/uploads/kVOkFHgbCvd2nW-0kyeyOw.png)

package/dist/doc/zeroheight/guidelines/4946782/unliked-styles.md

@@ -0,0 +1,24 @@
+## Unlinked styles
+
+I'm not going to explain what [styles](https://help.figma.com/hc/en-us/articles/360039238753-Styles-in-Figma) are or their importance, but it's very important to make sure that when you deliver a project, the colours, shadows and text styles are all those of the system design.
+
+**Working on a project without using styles has the following impact: **
+
+- screens cannot be updated using the design system
+
+- Does not display the correct information in the dev mod
+
+- Possibility of using colours or text styles that the design system does not use
+
+#### Examples
+
+- Do: null
+- Don't: null
+- Do: 
+- Don't: 
+- Do: 
+- Don't: 
+
+### Plugin : How to quicly fix this
+
+"Meh my design is finished, I've got other things to do than go over each of my artboards again"

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

@@ -0,0 +1 @@
+As design system manager

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

@@ -0,0 +1,71 @@
+![image](/uploads/gfzc83hhdXqwr4HtB3uAVg.png)
+
+## 1- Introduction
+
+Book a slot in the newcomer planning : ⏰ 30 minutes
+
+Purposes:
+
+- Joy presentation
+- Stickers
+- Workflow & Team Meeting
+- [Joy Documentation](https://joy.malt.com/)
+
+Resources that the newcomer has to read  -> [GET STARTED DESIGN ](https://zeroheight.com/6bf479565/p/28b9ba)
+
+## 2- Meetings
+
+Meetings related to the Design system where you need to add newcomers
+
+| Meeting | 👉 What | 👥 Who | 📅  When (depending of the need |
+| 1:1 | Meeting to discuss, review, support and review the ongoing work. As ds manager, you act like a coach | Solo Designer | Weekly placeholder |
+| DS Review | Updating the team about DS big update and roadmap, a placeholder for workshop/retro | All designer | Bi-Monthly |
+| DS Crit | Weekly Design crit' | Tribe designer | Weekly |
+## 2- Communication
+
+Communication channels where you need to add newscomers
+
+| Type | Canal | Purpose | Note |
+| Slack | [#3-guild-design-system](https://maltcommunity.slack.com/archives/CR1LXCKLY) | Everything related to the Design system of Malt |  |
+| Slack | #3-joy-figma-bot | Dedicated chan In which Figma library release notes are published |  |
+| Slack | #product-designers | Dedicated chan with all the product design team / Ops team |  |
+| Slack | #1-product-team | I've no idea, we already have too many channels. Don't ask me |  |
+| Mail | design@malt.com | Email group dedicated to the product design team / Ops team | Ask to Caroline |
+## 4- Tools
+
+| Tool | What | Owner | Note |
+| [Figma](https://joy.malt.com/6bf479565/p/43f45f-how-to-onboard-a-new-designer-on-joy/t/256693) | Main Design tool | DS Manager (Ex Antoine Deshoux) | Be careful of the permission |
+| [1password](https://joy.malt.com/6bf479565/p/43f45f-how-to-onboard-a-new-designer-on-joy/t/45e784) | Password manager | [IT Team](https://maltcommunity.slack.com/archives/C03KUA75NJ0) | See with IT team if issues |
+| Hotjar | Heatmap / ux tool | [Caroline](https://maltcommunity.slack.com/archives/D036Q0VFTB8) |  |
+| [https://saasinterface.com/](https://saasinterface.com/) | Benchmarktool |  | Login available in 1password |
+| [mobbin.com](https://mobbin.com) | Benchmarktool |  | Login available in 1password |
+### Figma
+
+Add the newcomer is the `**Joy - design system**` team
+
+⚠️  Only give "can view" rights, not edit
+
+![image](/uploads/RDF87JZQ8gI4pqQZOPT40Q.gif)
+
+Add the newcomer is the `**Freelancer - Tribe**` team
+
+Add the newcomer is the `** Client - Tribe**` team
+
+### 1password
+
+Invite newcommer in the `**Shared - design tool**` folder
+
+![image](/uploads/fMnWe2S_TRpKzyGaEB7AtA.png)
+
+## 5- Exercice Figma
+
+Find a quick exercise to do on Figma so that the designer can get to grips with figma libraries.
+
+Examples of exercice:
+
+- Rebrand an old page
+- Replicate an page in product
+- Build a simple contact form
+- Build a simple profil page
+
+If you have question please ask in [#design-ops-team](https://maltcommunity.slack.com/archives/C04TDM9RTA8)

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

@@ -0,0 +1,13 @@
+{
+  "source": "https://zeroheight.com/6bf479565/p/43f45f-how-to-onboard-a-new-designer-on-joy",
+  "title": "How to onboard a new designer on Joy",
+  "slug": "how-to-onboard-a-new-designer-on-joy",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 4951086,
+  "pageUid": "4951086",
+  "fetchedAt": "2026-07-15T08:24:45.783Z",
+  "tabs": [],
+  "imagesPath": "packages/core-vue/static/zeroheight/how-to-onboard-a-new-designer-on-joy/",
+  "extraction": "zeroheight-api"
+}

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

@@ -0,0 +1 @@
+This DoD document defines the basics criteria a design must meet before it is considered complete. It ensures all design work is high-quality, consistent, and ready for development.

package/dist/doc/zeroheight/guidelines/4951250/how-to-use-it.md

@@ -0,0 +1,5 @@
+### Ready, Set, Handover with the DoD!
+
+Our built-in checklist ensures you have everything covered before you mark you project ready to dev.
As much as possible, check the boxes before you meet the ops team.
+
+Simply review the essential criteria and sail through a smooth handover.

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

@@ -0,0 +1,3 @@
+### Why the DoD?
+
+Tired of infinite back and forth with your eng. during the handover step? Your DesignOps team is happy to present a tool that will reduce your mental load: an easy/fast checklist directly in your favorite design tool to make sure you don’t forget anything and with the right level of quality

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

@@ -0,0 +1,17 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "DoD Design Ops",
+  "slug": "dod-design-ops",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 4951250,
+  "pageUid": "4951250",
+  "fetchedAt": "2026-07-15T08:24:45.735Z",
+  "tabs": [
+    "Introduction",
+    "How to use it?",
+    "Where to find it?"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/dod-design-ops/",
+  "extraction": "zeroheight-api"
+}

package/dist/doc/zeroheight/guidelines/4951250/where-to-find-it.md

@@ -0,0 +1 @@
+You can file the DoD Design Ops Template in the "Figma Managment File"

package/dist/doc/zeroheight/guidelines/4952953/content-qa.md

@@ -0,0 +1,20 @@
+Disclaimer: Try as much as possible to test in your native language and EN, at least for the happy path.
+
+### Blockers
+
+| Note | Support (To help) |
+| All content is translated into all languages. | Content Designer |
+| Dynamic entries are properly localised (fees, currencies, dates, emails, etc.). | Content Designer |
+| Links redirect to resources in the right language and for the right locale. | Content Designer |
+| The right content is triggered whenever an action is performed (ex: transactional emails). | Content Designer |
+| No error is a dead-end. | Content Designer |
+### Non blockers
+
+| Note | Support (To help) |
+| The live content matches the validated content, without grammar or spelling mistakes. | Content Designer |
+| Any terminology update has been implemented on legacy content as well. | Content Designer |
+| The [level of Joy](https://zeroheight.com/6bf479565/p/280879-joyful-content) matches the experience, and it’s the same in all languages you’re testing. | Content Designer |
+| The meaning doesn’t change from one language to another, especially in CTAs from the happy path. | Content Designer |
+| Error messages, feedback messages (ex: snack bar), and tooltips are contextual. | Content Designer |
+| **For French** 🇫🇷: Use non-breaking spaces before “;”, “?”, “!”, and “:”. |  |
+| **For German** 🇩🇪: The tone of voice is correct (informal for freelancers, formal for clients). |  |

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

@@ -0,0 +1 @@
+QA process in product design involves systematic testing, evaluation, and validation of design elements to ensure they meet specified standards and user expectations, ultimately striving for a high-quality and user-friendly product.

package/dist/doc/zeroheight/guidelines/4952953/design-system-qa.md

@@ -0,0 +1,22 @@
+### Blockers
+
+| Type | Note | Support (To help) |
+| **Browser** | Works on different browsers (Chrome, Safari, Firefox) | DS Team |
+| **UI Quality** | All visual components display the styling that was planned (The visual quality of the component is respected) | Lead Design/DS Team |
+| **Functionality** | Make sure that you conform to the intended functionality and that the component respects this usage (The live component complies with the guidelines.) | Lead Design/DS Team |
+| **Consistency** | The components used are consistent | DS Team |
+| **Accessibility** | Ensure that the design complies with the minimum accessibility rules (colour, size, etc.). | DS Team |
+| **Responsiveness** | Check that the design works well in the different response formats (desktop, tablet, mobile) | DS Team |
+| [DoD checklist](https://zeroheight.com/6bf479565/p/2782e6-dod-design-ops) | Each checkbox of the DoD checklist is respected | Design Ops Team |
+### Non blockers
+
+| Type | Note | Support |
+| **Joy** | The level of Joy matches the experience. | Design Ops Team |
+| Interactive Elements States (Hover, Active, Disabled, etc.) | Stress-test all the interactions to ensure the developer implemented all states of buttons and links. | DS Team |
+| Animations | The micro-integrations and animations are seamlessly integrated. | DS Team |
+| Placeholders | Check if all the placeholders were implemented according to the design. | DS Team / Content Designer |
+| Interaction Type (Click, Drag, Swipe, etc.) | Test the clicks, drags, and swipes in the UI. Some might seem to be good solutions on the design phase but can prove to be annoying or just bad on the final product. Stress tests here are always recommended. | DS Team |
+| Warnings & Error States | Stress-test all the fields with wrongly inputted data, click out, close the page in the middle of an operation, click buttons, and go back and forth on the navigation. **Breaking the natural flow in various ways is important to test if the implemented error cases are enough to keep the UX in good shape.** | DS Team |
+| Feedback | Check if toast notifications, inline warnings, or any other visual signals are appearing after an action. Make sure that the correct feedback is happening whenever anything wrong occurs. | DS Team / UX Writing |
+| **Accessibility** | All audio/visual materials have alternatives (Alt text for images, captions on videos...) | DS and tech team |
+| Systems | Works on different systems  - Mac - Windows - Android - iOS | DS and tech team |

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

@@ -0,0 +1,21 @@
+![image](/uploads/QKOA3H1L-v5kQC-8JLxAhQ.png)
+
+## When do I have to do QA?
+
+Most of the time, you will do QA when one of the new features/projects is available in pre-production, synchronizing you with your team squad in order to do a proper QA.
+
+But QA is a continuous process, your responsibility as a designer is to ensure that the integration of interfaces is identical to what has been designed.
+
+You are the owner of your scope.
+
+If you find a bug in the interfaces that are not within your scope, please report it to the Slack channel that corresponds to the team.
+
+## What do I have to QA?
+
+You are the owner of the visuals and interfaces, peer with the PM, who is responsible for functional testing, your job is to list all the differences and provide solutions to the developers in charge of the features.
+
+## Where I can find the QA template?
+
+## Report Issues
+
+❗️ If the issue is related to a Joy component, Post a message in [#3-guild-design-system](https://maltcommunity.slack.com/archives/CR1LXCKLY)

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

@@ -0,0 +1,18 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "QA Design checklist",
+  "slug": "qa-design-checklist",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 4952953,
+  "pageUid": "4952953",
+  "fetchedAt": "2026-07-15T08:24:45.872Z",
+  "tabs": [
+    "Introduction",
+    "Design System QA",
+    "Content QA",
+    "QA Tooling "
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/qa-design-checklist/",
+  "extraction": "zeroheight-api"
+}

package/dist/doc/zeroheight/guidelines/4952953/qa-tooling.md

@@ -0,0 +1,3 @@
+## QA Tooling
+
+Here are some practical tools to help you carry out your QA in the best possible conditions

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

@@ -0,0 +1 @@
+Display a message when the responsive is not available on mobile

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

@@ -0,0 +1,20 @@
+![Mobile wall on app](/uploads/6-_v7KqvDxzGZTqIxjFThA.png)
+
+## Key UX Context
+
+The goal is to display a simple page redirecting the user to the desktop version with a better user experience
+
+## Why?
+
+Malt is not a mobile-first audience platform, more and more we are building complex pages with data tables with bulk actions that are too expensive to build on mobile regarding the number of users for those screen sizes.
+
+By displaying in a simple page inciting the user to continue on the desktop version, we guarantee a proper user experience and don't spend too much time and money on a mobile version with a low impact.
+
+## General guidelines
+
+### Breakpoint
+
+| **Size** | **Values** | Page display |
+| **Mobile** | < 480px | Mobile blocked page |
+| **Tablet - Desktop** | > 481px | Classic Experiences |
+![image](/uploads/eaJI8AUVBCV_N3DlQOJ6nw.svg)

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

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