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

New WET elements required (image slider, responsive table, image table) #6

Open
lmichaud opened this issue Dec 6, 2018 · 4 comments

Comments

@lmichaud
Copy link
Contributor

lmichaud commented Dec 6, 2018

Following the usability report, and the prototypes supporting the proposed RSA content template, new elements need to be developed and deployed into WET.

  1. image slider: a mobile friendly image carousel to display a series of images

  2. responsive table: expansion of the data table to support mobile responsiveness

  3. displaying images in a table format: ability to display images in a table when visuals provide information value

@thomasgohard
Copy link

thomasgohard commented Dec 10, 2018

  1. WET already has a mobile-friendly image carousel: https://wet-boew.github.io/v4.0-ci/demos/tabs/tabs-carousel-en.html.

  2. WET has a basic responsive table: http://wet-boew.github.io/wet-boew-styleguide/v4/design/tables-en.html#responsive. We had also started work on integrating Tablesaw, which offers more features and may better meet your needs.

  3. WET in no way stops you from putting images in a table.

@lbelmore
Copy link
Contributor

Here are the mockups for the image table layout we reviewed with TBS

image

@lmichaud
Copy link
Contributor Author

@thomasgohard , yes, I realize that WET has an image carousel and a data table but during usability testing conducted by the DTO team, a new swipe carousel and responsive mobile table view was opted to improve the mobile experience. Displaying columns on mobile proved to be problematic. As per TBS's recommendations, we're working with Mario to expand WET to include additional options (one as seen above from Lisa).

@thomasgohard
Copy link

@lmichaud perfect. I just wanted to make sure you weren't under the impression that the functionality didn't exist. And I do agree that it needs improvement, so I'm glad that work is underway to do so.

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

No branches or pull requests

3 participants