Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add sidebar to plugin manager, increase search bar size #6783

Merged
merged 59 commits into from
Sep 6, 2022

Conversation

janfaracik
Copy link
Contributor

@janfaracik janfaracik commented Jul 5, 2022

This is a small-ish PR to add a sidebar to the plugin manager, as well as to increase the size and prominence of the search bar.

What's changed

  • New sidebar
  • Update count now displays in the sidebar
  • Search bar is now larger and sticks to the top of the page
  • Misc text changes

Before
image

After
image

Screen.Recording.2022-07-05.at.17.32.21.mov

Proposed changelog entries

  • Add sidebar to plugin manager, increase search bar size

Proposed upgrade guidelines

N/A

Submitter checklist

  • (If applicable) Jira issue is well described
  • Changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developer, depending on the change) and are in the imperative mood. Examples
    • Fill-in the Proposed changelog entries section only if there are breaking changes or other changes which may require extra steps from users during the upgrade
  • Appropriate autotests or explanation to why this change has no tests
  • New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadoc, as appropriate.
  • New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO") if applicable.
  • For dependency updates: links to external changelogs and, if possible, full diffs

Desired reviewers

@jenkinsci/sig-ux

Maintainer checklist

Before the changes are marked as ready-for-merge:

  • There are at least 2 approvals for the pull request and no outstanding requests for change
  • Conversations in the pull request are over OR it is explicit that a reviewer does not block the change
  • Changelog entries in the PR title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood
  • Proper changelog labels are set so that the changelog can be generated automatically
  • If the change needs additional upgrade steps from users, upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the PR title. (example)
  • If it would make sense to backport the change to LTS, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).

@timja
Copy link
Member

timja commented Aug 20, 2022

Do you want something done here?

We could try disabling autocomplete if required.

——

Can you clarify what is holding back the approval please?

@daniel-beck
Copy link
Member

daniel-beck commented Aug 20, 2022

Can you clarify what is holding back the approval please?

Available time and competing priorities. I like to review and test nontrivial changes in depth. What I wrote above was initial feedback when running this PR, haven't gotten around to a more extensive test.

Copy link
Member

@NotMyFault NotMyFault left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • manage/pluginManager/available's bottom sticker is detached from the background, until you scroll to the bottom of the page and back up:
Kapture.2022-08-23.at.22.34.44.mp4

- I'd be in favor of dropping the search bar suggestions for now, if that's a specific addition of this PR, because this PR targets the sidebar and search bar size. We can reiterate that on a later PR, but I feel minor changes like these end up in delaying PRs longer than needed.

Edit: Disregard the latter, the same behavior is present on recent weeklys.

@timja
Copy link
Member

timja commented Aug 23, 2022

manage/pluginManager/available's bottom sticker is detached from the background, until you scroll to the bottom of the page and back up:

I haven't managed to reproduce this (on chrome)

Can you reliably reproduce it? and are there any specific steps

@NotMyFault
Copy link
Member

NotMyFault commented Aug 23, 2022

Can you reliably reproduce it? and are there any specific steps

Dashboard -> Manage Jenkins -> Manage Plugins -> Available plugins on a clean installation let me reproduce it with Chrome 104.

I can't reproduce it reliable it with Safari or Firefox :/

@github-actions github-actions bot added the unresolved-merge-conflict There is a merge conflict with the target branch. label Aug 25, 2022
@github-actions
Copy link

Please take a moment and address the merge conflicts of your pull request. Thanks!

@github-actions github-actions bot removed the unresolved-merge-conflict There is a merge conflict with the target branch. label Aug 25, 2022
@basil basil added the squash-merge-me Unclean or useless commit history, should be merged only with squash-merge label Aug 25, 2022
@github-actions github-actions bot added the unresolved-merge-conflict There is a merge conflict with the target branch. label Aug 28, 2022
@github-actions
Copy link

Please take a moment and address the merge conflicts of your pull request. Thanks!

@github-actions github-actions bot removed the unresolved-merge-conflict There is a merge conflict with the target branch. label Aug 28, 2022
Copy link
Member

@NotMyFault NotMyFault left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks fancy 🎉

I'm fine with disregarding my previous concern, given input suggestions aren't introduced here and do already exist on the past weeklys.

@timja
Copy link
Member

timja commented Sep 3, 2022

/label ready-for-merge


This PR is now ready for merge, after ~24 hours, we will merge it if there's no negative feedback.

Thanks!

@comment-ops-bot comment-ops-bot bot added the ready-for-merge The PR is ready to go, and it will be merged soon if there is no negative feedback label Sep 3, 2022
@basil
Copy link
Member

basil commented Sep 5, 2022

Wow, this looks great! I am very pleased with the result and I think this is a huge step forward. I only have one piece of optional non-blocking feedback for your consideration.

When I click on "Download progress" on the sidebar, I get to a page with "Download progress" as its heading. When I click on "Advanced settings" on the sidebar, I get to a page with "Advanced settings" as its heading. However, when I click on "Updates", "Available Plugins", or "Installed Plugins" on the sidebar, I get to a page with "Plugins" as its heading. To me, this is unexpected because I would expect the heading of the page to match the navigation link. To me, this feels like it is possibly a relic of the older implementation (where these three pieces of functionality were on a single page with three tabs) that was unintentionally carried through into the redesigned version. But whether or not it was intentional, it seems inconsistent and therefore a potential source of confusion to users. My vote would be to make the headings consistent with the navigation links in all cases. If I am wrong about something here, please feel free to correct me.

@timja
Copy link
Member

timja commented Sep 5, 2022

But whether or not it was intentional, it seems inconsistent and therefore a potential source of confusion to users. My vote would be to make the headings consistent with the navigation links in all cases

I think that will be mostly addressed when #6783 (comment) is sorted.

The title will move into the sidebar and the plugin manager pages themselves won't have a main title.

Basically the 3 tabs are being considered as part of 1 page almost.
advanced being a bit special and it could be somewhat removed with some additional refactoring out of scope of this PR.


If no objections I plan to merge this tomorrow towards the next weekly.

@timja timja merged commit 6db88c3 into jenkinsci:master Sep 6, 2022
@timja timja deleted the new-plugin-manager-1 branch September 6, 2022 07:30
Comment on lines +62 to +82
.task-icon-badge {
position: relative;
color: currentColor;
letter-spacing: 0;
z-index: 0;
margin-left: auto;
min-width: 24px;
text-align: center;
padding: 0 8px;
line-height: 0.75rem;
font-size: 0.75rem;

&::before {
content: "";
position: absolute;
inset: -6px 0;
background: var(--item-background--hover);
border-radius: 100px;
z-index: -1;
}
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unused in this PR, only used in #7084.

Comment on lines +84 to 90
.task-link-text {
display: contents;
}

.task-link-text {
display: contents;
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Improperly resolved conflict, or what is this for?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You're correct 👍 I've removed it as part of #7084

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready-for-merge The PR is ready to go, and it will be merged soon if there is no negative feedback rfe For changelog: Minor enhancement. use `major-rfe` for changes to be highlighted security-approved @jenkinsci/core-security-review reviewed this PR for security issues squash-merge-me Unclean or useless commit history, should be merged only with squash-merge web-ui The PR includes WebUI changes which may need special expertise
Projects
None yet
6 participants