Web: Clean Up Bounty Creation Flow

[PixelantDesign]

As a bounty funder, I want to easily understand the bounty creation process.

Description

There is a lot of information in the bounty creation flow such as metamask authentication, top tabs that do not accurately match the creation flow and form fields that are difficult to read. Mostly a structural update, very little visual update aside from resizing robot graphic and adding banners.

Assumptions

• This is clean up of the bounty screen only, not to redesign the flow.

Definition of Done

• Updates are made reflect the current experience and make bounty creation clearer (see provided documentation).
• Updating top nav to surface fund an issue
• Removing Metamask blocker page and change to a banner format
• Updating the order of form fields
• Adding dismissable banners in 3 states
• Support responsive views
• Leverage type and form styles defined in Gitcoin UI Kit
• Work with @PixelantDesign on any outstanding questions
• Remove Top four tabs on the following screens: Submit Work and Accept Bounty Fulfillment
• For form fields which are uneditable since data is brought in from Github. Add a tooltip on hover to indicate how a user might be able to edit this info.

Reviewers

@PixelantDesign @owocki

Reference Materials

Banners for the 4 scenarios

SVG Files are below
Graphics.zip

[olafghanizadeh]

I'll gladly take a look at this :)

[gitcoinbot]

__This issue now has a funding of 0.176 ETH (151.69 USD @ $861.85/ETH) attached to it.__

• If you would like to work on this issue you can claim it here.
• If you've completed this issue and want to claim the bounty you can do so here
• Questions? Get help on the Gitcoin Slack
• $6568.22 more Funded OSS Work Available at: https://gitcoin.co/explorer

[olafghanizadeh]

I'm still working on this, but had a lot of trouble with the docker container...

[mkosowsk]

@olafghanizadeh were you able to resolve your Docker issues or are they ongoing? What was the problem? 🤔

[olafghanizadeh]

@mkosowsk I was able to solve it yeah :)

Still working on this. There are some design issues I'm taking up with @PixelantDesign directly.

Also I would like to refactor so that all of the different notification messages for web3.js (metamask) stays in one file instead of 3 different files. Input? @mkosowsk @mbeacom

[mkosowsk]

@olafghanizadeh refactor into one file makes sense to me!

[owocki]

hows this going? last comment i see was 18 days ago

[jpramassini]

I was going to work on this, but I might need a week or so before I can. For now, I'll take myself off of this issue and then when I'm able put myself back on it on Gitcoin.

[mbeacom]

@olafghanizadeh Do you have a branch for this? Would you mind opening a PR? Also, one file makes sense! Feel free to handle that now or we can open an issue for it afterwards.
Please let me know if you have any questions or concerns!

[olafghanizadeh]

I’m actually working on this, but I’m having a lot of trouble staying up to
date with the repo :/

On Mon, 9 Apr 2018 at 13:00, Mark Beacom [e-mail] wrote:

@olafghanizadeh https://github.com/olafghanizadeh Do you have a branch
for this? Would you mind opening a PR? Also, one file makes sense! Feel
free to handle that now or we can open an issue for it afterwards.
Please let me know if you have any questions or concerns!

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gitcoinco/web/issues/429#issuecomment-379803184, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AYARAdspcLEzylY4zpXP3ITAnsbdxYkeks5tm4WLgaJpZM4SEzPo
.

[mbeacom]

@olafghanizadeh Yeah, that's what I heard. If you raise a PR associated with your branch, it'll be easier to know which files you're encountering conflicts with and allow us to try to accommodate those changes. Without knowing where/what you're working on, it's fairly difficult to try to avoid the conflicts.

Once you raise the PR, I'll be sure to review it and attempt to avoid merge conflicts with your changes or likewise, resolve the conflicts as they occur. Beyond that, you can always raise a PR and wait to rebase until you're done.

Feel free to reach out to me directly on slack if you have any questions or concerns.

Thanks for the contribution!

cc @PixelantDesign

[gitcoinbot]

@olafghanizadeh are you still working on this issue?

[gitcoinbot]

@olafghanizadeh are you still working on this issue?

[gitcoinbot]

@olafghanizadeh has been removed from this issue due to inactivity (11 days) on the github thread. @olafghanizadeh if you believe this was done in error, please go to the bounty and click 'start work' again.

[owocki]

kicking this back to 'open'

[owocki]

closing this as its been abandoned and the scope has been moved to #982

[gitcoinbot]

Issue Status: 1. Open 2. Expired

---

__Work has been started__.

1. @Theoutsiders733

   has committed to working on this project to be completed 2 months ago.

@PixelantDesign, __please see the below comments / questions regarding approach for this ticket from the bounty hunter(s):__

[thelostone-mc]

@owocki is this still open ? I believe this issue is being worked on two folks now

cc @Theoutsiders733 & @SaptakS

[owocki]

waiting for @PixelantDesign to close down the old bounty

[vs77bb]

FYI to @theoutsiders733 - this one is not open at this time. Thank you however, for your interest!

[thelostone-mc]

@Theoutsiders733 If you need other front end work -> Leave me a ping and I'll give you a heads-up over slack when something comes up! (Sorry about the confusion 😅)

[gitcoinbot]

@Theoutsiders733 Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• [x] warning (3 days)
• [ ] auto removal (6 days)

[gitcoinbot]

@Theoutsiders733 Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• [x] warning (3 days)
• [ ] auto removal (6 days)

[gitcoinbot]

@Theoutsiders733 Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• [x] warning (3 days)
• [ ] escalation to mods (6 days)

[thelostone-mc]

@PixelantDesign @vs77bb could we close the bounty out ?

[gitcoinbot]

@Theoutsiders733 Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• [x] warning (3 days)
• [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[gitcoinbot]

@Theoutsiders733 Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• [x] warning (3 days)
• [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[gitcoinbot]

@Theoutsiders733 Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• [x] warning (3 days)
• [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[gitcoinbot]

Issue Status: 1. Open 2. Expired

---

__The funding of 0.176 ETH (121.08 USD @ $687.95/ETH) attached to this issue has been cancelled by the bounty submitter__

• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $8,018.44 more funded OSS Work available on the Gitcoin Issue Explorer