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

Use bugs for status indicators #980

Closed
hbillings opened this Issue Oct 28, 2016 · 11 comments

Comments

Projects
None yet
3 participants
@hbillings
Member

hbillings commented Oct 28, 2016

For the user's own price lists, bugs like the WDS uses for their "alpha" and "beta" component indicators might be really helpful: https://standards.usa.gov/labels/

@jseppi

This comment has been minimized.

Contributor

jseppi commented Oct 28, 2016

Are "bug" and WDS's "label" the same thing?

@hbillings

This comment has been minimized.

Member

hbillings commented Oct 28, 2016

LOL, I picked a terrible example page. Though we probably could use labels, depending on how we want to design it. I was thinking of these things like the "beta" here:
screen shot 2016-10-28 at 11 48 54 am

EDIT: I think the biggest difference is probably where they sit -- the bugs are inline, whereas the labels ride above the text.

@ericronne

This comment has been minimized.

Contributor

ericronne commented Dec 21, 2016

@hbillings what does a "bug" look like?

@jseppi

This comment has been minimized.

Contributor

jseppi commented Dec 21, 2016

@ericronne I think that is TBD! What do you think a bug should look like?

@ericronne

This comment has been minimized.

Contributor

ericronne commented Dec 21, 2016

Ah, i thought she was referring to a bug that WDS uses.

So we're talking about designing a way for data uploaders to know the status of their uploads. Could be a bug/icon, but an explicit label is generally more clear. We could also use a bug, label, and color together. I'll noodle on this as i re-style the details page.

I'm thinking we should also indicate status on a user's list of uploaded PL's. Agree?

@jseppi

This comment has been minimized.

Contributor

jseppi commented Dec 21, 2016

Yea, I agree.

@hbillings

This comment has been minimized.

Member

hbillings commented Jan 3, 2017

@ericronne I was thinking of these little labelly things that the standards site uses, but doesn't define:
screen shot 2017-01-03 at 1 36 37 pm

But please do what makes sense to you!

@ericronne

This comment has been minimized.

Contributor

ericronne commented Jan 3, 2017

Yep
image

@ericronne

This comment has been minimized.

Contributor

ericronne commented Jan 15, 2017

Blew this out a little more, and added an icon for style and increased accessibility.

image

Here are the icon svg files.

Colors

Pending
BG: #FBEEBE
Icon and text: #825C1E

Rejected
BG: #FAD0D0
Icon and text: #BC1630

Approved
BG: #E6EDC2
Icon and text: #61701C

image

@ericronne ericronne referenced this issue Jan 15, 2017

Merged

Style error tables and implement tooltips #1245

1 of 1 task complete
@ericronne

This comment has been minimized.

Contributor

ericronne commented Jan 15, 2017

lmk if those svg files are funky.
i'll be amazed if they aren't!

@hbillings

This comment has been minimized.

Member

hbillings commented Feb 16, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment