a11y-theme-builder
a11y-theme-builder copied to clipboard
finos
DesignOps toolchain theme builder for accessibility inclusion using Atomic Design.
This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [@types/node](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/node) ([source](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node)) | [`20.14.15` -> `20.16.10`](https://renovatebot.com/diffs/npm/@types%2fnode/20.14.15/20.16.10) | [](https://docs.renovatebot.com/merge-confidence/) |...
![renovate[bot] avatar](https://avatars.githubusercontent.com/in/2740?v=4 "renovate[bot] avatar"){kind=avatar}
## Problem/Concern Discussed by @smithbk during his SDK educational session this week. It might be a good idea to create a way for developers to print out the dependency graph...
## Problem/Concern This issue is related to #888 and the other issues surrounding our decision to have a "single source of truth" JSON token generator rather than continuing to support...
## Problem/Concern Lise is doing a podcast, #A11yTalk in mid December. This issue is to make sure that we obtain a recording or a link to that podcast in order...
[](https://renovatebot.com) This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [node](https://togithub.com/nodejs/node) | final | minor | `18.19-bookworm-slim` -> `18.20-bookworm-slim` | ---...
Adding three pages /steps. 1. Core Settings 2. Build Color Palette 3. Light and Dark Mode Resolves issue: #820 #914 #916 #917 #918 #919 #920
Adding three pages /steps. 1. Core Settings 2. Build Color Palette 3. Light and Dark Mode Resolves issue: #820 #914 #916 #917 #918 #919 #920
## Problem/Concern Stemming from https://github.com/finos/a11y-theme-builder/pull/948#issuecomment-2200477209, it was suggested that we should have a pre-commit hook in Theme Builder to enforce Prettier formatting and linting so that we know that code...
## Problem/Concern @lwnoble asked me to create this issue. We need to determine if it is best to have component styling in one big file (perhaps broken into component-specific sections)...
This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [react-router-dom](https://redirect.github.com/remix-run/react-router) ([source](https://redirect.github.com/remix-run/react-router/tree/HEAD/packages/react-router-dom)) | [`6.26.0` -> `6.26.2`](https://renovatebot.com/diffs/npm/react-router-dom/6.26.0/6.26.2) | [](https://docs.renovatebot.com/merge-confidence/) |...