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

Fixes 646: kill Thanks page (and move it into a flash message of new issue) #1247

Merged
merged 6 commits into from
Dec 22, 2016

Conversation

miketaylr
Copy link
Member

@miketaylr miketaylr commented Dec 16, 2016

r? @magsout for CSS
r? @karlcow for Python

Not sure we want to merge just yet, it's sort of ugly. I'd like Mesha to do a UX review of the copy as well -- suggestions for words or design welcome from anyone!

(edit: also ignore that the header isn't styled -- that's taken care of in #1246)

screen shot 2016-12-16 at 5 37 07 pm

@miketaylr
Copy link
Member Author

Oops:

FAIL: Test that /thanks/1 exists.

@miketaylr miketaylr requested review from karlcow and magsout December 17, 2016 02:02
Copy link
Member

@karlcow karlcow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Everything looks good under the hood. r+ @miketaylr

@adamopenweb
Copy link
Collaborator

Pinging @lockettm. Can you take a quick look at this please? Would love to have your feedback. :)

@miketaylr
Copy link
Member Author

(also, the "Complain on Facebook" text is a joke)

@lockettm
Copy link

Copy looks good.

I kind of like the "Complain on Facebook" text. :) If we want to add more context to the "Share on Twitter" and "Share on Facebook" buttons, a line above stating "Tell your friends about the bug you just filed," might work.

This could also be an opportunity to further engage users--explain what happens next and invite them to join the team. However, if the main goal is to get them to share on social media, this may split their attention.

@miketaylr
Copy link
Member Author

Thanks for reviewing!

This could also be an opportunity to further engage users--explain what happens next and invite them to join the team. However, if the main goal is to get them to share on social media, this may split their attention.

Yeah, I agree this is a good spot to recommend next steps and give suggestions on how they can help, etc. Let's file a bug to add that kind of stuff after we ship the simple version.

Copy link
Member

@magsout magsout left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good idea @miketaylr
👍

border-color: #ffc900;
position: static;
width: var(--Issue-widthComment);
color: #fff;

This comment was marked as abuse.

This comment was marked as abuse.

@@ -29,3 +30,18 @@
color: #fff;
background-color: rgba(255, 89, 89, 0.92)
}

.wc-FlashMessage.thanks {

This comment was marked as abuse.

This comment was marked as abuse.

background-color: #fff;
color: #000;
text-align: left;
margin: 0;

This comment was marked as abuse.

This comment was marked as abuse.

@miketaylr
Copy link
Member Author

screen shot 2016-12-22 at 11 24 38 am

OK, here we are. There's lots of room for improvement -- please file bugs and send PRs to make it better!

Thanks @karlcow @lockettm @magsout for review!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants