we could stop adding css variable fallbacks, polyfills, and target more modern js for smaller bundles
I've added how to triage someone else's issue to the main tables to divs issue, https://issues.jenkins.io/browse/JENKINS-64072?focusedCommentId=401604&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-401604
if anyone has time triaging some of them would be appreciated :)
A small addition to our icon discussion in the SIG meeting on Wednesday (it was a little bit hard for me to follow the discussion since I needed to take care of my children in parallel :smile:) I think both FontAwesome and Material Design provide a lot of good looking icons. I prefer the style of FontAwesome: they also seem to have more useful icons (for Jenkins), have an active community to get new icons designed, etc. But I think that by using Material Design we also would not do something completely wrong.
However, before we now start to replace icons in PRs we should go one step back and think about that in more detail. Otherwise we would get the same design diversity as we have now with some Tango icons and a lot of icons from varying sources. Where do we need icons in the upcoming Jenkins versions? I know we need a build status, alerts (warnings, errors, etc.) actions like search, copy, edit, etc. But where else do we need icons? Do we still want that every plugin action provides UI elements that use icons? How can we achieve that so that the UI still looks consistent? Maybe it would be helpful to make a list of elements that currently use icons and show which of these icons can be replaced by existing icons of the icon libraries (FontAwesome or Material Design). If there is no existing icon, how can we get one? Do we have designers on board? Do have have supporting companies that would sponsor the design of a consistent icon set? Can we follow a way similar to FontAwesome (with Crowdsourcing?)… Sorry a lot of questions, for which I do not have an answer yet.
I’m currently fixing some small bugs in my warnings plugin due to the table to div conversion. Is it intended, that the font of the label is 14px while the font of the description text is 16px? In most cases the labels are more important than the descriptions.
And another question related to the new layout: now that the label is above the input field there is much more space available for the label text. What is the idea for form controls now: should we rework labels and descriptions so that the label gets a longer text and maybe the description can be removed at all? Or should labels still be as short as possible. It would be helpful if we would provide some guidelines on how to create good and consistent forms...