@iress-oss/ids-mcp-server 6.0.0-alpha.0 → 6.0.0-alpha.1-canary-20251204014525-3f0dce4

package/generated/docs/foundations-user-experience-docs.md

@@ -1,63 +0,0 @@
-[](#user-experience)User experience
-===================================
-
-We use heuristic guidelines to assess the usability and user-centred design quality of all Iress products.
-
-[](#system-feedback)System Feedback
------------------------------------
-
-*   Always show users where they are, what just happened, and what’s possible next.
-*   Provide immediate visual and textual feedback for all actions and states.
-*   Ensure feedback is clear, contextual, and proportionate to the importance of the action.
-
-[](#language-and-mental-models)Language and Mental Models
----------------------------------------------------------
-
-*   Use user-centred language and avoid technical jargon.
-*   Follow cultural and industry conventions for colour, iconography, terminology, and layout.
-*   Align interaction patterns with real-world analogues wherever feasible.
-
-[](#control-and-forgiveness)Control and Forgiveness
----------------------------------------------------
-
-*   Make actions reversible and provide undo where errors may occur.
-*   Let users easily backtrack, edit inputs, or abandon flows.
-*   Provide escape hatches from any process without penalty.
-
-[](#standards-and-consistency)Standards and Consistency
--------------------------------------------------------
-
-*   Use consistent layout, labelling, iconography, and grammar.
-*   Reinforce expectations by placing similar elements in predictable positions.
-*   Apply colour, spacing, and visual patterns consistently across all screens.
-
-[](#error-prevention-and-recovery)Error Prevention and Recovery
----------------------------------------------------------------
-
-*   Prevent errors by anticipating misuse and validating early.
-*   Phrase error messages with clarity, empathy, and constructive suggestions.
-*   Where errors occur, explain why and how they can be resolved.
-
-[](#recognition-over-recall)Recognition Over Recall
----------------------------------------------------
-
-*   Display necessary information at the point of decision.
-*   Use visual grouping, spacing, and affordance to reveal hierarchy.
-*   Prioritise visual clarity over novelty.
-
-[](#simplicity-and-minimalism)Simplicity and Minimalism
--------------------------------------------------------
-
-*   Remove unnecessary detail—every word, element, or feature should earn its place.
-*   Design for clarity of purpose with visually distinct, semantically meaningful UI components.
-*   Use whitespace, clean alignment, and simplified flows to reduce cognitive load.
-
-On this page
-
-*   [System Feedback](#system-feedback)
-*   [Language and Mental Models](#language-and-mental-models)
-*   [Control and Forgiveness](#control-and-forgiveness)
-*   [Standards and Consistency](#standards-and-consistency)
-*   [Error Prevention and Recovery](#error-prevention-and-recovery)
-*   [Recognition Over Recall](#recognition-over-recall)
-*   [Simplicity and Minimalism](#simplicity-and-minimalism)

package/generated/docs/foundations-visual-design-docs.md

@@ -1,46 +0,0 @@
-[](#visual-design-standards)Visual Design Standards
-===================================================
-
-[](#typography)Typography
--------------------------
-
-*   Use systematic font sizing with heading scales (H1-H6)
-*   Implement consistent line heights and font weights
-*   Provide text colour hierarchies (primary, muted, success, warning, danger)
-*   Support responsive typography scaling
-
-[](#colour-system)Colour System
--------------------------------
-
-*   Maintain semantic colour meanings:
-    *   **Primary**: Main call-to-action colour with high contrast
-    *   **Success**: Positive outcomes and confirmations
-    *   **Warning**: Caution and important notices
-    *   **Danger**: Errors and destructive actions
-    *   **Info**: Neutral information and guidance
-    *   **Positive/Negative**: Financial context (buy/sell actions)
-*   Ensure all colour combinations meet accessibility contrast requirements
-*   Provide consistent hover and active state colours
-
-[](#spacing-and-layout)Spacing and Layout
------------------------------------------
-
-*   Use systematic spacing scale (xs, sm, md, lg, xl)
-*   Apply consistent gutter systems for layout components
-*   Implement responsive breakpoints for adaptive layouts
-*   Maintain proper margin and padding relationships
-
-[](#interactive-states)Interactive States
------------------------------------------
-
-*   Provide clear hover, focus, active, and disabled states
-*   Use consistent transition timing and easing
-*   Implement proper focus indicators for keyboard navigation
-*   Show loading states for asynchronous operations
-
-On this page
-
-*   [Typography](#typography)
-*   [Colour System](#colour-system)
-*   [Spacing and Layout](#spacing-and-layout)
-*   [Interactive States](#interactive-states)

package/generated/docs/foundations-z-index-stacking-docs.md

@@ -1,31 +0,0 @@
-[](#z-index-stacking)Z-index (stacking)
-=======================================
-
-The z-index determines the stacking order of elements. Elements with a higher z-index always sit in front of elements with a lower z-index. Each index has been mapped to the appropriate elevation(s).
-
-[](#reference)Reference
------------------------
-
-| Name | Usage | Value |
-| --- | --- | --- |
-| DEFAULT | The default z-index used for most elements. Can be combined with raised and floating elevations. | 0 |
-| MODAL | Used for IressModal. Can be combined with floating elevation. | 400 |
-| NAVBAR | Used for navbars. Can be combined with overflow elevation. | 100 |
-| POPOVER | Used for IressPopover. Can be combined with floating elevation. | 200 |
-| SLIDEOUT | Used for IressSlideout. Can be combined with floating elevation. | 300 |
-| TOAST | Used for IressToast. Can be combined with floating elevation. | 500 |
-| TOOLTIP | Used for IressTooltip. Can be combined with floating elevation. | 600 |
-
-* * *
-
-[](#for-developers)For developers
----------------------------------
-
-If you are using the IDS components, the z-indexes have already been mapped out to their respective components based on the usage above. They are hardcoded into the components, so you don't need to worry about them.
-
-The mapping is exported as `Z_INDEX` from the `@iress-oss/ids-components` package, in case you need to reference it in your own code.
-
-On this page
-
-*   [Reference](#reference)
-*   [For developers](#for-developers)

package/generated/docs/frequently-asked-questions-docs.md

@@ -1,53 +0,0 @@
-[](#frequently-asked-questions)Frequently asked questions
-=========================================================
-
-Some of the most frequently asked questions related to IDS are answered here.
-
-* * *
-
-[](#how-long-will-version-4-be-supported)How long will version 4 be supported?
-------------------------------------------------------------------------------
-
-We will continue to support version 4.x until the end of 2024. This means there will be security patches and critical bug fixes, but no new enhancements will be added to version 4.
-
-[](#does-this-mean-we-need-to-upgrade-now)Does this mean we need to upgrade now?
---------------------------------------------------------------------------------
-
-No, you do not need to upgrade now. However, we recommend that you start planning your migration to version 5 and use it for new projects. Support for version 4 will continue until the end of 2024.
-
-[](#what-support-will-there-be-to-help-us-upgrade)What support will there be to help us upgrade?
-------------------------------------------------------------------------------------------------
-
-If you are moving from version 4 to version 5, a [migration guide](?path=/docs/resources-migration-guides-from-v4-to-v5--docs) is available. This guide will help you understand the changes between the two versions, how to migrate your code, and how to use them side by side while you are migrating.
-
-If you plan to migrate soon, we would like to partner with you. Please reach out to the design system team via Iress channels.
-
-[](#what-will-happen-if-we-do-not-upgrade-by-the-end-of-2024)What will happen if we do not upgrade by the end of 2024?
-----------------------------------------------------------------------------------------------------------------------
-
-After the end of 2024, we will no longer provide support for version 4. This means that we will not provide any security patches or critical bug fixes, which may leave the rest of your application vulnerable to security threats. There are several ways to handle this:
-
-*   Upgrade to version 5 before the end of 2024.
-*   Create a PR to fix the issue in version 4 and submit it to IDS for review.
-*   Update nested dependencies to the secure version using `yarn audit` and `resolutions` in your `package.json`.
-
-[](#will-the-documentation-for-version-4-still-be-available)Will the documentation for version 4 still be available?
---------------------------------------------------------------------------------------------------------------------
-
-Yes, we will host the documentation for version 4 indefinitely. The documentation will be available on the [Versions page](?path=/docs/versions--docs).
-
-[](#can-i-contribute-to-version-4)Can I contribute to version 4?
-----------------------------------------------------------------
-
-Yes! We will continue to accept pull requests for version 4, but only until the end of 2024. To do so, please use `4.x` as the base branch for your pull request.
-
-After this time, we will only accept pull requests regarding critical security patches or critical bug fixes.
-
-On this page
-
-*   [How long will version 4 be supported?](#how-long-will-version-4-be-supported)
-*   [Does this mean we need to upgrade now?](#does-this-mean-we-need-to-upgrade-now)
-*   [What support will there be to help us upgrade?](#what-support-will-there-be-to-help-us-upgrade)
-*   [What will happen if we do not upgrade by the end of 2024?](#what-will-happen-if-we-do-not-upgrade-by-the-end-of-2024)
-*   [Will the documentation for version 4 still be available?](#will-the-documentation-for-version-4-still-be-available)
-*   [Can I contribute to version 4?](#can-i-contribute-to-version-4)

package/generated/docs/get-started-develop-docs.md

@@ -1,209 +0,0 @@
-[](#develop)Develop
-===================
-
-Set up your environment to use the latest version of the Iress Design System (IDS). You can use this library to build React applications that align to IDS, and ensure a consistent and modern look and feel across all Iress products.
-
-[](#requirements)Requirements
------------------------------
-
-*   [React 17 or later](https://reactjs.org/)
-*   Access to Iress Artifactory
-
-[](#set-up-the-component-library)Set up the component library
--------------------------------------------------------------
-
-1.  Install using the command line:
-    
-    \[data-radix-scroll-area-viewport\] {
-      scrollbar-width: none;
-      -ms-overflow-style: none;
-      -webkit-overflow-scrolling: touch;
-    }
-    \[data-radix-scroll-area-viewport\]::-webkit-scrollbar {
-      display: none;
-    }
-    :where(\[data-radix-scroll-area-viewport\]) {
-      display: flex;
-      flex-direction: column;
-      align-items: stretch;
-    }
-    :where(\[data-radix-scroll-area-content\]) {
-      flex-grow: 1;
-    }
-    
-    yarn add @iress-oss/ids-components
-    
-    Copy
-    
-2.  Import the styles:
-    
-    \[data-radix-scroll-area-viewport\] {
-      scrollbar-width: none;
-      -ms-overflow-style: none;
-      -webkit-overflow-scrolling: touch;
-    }
-    \[data-radix-scroll-area-viewport\]::-webkit-scrollbar {
-      display: none;
-    }
-    :where(\[data-radix-scroll-area-viewport\]) {
-      display: flex;
-      flex-direction: column;
-      align-items: stretch;
-    }
-    :where(\[data-radix-scroll-area-content\]) {
-      flex-grow: 1;
-    }
-    
-    import '@iress-oss/ids-components/dist/style.css';
-    
-    Copy
-    
-3.  Import the components. The provider is optional, but recommended for most applications. It sets up the design system and provides a consistent container for components like modals, slideouts, and toasts.
-    
-    \[data-radix-scroll-area-viewport\] {
-      scrollbar-width: none;
-      -ms-overflow-style: none;
-      -webkit-overflow-scrolling: touch;
-    }
-    \[data-radix-scroll-area-viewport\]::-webkit-scrollbar {
-      display: none;
-    }
-    :where(\[data-radix-scroll-area-viewport\]) {
-      display: flex;
-      flex-direction: column;
-      align-items: stretch;
-    }
-    :where(\[data-radix-scroll-area-content\]) {
-      flex-grow: 1;
-    }
-    
-    import { IressProvider, IressButton } from '@iress-oss/ids-components';
-    
-    Copy
-    
-4.  Use the components:
-    
-    \[data-radix-scroll-area-viewport\] {
-      scrollbar-width: none;
-      -ms-overflow-style: none;
-      -webkit-overflow-scrolling: touch;
-    }
-    \[data-radix-scroll-area-viewport\]::-webkit-scrollbar {
-      display: none;
-    }
-    :where(\[data-radix-scroll-area-viewport\]) {
-      display: flex;
-      flex-direction: column;
-      align-items: stretch;
-    }
-    :where(\[data-radix-scroll-area-content\]) {
-      flex-grow: 1;
-    }
-    
-    const App \= () \=> (
-      <IressButton onClick\={() \=> success({ children: 'Toast triggered' })}\>
-        Trigger toast  </IressButton\>
-    );
-    ReactDOM.createRoot(document.getElementById('root')!).render(
-      <IressProvider\>
-        <App />
-      </IressProvider\>,
-    );
-    
-    Copy
-    
-
-* * *
-
-[](#set-up-the-theme)Set up the theme
--------------------------------------
-
-The component library comes with the white label theme by default. You can add a theme by importing the theme file and including it in your application.
-
-Microfrontends
---------------
-
-If you are building a React App that is intended to be used as a microfrontend, please skip this step. Microfrontends should inherit the parent application's theme, and not define a theme itself, as it may conflict with other microfrontends in the same parent application.
-
-1.  Install using the command line:
-    
-    \[data-radix-scroll-area-viewport\] {
-      scrollbar-width: none;
-      -ms-overflow-style: none;
-      -webkit-overflow-scrolling: touch;
-    }
-    \[data-radix-scroll-area-viewport\]::-webkit-scrollbar {
-      display: none;
-    }
-    :where(\[data-radix-scroll-area-viewport\]) {
-      display: flex;
-      flex-direction: column;
-      align-items: stretch;
-    }
-    :where(\[data-radix-scroll-area-content\]) {
-      flex-grow: 1;
-    }
-    
-    yarn add @iress/ids-themes
-    
-    Copy
-    
-2.  Import the component:
-    
-    \[data-radix-scroll-area-viewport\] {
-      scrollbar-width: none;
-      -ms-overflow-style: none;
-      -webkit-overflow-scrolling: touch;
-    }
-    \[data-radix-scroll-area-viewport\]::-webkit-scrollbar {
-      display: none;
-    }
-    :where(\[data-radix-scroll-area-viewport\]) {
-      display: flex;
-      flex-direction: column;
-      align-items: stretch;
-    }
-    :where(\[data-radix-scroll-area-content\]) {
-      flex-grow: 1;
-    }
-    
-    import { IressTheme } from '@iress-oss/ids-components';
-    
-    Copy
-    
-3.  Add the component to your application:
-    
-    \[data-radix-scroll-area-viewport\] {
-      scrollbar-width: none;
-      -ms-overflow-style: none;
-      -webkit-overflow-scrolling: touch;
-    }
-    \[data-radix-scroll-area-viewport\]::-webkit-scrollbar {
-      display: none;
-    }
-    :where(\[data-radix-scroll-area-viewport\]) {
-      display: flex;
-      flex-direction: column;
-      align-items: stretch;
-    }
-    :where(\[data-radix-scroll-area-content\]) {
-      flex-grow: 1;
-    }
-    
-    ReactDOM.createRoot(document.getElementById('root')!).render(
-      <IressProvider\>
-        <IressTheme />
-        <App />
-      </IressProvider\>,
-    );
-    
-    Copy
-    
-
-For alternative ways to import the theme, see the [Themes documentation](./?path=/docs/themes-introduction--docs).
-
-On this page
-
-*   [Requirements](#requirements)
-*   [Set up the component library](#set-up-the-component-library)
-*   [Set up the theme](#set-up-the-theme)

package/generated/docs/get-started-using-storybook-docs.md

@@ -1,68 +0,0 @@
-[](#using-storybook)Using Storybook
-===================================
-
-The IDS team uses Storybook to develop and document our components. Storybook is a development environment for UI components. It allows you to browse a component library, view the different states of each component, and interactively develop and test components. It is most likely what you are looking at right now.
-
-Here we have just highlighted a few of our top tips on how you can use Storybook more efficiently. We have separated it by different stages of the product delivery cycle, but you can use these tips at any stage.
-
-* * *
-
-[](#first-time-users)First-time users
--------------------------------------
-
-When you first come to the IDS Storybook, you may notice the pages look un-styled. This is the default theme of IDS. You can change the theme to the theme you normally use in your product by clicking the `brush` icon in the top left, right above this page.
-
-You can also change to use the dark theme of Storybook itself by clicking the `moon` icon in the top left, right above this page.
-
-These settings are saved so the next time you come back to Storybook, it will remember your preferences.
-
-[](#scoping-work)Scoping work
------------------------------
-
-If you are scoping work, you can use Storybook to see what components are available to you. You can also see how they are used and what states they can be in. This can help you to understand what is possible and what is not.
-
-Every IDS component has a `Docs` page and a `Guidelines` (coming soon) page. The `Docs` page will show you how to use the component and what props it accepts, helping you understand what is available, and how each property behaves to allow you to understand the final user experience of your feature.
-
-The `Guidelines` page will show you how to use the component in a way that is consistent with other Iress applications. It covers things like accessibility, usability, and design principles, as well as which scenario to use which component and common pitfalls.
-
-[](#design)Design
------------------
-
-When designing a new feature, you can use Storybook to see how your designs will look and behave in a real application.
-
-`Docs` and `Guidelines` (coming soon) pages will help you understand how to use the components and what is possible, and help you align to any design decisions made previously.
-
-`Examples` are a good way to see how variations of a component look and behave. You can see how a component looks in different states, and how it behaves with different props. If there is a variation that is not shown in the `Examples`, you can use the `Controls` tab to change the props of the component to see how it behaves with different values. You can also toggle how each component looks at different breakpoints (screen sizes/devices), how they look to users with certain eyesight conditions, and how they look in different states.
-
-Storybook is a starting point for your designs. It is the language developers will be using as they convert your designs into live user experiences. However, not everything is covered here. It is good to discuss your designs with developers to understand what is possible and what is not.
-
-[](#development)Development
----------------------------
-
-During development, you can refer to Storybook for code examples and understand the API available to you.
-
-If you are using Typescript, majority of the API is available in your IDE. However, Storybook provides more than just the API. It provides examples of how to use and combine the properties, as well as which components were designed to work with each other.
-
-`Docs` covers the API of the component, and also discusses `Examples` in detail. Code examples are shown here as well.
-
-`Examples` in the sidebar actually allow you to toggle the props in the `Controls` tab to see how combinations look and behave. The `Actions` tab will show you what events are being emitted by the component, and the `Accessibility` tab will show you whether the combination of props is accessible or not in this component. You can also toggle how each component looks at different breakpoints (screen sizes/devices), how they look to users with certain eyesight conditions, and how they look in different states.
-
-IDS is a starting point for your application development. It provides the foundations to make your application look and behave in a consistent way to other Iress products. However, not everything is covered here. It is good to discuss with designers and other developers to understand any constraints or guidelines that are not covered by IDS.
-
-* * *
-
-[](#common-issues)Common issues
--------------------------------
-
-### [](#i-cant-find-the-controls-actions-or-accessibility-tab)I can't find the `Controls`, `Actions` or `Accessibility` tab
-
-These tabs are only shown in the `Examples` area of the component. Some tabs are not applicable to some components. If you click on an example and still cannot see it, you may need to toggle the orientation of the addon. You can do this by tapping the `d` key twice, or using the settings as shown in the video.
-
-On this page
-
-*   [First-time users](#first-time-users)
-*   [Scoping work](#scoping-work)
-*   [Design](#design)
-*   [Development](#development)
-*   [Common issues](#common-issues)
-    *   [I can't find the Controls, Actions or Accessibility tab](#i-cant-find-the-controls-actions-or-accessibility-tab)