New answers tagged

0

I would recommend only showing the scrollbar on hover and having sticky columns that allow the user to still see which rows are relevant. Adding a shadow to the sticky column will give the impression that the columns are scrolling beneath. I think having the scrollbar at the bottom is fine as long as the table is not taller than the window. If it is taller ...


0

It looks like you are describing a stepper with each of the setup steps. Similar to tabbed partition, but staying on the same screen and with the possibility of using different elements and scrollings in each step. Example from Codepen


1

I would use the dashboard page for simple navigation first, with three cards side by side. Every card with an icon on top, Small Title beneath it, and a small description underneath the title if necessary. Have a button at the bottom of each card to take the user to the respective form/page. Make sure to keep the form simple with help-blocks beneath the ones ...


0

Scroll-by-column is a nice pattern for when there are long columns, and the user wants to examine them one-at-a-time. Benefits: It's good for when the user is focused on their own to-do list (out of a group), or when a scrummaster calls on one engineer at a time. Animation (such as the small scrolling interaction of a rolling column) helps draw attention. ...


0

It all depends on the content provided there. Infinite scroll has pros and cons. In order to user test this you first need to determine how that content is digested by the user. Do they need to find a specific content ? Do they need to create a mental model of where that specific content was ? ( this is hard to do with infinite scroll ). Do they need to ...


Top 50 recent answers are included