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

[EPIC] Swag Store UX Improvements #123

Closed
4 tasks done
jlengstorf opened this issue Aug 24, 2018 · 3 comments · Fixed by #219
Closed
4 tasks done

[EPIC] Swag Store UX Improvements #123

jlengstorf opened this issue Aug 24, 2018 · 3 comments · Fixed by #219

Comments

@jlengstorf
Copy link
Contributor

jlengstorf commented Aug 24, 2018

NOTE: This issue is an epic, which bundles up lots of related issues into a single goal. If you have the free ZenHub extension, you’ll be able to see overall progress and related issues, as well as a "board view" that shows this epic from a bird's-eye view.

Who will own this?

Role Contributor(s)
AoR owner @jlengstorf
Domain owner @jlengstorf
Project manager TBD
Tech lead @jlengstorf
Contributors @jlengstorf, @lindaleebumblebee, @marisamorby

Summary

We have a lot of cleanup tasks for the swag store that need to be completed, as well as next steps (new swag #122 and contribution-based rewards #116).

This epic will bundle up the scope of work for phase 2.

How will this impact Gatsby?

Domains

  • Swag

Goals

What are the top 3 goals you want to accomplish with this epic? All goals should be specific, measurable, actionable, realistic, and timebound.

  1. Improve the UX of the swag store
  2. Eliminate annoying bugs like out-of-stock errors
  3. Add new features like larger image lightboxes to improve the store functionality

How will we know this epic is a success?

What changes must we see, or what must be created for us to know the project was a success. How will we know when the project is done? How will we measure success?

We'll know this epic is a success if:

  • The outstanding UX issues are addressed in the repo
  • The new features have been implemented successfully

Metrics to Measure Success

  • Decreased UX issues for the store

What are the risks to the epic?

In a few sentences, describe what high-level questions we still need to answer about the project. How could this go wrong? What are the trade-offs? Do we need to close a door to go through this one?

If we don't get the UX right, we risk adding extra hurdles or frustration to the swag buying/claiming experience, which could deter contributors from getting involved.

What questions do we still need to answer, or what resources do we need?

Is there research to be done? Are there things we don’t know? Are there documents we need access to? Is there contact info we need? Add those questions as bullet points here.

We need the following resources:

  • Limited design time to cover e.g. lightbox design and product detail pages
  • Dedicated developer time to implement the changes

How will we complete the epic?

What are the steps involved in taking this from idea through to reality?

  1. Finalize the scope of phase 2
  2. Write out better issue descriptions of the work
  3. Burn through the issues

How else could we accomplish the same goal?

Are there other ways to accomplish the goals you listed above? How else could we do the same thing?

Nope. Just have to do the work.

Next Steps

  • Under Pipeline select Proposed Epics (only if you are NOT the AoR owner)
  • Under Assignees select the AoR Owner
  • Under Labels select Epic
  • Select Create Epic
@jlengstorf jlengstorf self-assigned this Aug 24, 2018
@jlengstorf jlengstorf changed the title [EPIC] Swag Store Phase 2 [EPIC] Swag Store UX Improvements Aug 30, 2018
@jlengstorf
Copy link
Contributor Author

TODO: narrow scope of this, create follow-up epics for the work we're not going to do this time around.

@d3caf
Copy link

d3caf commented Oct 27, 2018

@jlengstorf I was going to open an issue and work to try and add a lightbox for the store item images. I saw that that feature is mentioned here, but this issue is closed so I was wondering if that was still something that would be good to work on.

@jlengstorf
Copy link
Contributor Author

@andrew-anguiano A lightbox would be great — I think we closed it as "not important", but there's no reason we wouldn't want to have that feature if you want to add it.

Thanks!

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

Successfully merging a pull request may close this issue.

2 participants