Skip to content

Conversation

@JadElClemens
Copy link
Contributor

@JadElClemens JadElClemens commented Jan 1, 2026

Introduces a slight Wishlist UI rework to remove (imo) unnecessary headers and considerably condense "action buttons" (pledge/unpledge, move, edit, and delete) in the mobile UI particularly. Incidentally, I have also tuned some of the wishlist table widths. and completely removed (not disabled) buttons for actions that are not allowed (i.e. delete or edit an item you did not add).

Here on, I'll use "standard UI" to mean a wide screen and "mobile UI" to mean a narrow screen. Overall, compressing the action buttons saves a considerable amount of vertical space on the mobile UI, making it much easier to get an overview of the whole list. On the stanrdard UI, we save a little bit of horizontal space - I have used this to slightly enlargen the name and description fields (I think).

Feedback Requested

I think that the meaning of the buttons is pretty easy to understand, but I can also forsee the need to keep the "move" buttons on one's own list separated into their own section (i.e. "Move Item") to further clarify their purpose. I could use some feedback on the placement/justification of items (pledge/unpledge on right, others on left - where applicable) and the new widths of columns.

I've also used mostly element-level styles. Not sure if any existing classes come close to what I've changed or what a better way to do this would be.

Alternatives

Instead of completely removing Delete and Edit when not allowed, it might be better to keep them present but disabled, and we can make the Pledge/Unpledge button match the width of the four move buttons that would be present on your own wishlist. That way the UI is a little more consistent.

Comparison

Own wishlist, standard UI

Before:

image

After:

image

Other's wishlist, standard UI

Before:

image

After:

image

Own wishlist, mobile UI

Before:

image

After:

image

Other's wishlist, mobile UI

Before:

image image

After:

image

@JadElClemens JadElClemens marked this pull request as ready for review January 5, 2026 01:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant