|
| 1 | +# Design System Working Group |
| 2 | + |
| 3 | +Design System maintainers are responsible for developing and sustaining the [STRUDEL Design System](https://strudel.science/design-system/overview/), including STRUDEL-Kit. They must: |
| 4 | +- Keep the STRUDEL Design System usable by the community. This includes stewardship of the STRUDEL Kit, Task Flow designs, tutorials, and documentation. |
| 5 | +- Monitor issues, emails, and pull requests, even if they are not the primary contact point for a given issue, email, or pull request |
| 6 | +- Ensure a maintainer replies to new issues, emails, and pull requests promptly, ideally within two days |
| 7 | +- Ensure other contributors have adequate opportunity to engage |
| 8 | +- Define and maintaining a product roadmap |
| 9 | + |
| 10 | +## Roadmap |
| 11 | +*Current priorities:* |
| 12 | +- Review and refine contribution guidelines and governance procedures |
| 13 | +- Evaluate processes and tools to ensure sustainable, low‑effort contributions |
| 14 | +- Design for AI capabilities in Task Flows (existing and new) |
| 15 | + |
| 16 | +*Near future priorities:* |
| 17 | +- Consolidate STRUDEL resources in STRUDEL website |
| 18 | +- Refine onboarding pathways for different STRUDEL users |
| 19 | + |
| 20 | +*Long term priorities:* |
| 21 | +- Refine and expand existing guidelines and Task Flows, incorporating new variations and evolving user needs |
| 22 | +- Develop a STRUDEL components library to enable more granular, flexible, and reusable UI elements |
| 23 | +- Expand the task flow code to include minimal backends to act as templates and reference apps |
| 24 | + |
| 25 | +## Membership |
| 26 | +Design System Working Group currently include: |
| 27 | +Cody O’Donnell, @codytodonnell |
| 28 | +Rajshree Deshmukh, @Rjdesh |
0 commit comments