Improve dev experience for plugins
- Dominant language
- Scala
- Stars
- 301
- Forks
- 76
- PR merge metrics
- No merged PRs in 30d
Description
## Tasks
- [ ] Storybook. Develop using storybook approach. (Initial version with basic set up): 2 SP
- [ ] Cover cases where providing static resources is not an option. (instigate and develop) . 3 SP.
- [ ] Get a dev client id and fix token management. 1 SP.
- [x] Move the repo to EPFL Gitlab with CI/CD. (3 SP).
- [ ] Automate the package version for each individual package using CI.
- [ ] Optimize build script and bundling. 2 SP
Please contact other teams at BBP (e.g. NSE, DKE) to query them about their dev experience.
Contributor guide
Research direction
No files, tests, or entry points are named. Start by inspecting the repository's plugin packages, Storybook setup, build script, and CI/CD configuration, then clarify the unchecked tasks with the relevant BBP teams. Done means the agreed development workflow, token management, package versioning, and build improvements are implemented and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gitlab, scala, storybook
- Domain
- build-system, ci-cd, developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100