design-library-plugin
design-library-plugin copied to clipboard
[sirocco_based] refactor to be based on sirocco-wc
Background
I am currently working on the introduction of web components to be used in cloudbees jenkins plugin development. I created a small framework around lit and tailwind to be able to quickly develop new modern UIs based Jenkins plugins. https://github.com/scherler/sirocco-wc#readme
In case we base our development on a web component based library we can use the design library as we currently know it as a wrapper (to still support plugins that uses them), so it still exposes those tags but underlying it just hands over to a standard web component. That allows us to focus on one central place for the design and the look and feel of server-side rendered components is the same as with a SPA development. In the future, we may want to recommend using the web components directly instead of the jelly ones. e.g. <f:checkbox title="${%Example}" field="hello" /> could become
There are undergoing efforts to create and use a lit-based WC lib https://github.com/halkeye/jenkins-io-components IMOHO this library could be moved here and be a starting point to not only expose jelly tags but as well web components published in npm.
- [ ] Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
- [ ] Ensure that the pull request title represents the desired changelog entry
- [ ] Please describe what you did
- [ ] Link to relevant issues in GitHub or Jira
- [ ] Link to relevant pull requests, esp. upstream and downstream changes
- [ ] Ensure you have provided tests - that demonstrates feature works or fixes the issue
FYI This PR will fail until https://github.com/jenkinsci/plugin-pom/pull/625 is resolved and released.