backstage / backstage/community-plugins
🚀 todo: Migrate to Backstage UI
- Dominant language
- TypeScript
- Stars
- 422
- Forks
- 697
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 286
Description
### Workspace
Select a workspace...
### 🔖 Feature description
The plugin can be migrated to BUI.
The plugin code is here: https://github.com/backstage/community-plugins/tree/main/workspaces/todo/plugins/todo
The list of available Backstage UI components is here: https://ui.backstage.io/
The process would be to just switch out the Material UI (MUI) components with their Backstage UI (BUI) versions and visually check to make sure they match. Additionally the Table component from `@backstage/core-components` can be changes to use the Table from Backstage UI (BUI).
### 🎤 Context
~
### ✌️ Possible Implementation
~
### 👀 Have you spent some time to check if this feature request has been raised before?
- [x] I checked and didn't find similar issue
### 🏢 Have you read the Code of Conduct?
- [x] I have read the [Code of Conduct](https://github.com/backstage/community-plugins/blob/main/CODE_OF_CONDUCT.md)
### Are you willing to submit PR?
No, but I'm happy to collaborate on a PR with someone else
Contributor guide
Research direction
Inspect the plugin code in workspaces/todo/plugins/todo and compare its current Material UI components with the available Backstage UI components at ui.backstage.io. Check the existing UI visually, then verify that the MUI components and the @backstage/core-components Table have been replaced with matching Backstage UI versions and the resulting visuals match.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100