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

Responsive Layout: Events List #162

Open
rymaju opened this issue May 19, 2021 · 0 comments · May be fixed by #189
Open

Responsive Layout: Events List #162

rymaju opened this issue May 19, 2021 · 0 comments · May be fixed by #189
Assignees
Labels
backlog These are non-essential tickets that are on the backburner. css This label indicates that the assigned issue requires CSS/styling knowledge medium

Comments

@rymaju
Copy link
Member

rymaju commented May 19, 2021

Project/Issue Tracker

Objective

As a user I would like to comfortably view the events list on my phone. See the Figma for an exact specification of how the UI should look.

Tech Spec

  • Augment the CSS such that the component fits on tablet and mobile, include screenshots for verification
  • Website must match Figma specifications.

Please look at #161 (PR #175) if you need starting ideas.

@rymaju rymaju added the medium label Jun 16, 2021
@rymaju rymaju added this to the Summer milestone Jun 16, 2021
@varunthakkar1 varunthakkar1 added the css This label indicates that the assigned issue requires CSS/styling knowledge label Jul 2, 2021
@varunthakkar1 varunthakkar1 self-assigned this Aug 2, 2021
@varunthakkar1 varunthakkar1 added the backlog These are non-essential tickets that are on the backburner. label Sep 14, 2021
@varunthakkar1 varunthakkar1 linked a pull request Oct 10, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog These are non-essential tickets that are on the backburner. css This label indicates that the assigned issue requires CSS/styling knowledge medium
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants