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

Design shrapnel #142

Open
24 tasks
edwh opened this issue Dec 31, 2019 · 7 comments
Open
24 tasks

Design shrapnel #142

edwh opened this issue Dec 31, 2019 · 7 comments
Labels
DevReady - Low Ready to code. Minor. UX/UI/CSS Requires visual flair

Comments

@edwh
Copy link
Member

edwh commented Dec 31, 2019

Little bits and pieces which could be slightly prettier, all fairly quick.

  • About - Rework to have a similar feel to the help page
  • error-toast - needs love
  • DonationThermometer - animate change in value
  • DraggableMap used from Spread - icon pin in the centre is not visible enough on the map.
  • GroupHeader There's a max-height hack above to keep the description from hogging the screen. It's not that pretty and some people may not even notice the scrollbar, but could be neater.
  • GroupSelect - hard-coded max-width.
  • OutcomeModal - Needs visual push to make people select a user. How?
  • OutcomeModal - "Please choose" is red but the dropdown shouldn't be.
  • Ratings - Showing your own feedback in blue is not intuitive. How can we improve that given the very limited space for this?
  • default - Shrink navbar on scroll? Hardcoded navbar heights in other places, though, search for 68px.
  • default - Notifications dropdown list isn't wide enough before it's loaded.
  • message/_id - when it doesn't exist, the message is brutal. error variant is a very shouty red.
  • StartEndDate - should be fieldset within a form.
  • In settings/index, the notice about phone costs should be a b-alert when it pops up but if the page loads with it already present then it should be a notice-message component
  • When an item has multiple photos, we have arrow buttons to move between them. Those buttons are lame.
  • Better way of indicating active page on navbar. Proposal is like LinkedIn with white for the active, grey of the others, and a white bar at the bottom. (Bar has been added but investigation is still required into suitable colours for the options)
  • Change 0px to be 0 everywhere
  • Use shorthand for padding/margins where appropriate
  • Analyse the use of !important
  • Remove all px font sizes are use relative units instead.
  • On mobile, when posting, Add photos button could be on same line as the message type, only over on the right, which would save some vertical space.
  • Tidy up the view profile logic. When clicking on the profile picture in NewsLovesModal it should link to the persons profile /profile/userid. The location information in NewsUserInfo already does this. Should we consolidate this in one place at the higher level?
  • The "Close Message" link you get after clicking to see details on a post needs better positioning and perhaps styling.
  • Hide the technical details of error messages in error.vue behind a "Show details" button.
@edwh edwh added UX/UI/CSS Requires visual flair DevReady - Low Ready to code. Minor. labels Dec 31, 2019
@edwh edwh added this to Triage in FD Nuxt Client via automation Dec 31, 2019
@project-bot project-bot bot moved this from Triage to DevReady - Low in FD Nuxt Client Dec 31, 2019
@aaronferris
Copy link

aaronferris commented Jan 13, 2020

With respect to the Group header, how do we want to position the buttons (join etc) on mobile?

Both Under the logo? Just contact under the logo? Assume left align for any under the logo?

Screenshot 2020-01-13 at 09 17 14

@edwh
Copy link
Member Author

edwh commented Jan 13, 2020 via email

@aaronferris
Copy link

aaronferris commented Jan 13, 2020

OK - think I have that right in my head, probably best to mock something up for mobile, tablet, desktop then confirm before we make any changes. That might be tricky to attain using just CSS, having a quick look at the markup.

@edwh
Copy link
Member Author

edwh commented Jan 13, 2020 via email

@aaronferris
Copy link

Yeah ill take a look when I get chance, back at work now so might be a few days before I can, was just having a quick look to define what the expected result would be.

@edwh
Copy link
Member Author

edwh commented Jan 13, 2020 via email

aaronferris pushed a commit to aaronferris/iznik-nuxt that referenced this issue Jan 18, 2020
aaronferris pushed a commit to aaronferris/iznik-nuxt that referenced this issue Jan 19, 2020
aaronferris pushed a commit to aaronferris/iznik-nuxt that referenced this issue Jan 19, 2020
edwh added a commit that referenced this issue Jan 19, 2020
#142 improve group header layout to avoid any overlap, obtuse or odd …
aaronferris pushed a commit to aaronferris/iznik-nuxt that referenced this issue Jan 19, 2020
edwh added a commit that referenced this issue Feb 3, 2020
#142 Additional header changes with the 'see' text
@JayyajGH
Copy link
Contributor

I've just removed the "tidy the group header" issue as it was recently resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DevReady - Low Ready to code. Minor. UX/UI/CSS Requires visual flair
Projects
FD Nuxt Client
  
DevReady - Low
Development

No branches or pull requests

3 participants