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.

Sign up for GitHub

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

Jump to bottom

Design updates from Tobey #32

Closed
11 tasks done
seeReadCode opened this issue Jul 15, 2016 · 6 comments
Closed
11 tasks done

Design updates from Tobey #32

seeReadCode opened this issue Jul 15, 2016 · 6 comments
Labels
question
Milestone
v0.4.0

Comments

@seeReadCode
Copy link
Contributor

seeReadCode commented Jul 15, 2016 •
edited
Loading

Short term

  • 3x grid for home view
  • leaderboard

Accomplished

  • new fonts
  • user dropdown
  • fixed header
  • better announcement treatment
  • blue for input fields
  • label treatments
  • tabbed login/signup
  • oo to word mark and back during page transition
  • focus state for non-input keyboard v. mouse (ask sina for code)
@seeReadCode
Copy link
Contributor Author

Relates to #5 #16 #29 #26 #25

@seeReadCode seeReadCode added this to the v0.4.0 milestone Jul 15, 2016
seeReadCode added a commit that referenced this issue Jul 19, 2016
@seeReadCode
fonts added and set, user dropdown implemented ref #32
03d17e3
seeReadCode added a commit that referenced this issue Jul 19, 2016
@seeReadCode
input fields, input field outline color, fixed header ref #32
d630db1
seeReadCode added a commit that referenced this issue Jul 19, 2016
@seeReadCode
label styling ref #32
a49c79b
seeReadCode added a commit that referenced this issue Jul 19, 2016
@seeReadCode
announcement treatment ref #32
1f1b145
seeReadCode added a commit that referenced this issue Jul 27, 2016
@seeReadCode
home page improvements ref #32
5f4dc18 
+ sticky footer styling
+ log in and sign up tabs on home page
+ placeholder styling
+ some more about text
+ typo on form
@seeReadCode
Copy link
Contributor Author

this commit was related as well 9e1eccb

seeReadCode added a commit that referenced this issue Jul 27, 2016
@seeReadCode
temp fix for footer ref #32
2308363
seeReadCode added a commit that referenced this issue Jul 27, 2016
@seeReadCode
more button styling ref #32
8e0714b
@seeReadCode seeReadCode mentioned this issue Aug 11, 2016
Closed
seeReadCode added a commit that referenced this issue Aug 13, 2016
@seeReadCode
no visual focus indicator for non form elements ref #32
05b5c50
seeReadCode added a commit that referenced this issue Aug 13, 2016
@seeReadCode
actually black text ref #32
c05d183
seeReadCode added a commit that referenced this issue Sep 8, 2016
@seeReadCode
home page tweaks ref #32
bf770c2 
+ isotope added for queue columnar layout
+ dropdown positioned flush with button left cornr
+ btn-full full width with dropdown for queue action
+ SASS file organized a bit better and commented
seeReadCode added a commit that referenced this issue Sep 8, 2016
@seeReadCode
leaderboard basic ref #32
e2f5b69
@seeReadCode
Copy link
Contributor Author

seeReadCode commented Sep 8, 2016 •
edited
Loading

Other leaderboard component ideas:

  • non-progress bar-able important metrics, such as ones that hopefully count from n to 0, e.g. the ready to review count,
  • comparably show counts for top 5 describers as well as v. self,
  • show badges, names for some of the bests, e.g. approval record, days active streak.

We would need agreement on the important metrics, and then a graphic treatment per metric type. Some of these ideas would require much more dev time than others to implement.

Other design ideas for the near to short term:

  • more intense visual call to action for priority items (maybe red highlight?),
  • display priority counts in queue headings on home page,
  • do we want to show counts across image groups in queue headings?

seeReadCode added a commit that referenced this issue Sep 8, 2016
@seeReadCode
leaderboard tweaks for admin counts ref #32
0a5fe48
@alavatelliMCA
Copy link
Contributor

I like the leaderboard component ideas. Do you need a design for graphic treatment?

  • Will the priority items be the first to appear in the Queue? They should be pushed ahead of everything. If so I don't know that it needs to be called out more, but will look with Tobey.
  • Can you explain what you mean by priority counts in queues? Not following
  • I don't think we need counts across groups as the groups are somewhat blurred, but if simple to implement it can't hurt to have.

@seeReadCode
Copy link
Contributor Author

@alavatelliMCA I clarified my text a bit to help answer your questions (and to clarify some of your responses for anyone else following along).

@seeReadCode
Copy link
Contributor Author

@alavatelliMCA please let me know what you are thinking about the leaderboard and what questions you have now re: priority counts etc

This was referenced Sep 20, 2016
Closed
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question
Projects
None yet
Milestone
v0.4.0
Development

No branches or pull requests
2 participants
@alavatelliMCA @seeReadCode