List view
📋 Gather product team requirements for Data Grid functionality 🔍 Evaluate Toolbox Grid against the feature matrix 📝 Propose a contribution strategy for Q3
Due by June 30, 2026•0/6 issues closed🌗 Alpha-channel approach for disabled states implemented: investigation completed, decision made, and approach applied consistently across all existing components 🔍 Colour token values reviewed and refined: a joint design and development review of all current token values completed, with changes documented and released 📐 Density mode tokens updated: token set updated to reflect the new spacious mode and the renaming of existing modes to comfortable and compact 🏷️ Token naming re-evaluated: a review of the current token naming conventions completed, with a documented proposal for any changes and a clear rationale 📖 Token documentation updated to reflect all changes, including rationale for the alpha-channel approach, density mode naming, and any token naming updates
Due by June 30, 2026•0/9 issues closed🔬 Spike completed: the most appropriate technical approach for AI-assisted EDS integration investigated and a decision made – MCP server, CLI, or alternative 🛠️ MVP built and deployed: a working solution that enables AI tools to query EDS components, tokens, and guidelines accurately 🧪 MVP validated: confirmed working with at least one AI-assisted tool (e.g. Claude Code) in a real design or development workflow 📖 Usage documented: a guide published for the EDS team and product teams on how to use the solution in their AI-assisted workflows
Due by June 30, 2026•0/11 issues closed🔬 Typography investigation completed and documented: React Native typography capabilities – already being assessed at the end of Q1 – finalised with clear decisions on what is achievable and what requires workarounds or constraints 🏗️ Colour, spacing, and typography foundations integrated into the React Native component library 📐 Density modes introduced: a new spacious mode added as the default for mobile, with the existing density modes renamed to comfortable (default for web) and compact; all React Native components updated accordingly 📤 Updated React Native library published to npm with a migration guide ✅ Library validated by the Mobility team: at least one production app replaces components using the updated library, with the app fully functional and no major visual regressions
Due by June 30, 2026•1/1 issues closed✅ Update previously released components to component-owned CSS typography 🏗️ Build all new Q2 components with component-owned CSS typography from the start 🚢 Ship components in phases/slices 🎯 Ensure Figma components accurately reflect the code implementation 📚 Complete and standardise component documentation across all newly shipped components ♿ Ensure all shipped components meet WCAG 2.2 AA accessibility standards
Due by June 30, 2026•9/115 issues closed#### Key Results - [ ] 🔍 Ergonomics app component requirements validated: Typography, Radio buttons, Button, Card, Link, Accordion, Table (simple), TextField, TextArea - [ ] 🎨 All required components for Ergonomics POC available in task-focused theme (Figma + web components + React wrappers) - [ ] 🚢 Ergonomics app POC built as PWA using EDS web components (via React wrappers) - [ ] ✅ PWA POC validated with Mobility team: performance, offline capability, and installation tested on iOS - [ ] 📋 PWA migration path documented for other mobile apps based on POC learnings **Why Ergonomics:** This content-focused mobile app validates our PWA approach can replace React Native for informational apps. Success enables broader mobile strategy shift. **Timeline:** POC can begin after Slice 3 delivery (all required components except Table), complete after Slice 4.
Overdue by 14 day(s)•Due by March 31, 2026•6/7 issues closed#### Key Results - [ ] 🎯 Slice 2 - Form & Basic UI - [ ] 💬 Slice 3 - Layout & Feedback - [ ] 📊 Slice 4 - Data & Navigation - [ ] 🏗️ Component architecture established: base components defined in Core library, stateful components extracted to separate packages with migration guides - [ ] ✨ All components achieve 1:1 fidelity: matching component API and visual output between Figma and code - [ ] ♿ All components meet WCAG 2.2 AA accessibility standards with APCA contrast optimization where possible without compromising design system consistency **Vertical shipping approach:** Each component is completed across full stack (Figma design → web component → React wrapper → documentation) before moving to next component. **Architecture shift:** EDS Core contains only base components (presentational, no state management). Stateful components (like Autocomplete with built-in filtering) extracted to separate npm packages.
Overdue by 14 day(s)•Due by March 31, 2026•16/18 issues closed#### Key Results - [ ] 🎓 Team trained on Claude Code and AI-assisted development workflow by end of January - [ ] 🔧 Web components development workflow established with Claude Code integration and documented best practices - [ ] 📊 50% of Q1 component implementations completed using AI-assisted workflow - [ ] 🔄 Token Studio integrated into development workflow for algorithmic token generation - [ ] 🤖 RAG system made available with indexed EDS 2.0 documentation and components - [ ] 🎨 Product teams can generate EDS-compliant UIs using Figma Make **Why this matters:** Establishes foundation for efficient component development and makes our design system accessible to AI tools, setting up future Make kits and other AI integrations in Q2. Related discussion: https://github.com/equinor/design-system-internal/discussions/234
Overdue by 14 day(s)•Due by March 31, 2026•28/28 issues closed