Skip to content
This repository has been archived by the owner on Aug 17, 2019. It is now read-only.

UI Fix - Events section #5

Open
johnathantng opened this issue Mar 25, 2019 · 1 comment
Open

UI Fix - Events section #5

johnathantng opened this issue Mar 25, 2019 · 1 comment
Assignees
Labels
enhancement New feature or request UI Fix Fixes to User Interface user experience

Comments

@johnathantng
Copy link
Member

The events section is a bit cluttered.

  • I think a fix for it would be to take out the two rows, because it'll be less confusing that way. Especially since there's no borders that indicate how you should read it.

  • Maybe have some visual cues for how the user should read the events (borders, images, icons, etc.) Anything to indicate the flow/direction for how the user should read it.

  • The title the events should be emphasized and maybe even a short summary or description of each event. The event name should be "visually loud" so that it'll be the first thing that catches the user's eyes. The description(?), date, location, time should come after.

@tonynguyen111997 tonynguyen111997 added the UI Fix Fixes to User Interface label Mar 25, 2019
@lloan
Copy link
Member

lloan commented Mar 26, 2019

I agree. Since we're using Bootstrap, we should stick to the components provided by BootStrap.

Here is a link to the card component -> https://getbootstrap.com/docs/4.3/components/card/

We could use this for each event that is pulled from the Meetup.com API.

Building off your first point, we could have a horizontal carousel, slides from right to left, showing the latest event first. OR we could have the first row be the latest events and have a -show more- link below that row, centered. Once the user clicks it, another row is 'lazy loaded' - providing the user with more information about past events.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request UI Fix Fixes to User Interface user experience
Projects
None yet
Development

No branches or pull requests

3 participants